Reply posted on November 10, 2016 by AkshaySinhaPega
Hello, Please click on View additional configuration options:
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!
This week we recognize Dinesh Kumar Dhanasekaran as our Participant of the Week! Dinesh is using the PSC in an effective manner by actively driving their discussions forward and acknowledging the community for the responses received; thus, building successful solutions. Hope to see you around and Congratulations!
we also have the ACTIVITY Work- • pxForceCaseClose which closes all related work objects, i.e. removes assignments and updates the status.
You should use OOTB API activities pxAdjustSLA OR pxAdjustSLATimes which takes care of updating the SLA and the SLA event queue also.
You can find more information at https://pdn.pega.com/sites/pdn.pega.com/files/help_v72/procomhelpmain.htm#concepts/casemanagement/con_conceptsgetnextwork.htm#kanchor1455 and that article refers to https://pdn.pega.com/sites/pdn.pega.com/files/help_v72...
while routing please make sure the respective operator has a respective work group and make sure he will be haivng enough roles. kindly provide some more details of the issue so i can share my knowledge on same
Adding a target property to a case type Add a target property to your parent case type to support aggregate calculations. This helps you automatically collect information from child cases at run time. Open a parent case type in Case Designer. Click ...
Please provide more details on what you are trying accomplish. It will help in investigating the issue further.
Yes the checkbox was checked. The issue is resolved now. The problem was not with in Pega but with VM server. The VM Motion on the Server made it move to uncompatible node causing various issues.
Please wait while we search for PDN content that suits your question.