Support Article
Pega API handles page groups incorrectly
SA-63291
Summary
As part of the Pega API enhancement to support UI construction in other applications, the current Pega API handles page groups incorrectly.
Error Messages
Not Applicable
Steps to Reproduce
- Call PegaAPI to post an assignment with a PageGroup in the post body.
- Call pzPerformAssignment to test this (Private check out and add the Request, ActionID, and AssignmentID parameters).
For example,
Post body is {"content":{"BugDescription":"aa","StepsToReproduce":"bb","Followers":{"stuff":{"Type":"Developer","Name":"","Email":"","FollowerID":""}}}}
Where Followers is PageGroup.
Root Cause
A defect in Pegasystems’ code or rules.
The work object is saved with the pxObjClass value for the page group property. This is due to the combination of unknown properties on the page and performing page-merge-into.
Below are the four scenarios:
Scenario 1. POST /assignments/{id}?actionID={id} using the object populated with data as the new entry.
Scenario 2. POST /assignments/{id}?actionID={id} using an empty object as the new entry.
Scenario 3. PUT /assignments/{id}/refresh using the object populated with data as the new entry.
Scenario 4. PUT /assignments/{id}/refresh using an empty object as the new entry
Resolution
Apply the following hotfixes:
- HFix-44870
- HFix-46072
Published February 19, 2019 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.