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

 BOYINA VISWANTH (BOYINAVISWANTH)
Centene
Project Lead Application Software Engineer (Test Automation)
Centene
US
BOYINAVISWANTH Member since 2018 3 posts
Centene
Posted: Mar 13, 2019
Last activity: Sep 13, 2019
Posted: 13 Mar 2019 5:03 EDT
Last activity: 13 Sep 2019 15:37 EDT
Closed

Can any one please expalin why organisation and Framework are interchanging in Ruleset Stack?

According to Situation Layer Cake The Hirerarchy is

1.Personal Ruleset

2.Delegated Ruleset

3.Branched Ruleset

4.Application Ruleset

5.Implementation Ruleset

6.Framework Ruleset

7.Organisation Ruleset.

But after creating an Framework and an Implementation(on that Framework that we created before) why Pega is not following the same structure i.e.,

1.Personal Ruleset

2.Delegated Ruleset

3.Branched Ruleset

4.Application Ruleset

5.Implementation Ruleset

6.Organisation Ruleset

7.Framework Ruleset

Can any one please expalin why organisation and Framework are interchanging?

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

To see attachments, please log in.
Low-Code App Development

Posted: 5 years ago
Posted: 13 Sep 2019 15:37 EDT
Mike Townsend (MikeTownsend_GCS) Director, Technical Support, Customer Service
Pegasystems Inc.
US

Hello,

I would need to see your application rules and how they are defined. Are you referencing any of those rulesets listed on the production ruleset list under Advanced? In my experience, that is the most common source of rulesets being in unexpected places in the stack.

Thanks,
Mike
 

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