Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Errors creating application built on Appeals & Grievances layer

SA-3660

Summary



An error occurs when trying to generate a new application built on the 'Appeals & Grievances Layer v7.12 on Pega 7.1' application.

Error Messages



There was an error generating the application. Please contact your system administrator if the problem persists.

A Rule-Obj-CaseType could not be saved due to 7 error(s) on it:
.pyRemoteFields(8).pyMessageLabel: ** .pxFlow(Complaint).pyLastFlowStepLabel:  PageGroup type properties are not allowed
.pyRemoteFields(9).pyMessageLabel: ** .pxFlow(Data EntryFlow).pyLastFlowStepLabel: PageGroup type properties are not allowed
.pyPropertyValueFromFedarated(4).pyMessageLabel: ** .pyWorkParty(Member).pyWorkPartyUri : PageGroup type properties are not allowed
.pyPropertyValueFromFedarated(5).pyMessageLabel: ** .pyWorkParty(Member).pyLastName: PageGroup type properties are not allowed
.pyPropertyValueFromFedarated(6).pyMessageLabel: ** .pyWorkParty(Member).pyFirstName: PageGroup type properties are not allowed
.pyPropertyValueFromFedarated(7).pyMessageLabel: ** .pyWorkParty(Member): PageGroup type properties are not allowed
.pyPropertyValueFromFedarated(8).pyMessageLabel: ** .pyWorkParty(Provider): PageGroup type properties are not allowed

ERROR localhost|127.0.0.1 [email protected] - com.pega.pegarules.pub.database.AuthorizationException: You are not authorized to open instance RULE-OBJ-CASETYPE PEGAHC-AG-WORK-APPEAL PYDEFAULT #20140709T122751.357 GMT

Steps to Reproduce



In a Pega 7.1.7 system, create a new application built on the 'Appeals & Grievances Layer v7.12 on Pega 7.1' application.

Root Cause



The root cause of this problem is a backward compatibility defect in Pegasystems’ code or rules. Page group type properties are not allowed in the remote case type properties in Pega 7.1.7.

The root cause of the AuthorizationException is missing roles in the AGM:Administrators access group.


Resolution



The issue is resolved through the following local-change.
  1. Create a new ruleset and add it to the AGM:Administrators access group as a Production ruleset. The new ruleset must include PegaHCAGM:07-12-01 as a required ruleset.
  2. Save a copy of the PegaHC-AG-Work-Complaint pyDefault case type rule into the new ruleset and modify the remote case type properties to not use page properties.
  3. Add the AGM:AGCoordinator and AGM:CaseManager roles to the AGM:Administrators access group.

Published January 31, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

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

Pega Community 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
Contact us