Join Arun Sarada (ArunSarada) in the Ask the Expert session (21-25 Oct) on Case Management!
Meet Arun: Arun Sarada is a Product Manager at Pegasystems and responsible for Case management capabilities in the platform. Arun has close to 15 years of experience, out of which 7 years are in product management. It is his passion and love to build great products.
Message from Arun: Hi all! I'm glad and excited to share my learnings and knowledge on Pega Case Management that helps building the workflow applications that can automate and transform business operations and empower knowledge workers to perform their job more effectively. I’m looking forward to provide answers to all your queries around case types and its related functionality.
Watch this What's New video where ArunSaradaexplains changes to the Case Management and Collaboration capabilities such as the ability to switch applications, task improvements in spaces, and the ability to configure default feed sources in Pulse.
Child case can be created through the"Create case" smart shape . As part of "Create case " smart shape configuration there is a check box "Transfer information to new case" to be selected. This provides the ability to choose the data that needs to be propogated to the child case.
After reaching to stage I'll be displayed with 5 child cases. on selecting the link of the 1st child case, a window will be opened by replacing the parent case. here is my challenge that comes in to picture. After completing the child case I need to return to the parent case where I am displaying all the 5 child cases link. Please help me with this.
Assuming you're using OOTB case worker portal . If yes, once you open the child case from the parent case , you will be seeing all the open assignments for you in the child case . you'll also find a breadcrumb above the label of the child case using which you must be able to navigate to the parent case.
We have a requirement where we are creating child cases from a parent case .
Now my question is : When the child cases are closed one by one , it tries to acquire a lock on the parent and throws the below error:Parent case is locked by requstor"..." This erro gets triggered from pega OOTB activity Resolve upon submitting the screen . Scenario :Try creating a child case and have the parent case when in another operator . While resolving the child case, we will get this error . Please be noted that we are not trying to close the parent case upon closing the child .
I want to know what is the locking configuration we should ideally follow in the case configuration . Please find my sreen print attached and would appreciate if you can attach the screen print of the locking mechanism in the case configuration for both parent and child .
This is expected behaviour and the message is due to the fact that , by default, when a child case is opened , the lock is acquired on both parent and child case when default locking is enabled on the parent case type. This means users cannot work on child cases simultaneously.
If you want to users to work on the child cases simultaneously, you have to select the option "Do not lock the parent when the child case is being performed" . when you enable this option , there is no lock acquired on the parent case. Hope this clarifies.
we have the parent case and multiple subcases. we configured the locking as follows on the parent default locking and on the subcases we configured do not lock parent. user1 opens the parent case and works on. while the user try to initiate the child case, he is getting a message case is locked by user1.
if we already instantiated the child case then both users can work parallel. How do we overcome that second user can instantiate a child case if another is working on the parent case. I do not want to use optimistic locking.
"Do not lock the parent when the child case is being performed" checked specifies that some other user can work on the parent case when a user is working on the child case. If you don't want any other user to work on the child case when the parent case is locked , please uncheck "Do not lock the parent when the child case is being performed" option on the child case. This will make sure when some one is working on the parent case( directly or working on any other child of the same parent) they can't work on any of the child case related to this parent.