Question
Cognizant
IN
Last activity: 16 Oct 2018 12:03 EDT
UniqueActivityTerminateExceptions in V7.1.9 (after upgrading from V6.2.1)
We got the same exception UniqueActivityTerminateExceptions in 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...
Original thread for reference: https://collaborate.pega.com/question/activity-end-step-throws-activityterminateexception-pega-718
***Moderator Edit: Vidyaranjan | Branched comment to create new thread, updated categories***
***03/04/2017:Updated by moderator: Lochan to add SR details***
**Moderation Team has archived post**
We got the same exception UniqueActivityTerminateExceptions in 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...
Original thread for reference: https://collaborate.pega.com/question/activity-end-step-throws-activityterminateexception-pega-718
***Moderator Edit: Vidyaranjan | Branched comment to create new thread, updated categories***
***03/04/2017:Updated by moderator: Lochan to add SR details***
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
Accepted Solution
Pegasystems Inc.
IN
Hello!
On reviewing the corresponding SR, we see that it has been resolved. SA-34920 was created as a result of the investigation. Please reference that if you have the same question.
Thank you,
PEG
US
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?
Cognizant
IN
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.
Accepted Solution
Pegasystems Inc.
IN
Hello!
On reviewing the corresponding SR, we see that it has been resolved. SA-34920 was created as a result of the investigation. Please reference that if you have the same question.
Thank you,
Accenture
US
