What Motivates You to Participate Here in the PSC?
Reply posted on November 12, 2019 by Otto_PerdeckPega
Hi In strategy "test" mode that is the expected behavior- we evaluate all components. But when running for real, e.g. via a data flow run, that should not be the case. Can you confirm how you tested this? Thanks Otto
Reply posted on November 12, 2019 by LaurenceB_GCSPega
The Java code is going to generate the Java stack for the current thread. If this activity was called with a Batch operation, then this would send the job to a new Batch thread, hence you wouldn't be able to see the calling activity (as this would...
Reply posted on November 12, 2019 by SasidharB9516
To your point "The existing expired locks should not prevent a user from getting the lock", current customized logic is stopping user if any row in locks table for a instance handle. And please advise how locks are released based on system...
Reply posted on November 12, 2019 by AndreyO3
Issue was resolved. Into function "pzGenerateDocument" in processTable added correspondence handling.
Reply posted on November 12, 2019 by PraveenMohan
Hi Sathyajit, Recently, I have implemented the same. Please refer the attached document for reference
Reply posted on November 12, 2019 by DineshKumarD9112
Pega Creates a Page List for the below JSON code snippet when using Connect REST Wizard in Version 8.2. So even I have created a page list to store the values of the conditions. The values are stored in pyValue property of the page. "conditions...
Reply posted on November 12, 2019 by palakt44
I tried to configure the SLA on process tab for screen flow but WO level urgency and urgency on screenflow SLA is getting added and being displayed as WO level urgency. To be precise, SLA on screenflow is interrupting the WO level SLA