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

Class Structure design considerations

SA-25514

Summary




When a New Application is created using Pega wizard, the resultant ruleset stack in operator profile looked like the below format(From top to bottom) 
  1. IMPLEMENTATION level rulesets
  2. DIVISION level rulesets
  3. UNIT level rulesets
  4. ORG level rulesets
  5. FRAMEWORK level rulesets
  6. PEGA rulesets 



However the expected/correct sequence of the ruleset stack should be like the below stack 

  1. IMPLEMENTATION level rulesets 
  2. FRAMEWORK level rulesets 
  3. UNIT level rulesets
  4. DIVISION level rulesets
  5. ORG level rulesets
  6. PEGA rulesets 


.

Error Messages



Not Applicable


Steps to Reproduce

  1. Click on Create a New Application 
  2. Select framework and implementation before creating application 
  3. Provide the names of Organization, Division, Unit under advanced settings
  4. Save the configurations 
  5. Generate the application 
  6. Observe the user profile for the ruleset stack once the application is created 


Root Cause



An issue in the Pega application

Resolution



A defect in the pega system which will be addressed in fourth coming version of Pega

however there is a local-Change which can be implemented to get the expected ruleset stack


Local-Change:

Once the ruleset stack is generated  After the application is created update the  application ruleset by 

a) Setting the framework as the build on application and under the application ruleset stack mentioned the implementation rulesets






b) Expand the framework ruleset and set org , div , unit rulesets in respective order
 

Published July 29, 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