Reply posted on July 19, 2016 by JANAKA..PERERA
Hi Hanuma, Please let me know are you able to figure out this. We need to do the same thing. Thanks, Janaka Perera
Collaborate with developers, support engineers, and experts who build and work with Pega products and services. Join us to get fast answers to your questions, and participate in our Ask the Expert sessions!
Congratulations to Gouri Shankar for achieving the title of Participant of the Week! Gouri Shankar believes in sharing knowledge. He proved to be an amazing participant by writing a knowledge share article on a topic that will be informative to the diverse audience in the community. Read his article here. Keep up the great work!
Use on Exception check box ticked in each step expected to get exception while/after processing. Then set the error code and error message, in fault tab format a error message using error message property.
The solution suggested above does not work if you are testing the connection and providing a local file. Otherwise it does work.
Using the Pega Process Extender for Salesforce.com is the recommended approach for web mashup of Pega app into a Salesforce screen.
Hi Mandapan, You can change the logging level setting to DEBUG by navigating from Pega Button-> Tools-> log level settings. Supply the class name and change it to desired level. Thanks, Abdul Qaadir.
**..High priority..** My scenario is.. service returns complex data type in return property.. as accelerator is not able to decode it as different elements, it is storing all the repeating complex data type (<LISTITEM/>) tags into a single...
Please wait while we search for PDN content that suits your question.