Posted: 21 Aug 2015 10:43 EDT Last activity: 21 Mar 2017 4:42 EDT
'Activity-End' step throws 'ActivityTerminateException' in Pega 7.1.8
I have called 'Show-Harness' from 'PeformDefaults' activity in certain conditions. After it, I have added 'Activity-End' to abort all operations to just display what 'Show-Harness' brings. But it is throwing follwing error. This was working in Pega 6.2. We started noticing the problem only after upgrade to Pega 7.1.8.
com.pega.pegarules.pub.runtime.ActivityTerminateException: This is a singleton exception object and the stack trace below does NOT reflect the actual point of failure. To see the actual trace, set Initialization/UniqueActivityTerminateExceptions = true
Why would you call Show-Harness from PerformDefaults? If the process engine is calling that extension point activity, that means you are about to show the perform harness. I am far more surprised that this ever worked without problems than I am that you are having issues now. If you don't want to show the perform harness, why are you doing whatever it is that you're doing to call perform defaults (Opening an assignment? Moving the item forward in the flow?)? It sounds like your implementation is doing something fundamentally dangerous and you got lucky in PRPC 6.2, but I would strongly suggest you reconsider what you are doing and not compound the situation by adding more layers of code outside the guardrails to get past this error in Pega 7.1.8.
I agree. We use CPM framework, when user accidentally closes/refreshes the browser session, the pending service items of an interaction are still available in worklist. User clicks those service items directly from worklist. We would like to prevent it.
One workaround is add filter logic in worklist and prevent the pending service items and show only pending Interactions (I-XXX). Except that, do you have any ideas for simple workaround/solution?
Wouldn't you want the users to be able to go in and finish the pending work if they accidentally closed the browser? I think you're going down the right path by filtering the assignments that you don't want them to click on. That said, what mechanism do you have for cleaning up those old assignments? Won't they increase over time and clutter up the assignment tables in the database?
We have agents setup to clean up pending assignments. There are certain service items we encourage user to complete it single go. Even if they miss it, we have encouraged them to launch new interaction and corresponding service item.
I agree with Pega design that user can pick up from worklist and proceed from the point where they stopped/missed. But, the business requirement of our application needs the design that certain service items should complete single go.
All right. In that case, yes, definitely make sure that you filter the worklist so they only show interactions and not service items. That seems like the cleanest solution and one that's least likely to produce unintended consequences.
I want to continue this discussion as we dont have any agent configured to claer assignment. The developer, Ganesh, was not aware of this. When we were not having this exception (pega 6.1) we displayed a custom harness that shows a message to the user and a close button to delete the assignment.
Activity-End method was used to supress the out of the box perform harness which overrides the custom harness.
We got the same exception UniqueActivityTerminateExceptionsin V7.1.9 (after upgrading from V6.2.1).
Just like the post above... we are also calling 'Show-Harness' from 'PeformDefaults' activity.
When a user with insufficient skills attempts to open a case we have to call 'Activity-End' to abort all operations and show a 'custom screen' to convey that their skill set is not sufficient to work on the concerned case.
Is something wrong with the Activity-End method in Pega7 ? Do we have a hotfix ? We did not find any relevant messages/hits in the tracer...
This comment has been branched out as a new node and the new thread can be followed here