Question
Accenture
SG
Last activity: 2 Nov 2016 7:51 EDT
Case management Step Deletion
Team,
I have an wiered behaviour after deleting a step from Stage in case.
Case is run till that stage and terminating not going to next stages even theough there are no conditions to terminate.
And this is happening only if i delete a step from the stage. Any suggestions
Pegasystems Inc.
IN
Hi
Sounds like a cache issue , Have you checked the behavior logging out and logging in again ?
Also have you checked in your changes ?
Pegasystems Inc.
IN
When you deleted the step, which step was this current Case in ?
Was this case in the same step that you deleted or before ?
Accenture
SG
To santanu ,
Yes I have checked in my changes also tried logging out and relogging.
To rawap,
there is no UI th case is always started with Add. so after deletion, saving i rerun the case and then this issue occurs.
To reproduce the scenario below are the steps.
Have a Case with 2 stages and each stage say have 3 steps.And in first stage 3rd step have pre-condition so that it will never enter and always skips, make sure first 2 steps have some utility not assignments.
After that delete the 2ns step and run the case then the case terminates in first stage without going to 2nd stage. you introduce that 2nd step again then run again case goes to 2nd stage after completion of first stage.
Pegasystems Inc.
US
Hi,
Some screenshot would be helpful but make sure the Stage Tranistion is still set to automatic upon process completion. What happens when you remove the precondition of the third step?
Accenture
SG
Yes there is automatic transition to next stage.
And when that pre condition is removed on the step 3 then the case is processed and going to next stage successfully even when you delete the 2nd step.
As I indicated there is no UI for this and the issue is found when traced.
Attached tracer screens hots 1 for issue when 2nd step deleted and pre condition exist for 3rd step and othet when 2nd step deleted, pre condition removed for 3rd step.
Here after ValidateRequest there is another stage called ProcessRequest which needs to be called.
Pegasystems Inc.
IN
With the information provided, it's really difficult to understand what the issue is. To understand scenario better, let me put it down in a sequence of steps and see where you are facing the issue:
- Create a "Case type" with 2 stages: Stage A and Stage B
- Stage A has 3 steps: Step 1A, Step 1B and Step 1C
- Step 1C has pre-condition defined such that it never executes and moves to next stage
- Step 1A and 1B has utility shape used in the flows
- Stage B has 3 steps: Step 2A, Step 2B and Step 2C
- Run the case type. A new instance with ID "C1" is created and works fine
- Now go to "Case type" and delete Step 1B from stage A
- Run the case type again. Another new instance with ID "C2" is created AND terminates (read fails) in first stage and doesn't go to Stage B
- Add back Step 1B in Stage A and save the Case type
- Run the case type again. Another new instance with ID "C3" is created and it works fine.
If the above scenario is correct, some questions:
With the information provided, it's really difficult to understand what the issue is. To understand scenario better, let me put it down in a sequence of steps and see where you are facing the issue:
- Create a "Case type" with 2 stages: Stage A and Stage B
- Stage A has 3 steps: Step 1A, Step 1B and Step 1C
- Step 1C has pre-condition defined such that it never executes and moves to next stage
- Step 1A and 1B has utility shape used in the flows
- Stage B has 3 steps: Step 2A, Step 2B and Step 2C
- Run the case type. A new instance with ID "C1" is created and works fine
- Now go to "Case type" and delete Step 1B from stage A
- Run the case type again. Another new instance with ID "C2" is created AND terminates (read fails) in first stage and doesn't go to Stage B
- Add back Step 1B in Stage A and save the Case type
- Run the case type again. Another new instance with ID "C3" is created and it works fine.
If the above scenario is correct, some questions:
- Is the above narration is correct? are you facing this issue for existing instances created before deleting Step 1B or only for the new instances you create after deleting Step 1B? (Like "C2" above)
- What kind of utilities you are using in the Step 1A and Step 1B
- What do you mean by termination of Case? Do you see any errors in tracer?
- What is the purpose of Step 1C in stage A ?
- Which version of Pega 7 is it? (e.g., 7.1.8 or 7.1.9).
- Also, as Drew asked for:
- Can you share the screenshot of the Case type with stages/steps configurations?
- Did you try removing the pre-condition on Step 1C?
The tracer screenshots being shared with masked data and the explanation is not clear enough to understand the issue.
Accenture
SG
Hi Vijay,
1. Your narration is absolutely correct and here the issue is newly created instances, there is no further usage on old instances once created they are not iused further so o issue with old instances.
2. Utilities refer to the norml activities.
3. No errors in the trace but after the 1st stage the processing is stopped without going to 2ns stage.
4.the purpose of step 1c is for some different type of request and for one typ eof request it is always skipped.
5. the version is 7.1.6
6. a. this is an client project I cannot provide more screenshots
b. Yes when pre -conditiob removed it is working fine.
Pegasystems Inc.
IN
6. a. this is an client project I cannot provide more screenshots
b. Yes when pre -conditiob removed it is working fine.
In this case, the only way I see is to log a support ticket and have an expert from support team to debug further and do a screenshare if possible.
Pegasystems Inc.
IN
Hi Aditya,
Please let us know the SR number if you end up create one as Vijay suggests! We will tag it to this post for easy troubleshooting.
Regards,
Lochan | Community Moderator | Pegasystems Inc.