Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Venkata Krishna Chaitanya Potluri (ChaitanyaPVK)
Truviq Systems
Lead System Architect
Truviq Systems
NL
ChaitanyaPVK Member since 2015 15 posts
Truviq Systems
Posted: Sep 12, 2018
Last activity: Sep 18, 2018
Posted: 12 Sep 2018 12:11 EDT
Last activity: 18 Sep 2018 4:44 EDT
Closed

pxPersistCase activity instance key (gethandle) mapping

Why pxPersistCase activity having instance key mapping to newassignpage when GenerateID is executed in previous step.

GeneratedID wont generate the pzinsKey.

***Edited by Moderator Marissa to update platform capability tags****

To see attachments, please log in.
Case Management

Posted: 6 years ago
Posted: 12 Sep 2018 12:36 EDT
Marc Lasserre (MarcLasserre_GCS)
PEGA
Technical Account Manager
Pegasystems Inc.
FR

Hello,

Step3 is generating the ID for the pyWorkPage. Then in step4, the system is checking with when conditions if corresponding newAssignPage needs to be synchronized I would say.

So the ID generated for pyWorkPage (for the case) will be pushed to newAssignPage (for the assignment) 

To see attachments, please log in.
Posted: 6 years ago
Posted: 13 Sep 2018 4:51 EDT
Venkata Krishna Chaitanya Potluri (ChaitanyaPVK)
Truviq Systems
Lead System Architect
Truviq Systems
NL

Hi,

pyID is not sufficient to correct the newAssignPage. It's required pzInsKey of the instance and its not generated by GenerateID activity in previous step.

To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice