Reply posted on November 22, 2017 by MaulanaP
Thanks in advance for your response
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!
This issue rarely happen. 1. when clicking on a button child cases get resolved. not using agents 2.no lock errors in logs 3.pxCoverCountOpen =1 4.Obj-Refresh-And-Lock is used
As I mentioned can you post screenshots of your....-> 1. current application rule 2. Application Ruleset also. Seems like you are referring application context with no unlocked rulesets or in a branch.
pxGuardrailComplianceScore property has a declare expression(DE) defined on it. As per DE, if the value of.pyRules on the primary page is 0 then compliance score is set to 100. This may be the reason why you are seeing above behavior. Refer to DE and...
Hi Suresh, In the Optimistic locking functionality whoever submits the work object first is choosen as the first user and the second user will be notified with a message to reload the work object to see the first user changes before commit. Regards...
This was a limitation due to case locking and is addressed in 7.3 release. Please find below the snippet from the release notes. Cases no longer locked when followed Work party properties of the type follower are no longer associated with the cases...
Please wait while we search for PDN content that suits your question.