Question
NTT Data
US
Last activity: 30 Dec 2018 11:48 EST
OOTB Step Approve/Reject -using Case Wide
I have a requirement need to Cancel case any time in the Case Life Cycle, my idea was to add as optional action- eventually is become cancel local action in case lifecycle.
But thought of utilizing OOTB Approve/Reject , My Question is during different case stages - one of the stage step I added Approve/Reject then is getting as Alternate Stage "Approval Rejection" , my question is it available whole case life cycle?
Then what is the difference adding as optional actions ? and using OOTB Approve/Reject?
Pegasystems Inc.
US
There is an OOTB Work- pyResolveAndCloseCase Flow Action.
You can save this rule to your work pool class renaming it ResolveAndCloseCase.
For the post-activity create and use a ForceCaseResolve Activity that has a "WorkStatus" parameter. Set the value of this parameter to .pyResolvedStatus.
Activity Steps:
- Obj-Refresh-And-Lock
- param.ReleaseOnCommit = true
- call pxForceCaseClose
- param.WorkStatus = Param.WorkStatus
- param.CloseAllSubcases = true
- Commit = true
- CloseParentCase = true
Be certain that Param.WorkStatus is set.
This Flow Action can be also used from My Cases and My Worklist by adding a Button to the Grid.
- Event = Click
- Action = Local Action
- ResolveAndCloseCase
- Modal Dialog
NTT Data
US
Thanks, but sorry, my requirement is I need to cancel the case any point in case life cycle .
So I am thinking this are possible options utilizing OOTB rules also without any configuration.
1) Use Approve /Reject step in one stage that would automatically create "Approval Rejection" alternate stage which serve my purpose - so here am not doing anything -just drag and drop
2) Create Cancel Case optional process - not sure this is better than case wide local action
3)Create Cancel Case case wide local action
so i need to choose two of above listed three items , this one I am just using OOTB
Pegasystems Inc.
US
The button-launched local action I described earlier can be configured as a case-wide local action which is your option (3).
Your requirement is to be able to cancel the case at any step. Approval is step within a Primary stage.
You can always implement a variation of the case-wide Change Stage action that jumps to a "Cancel/Withdraw" Alternate stage. There is nothing magic about the Alternate stage generated by the Approval step - you can create it yourself.
If there is an elaborate process required to cancel a case, then option (2) would make sense. You could also implement that process within "Cancel/Withdraw" Alternate stage step(s).