Error in External Assignment Goal Execution
When an external assignment is created and correspondence generated to provide the external link, the behaviour of the Goal Execution to send a follow up has changed in Pega 7.1.7.
Previously, the .CorrHandle property was stored and retrieved from the pxFlow pages with a reference to the main flow which contains the External Assignment.
The “ExternalGoal” activity uses the CorrHandle property to retrieve the correspondence and send a follow up. The full “InstanceHandle” syntax is: primary.pxFlow(param.flowName).pyFlowParameters.CorrHandle
This no longer works as the .CorrHandle property is now located under a different page (VerifySendCorr)
Class does not exist
Steps to Reproduce
This issue can be reproduced with the following steps:
1. Call the “EngageExternalQuick” flow from a main flow.
2. Copy the “External” SLA rule and reduce execution time to be 10 seconds
3. Either trace the SLA agent or change “ExternalGoal” activity to write out an error message.
4. Process the flow to External Assignment and observe the error in Goal Execution.
The root cause of this problem is a defect in Pegasystems’ code/rules. The defect is described in the Summary above.
This issue is scheduled to be resolved in Maintenance Level (ML) release 7.1.8. A local change that can be made in 7.1.7 is to hard code the name of the "VerifySendCorr" flow in the "ExternalGoal" activity.