Posted: 21 Mar 2017 4:41 EDT Last activity: 16 Oct 2018 12:03 EDT
UniqueActivityTerminateExceptions in V7.1.9 (after upgrading from V6.2.1)
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 error message always appears in the log when activity-end is executed. The message just means that, because it occurs so often, no stack trace is provided. If you want a trace, follow the instructions in the message.
Is there any problem other than the message in the log?
We raised a request with Pega (SR-B13295) and we were given the following response.
As per PRPC design, Activities do not support throwing an exception, We recommend not to depend on exceptions.It’s impossible to throw exception from activity and it should depend on harness-fail response instead of exception, So the behaviour is intended to the PRPC platform.
We are facing same kinds of issue while using Activity-End method in an Standard Agent Processing. Cases are going to Broken Queue due to that exception.
As per the article from Pega -
"RESOLUTION : As per PRPC design, Activities does not support throwing an exception, user is recommend not to depend on exceptions. It is impossible to throw exception from activity and it should depend on harness-fail response instead of exception, so the behavior is intended to the PRPC platform."
Not sure what does it means. Does it says -
1. We can't use Activity-End in an Agent activity?
2. If we use Activity-End in a standard agent and cases goes to Broken Queue, there is no solution available?