Can a Data Type be delegated or not?
I've created a production ruleset and added it to an appropriate access group and the application. I have all the privileges I need and managed to set up delegation for a decision table and a value map rule. However, I am unable to set up delegation for a data type. I get this error:
The documentation references that I found appears to indicate that this should be possible. The information I found on the community site is confusing and perhaps dated. So I would really like a clear, unambiguous answer on this: can a data type be delegated or not? If yes, then how? I get that a data type is un-versioned and therefore it probably cannot be moved/copied to a production ruleset, so what else is needed to get it working?
***Edited by Moderator: Pallavi to update SR Details***
Accepted Solution
Ernst & Young
ZA
I've gotten the following response from Pega Support:
Quote:
SME(Matt) has investigated the issue after our call and found that it's a BUG which will be fixed in Pega 8.3.4 patch release.
RCA: Data type delegation is dependant upon the existence of a Rule-Access-Role-Object (RARO) for the delegated data type. When delegating to an accessgroup with the same roles the ruleset of the RARO the code attempts to naively update the RARO.
Updating the RARO will determine if the Ruleset of the RARO is unlocked. If the ruleset is locked then the code will determine that a new RS should be selected. But the RARO cannot be moved to a new ruleset.
For now we suggest the following workaround in order to fix the issue.
I've gotten the following response from Pega Support:
Quote:
SME(Matt) has investigated the issue after our call and found that it's a BUG which will be fixed in Pega 8.3.4 patch release.
RCA: Data type delegation is dependant upon the existence of a Rule-Access-Role-Object (RARO) for the delegated data type. When delegating to an accessgroup with the same roles the ruleset of the RARO the code attempts to naively update the RARO.
Updating the RARO will determine if the Ruleset of the RARO is unlocked. If the ruleset is locked then the code will determine that a new RS should be selected. But the RARO cannot be moved to a new ruleset.
For now we suggest the following workaround in order to fix the issue.
- Cleaning up RARO
- RARO objects have likely been created in a number of rulesets.
- It is advised that the client delete the RAROs that were created. They can look for RAROs for the data types they attempted to delegate
- Cleaning up System-User-MyRules instances
- Find DelegateAG type instances that reference the data type and remove the reference to the data type(s) that were delegated
- Ensure that a ruleset is unlocked when delegating data types
- The ruleset cannot be a branch ruleset.
- I would be a good idea if you had one ruleset at the top of your stack open for this when you delegate.
- Ensure that that ruleset is open when delegating
Unquote.
Pegasystems Inc.
US
Does this error occur when you open the Data Type and select Actions > Delegate or were you using different steps?
Updated: 14 Jun 2021 7:38 EDT
Pegasystems Inc.
IN
Please find the below articles which might be helpful.
https://community.pega.com/support/support-articles/error-occurs-when-delegating-data-type-rules
https://collaborate.pega.com/question/record-non-versioned-and-can-not-be-moved-different-ruleset
Ernst & Young
ZA
No, not helpful at all. As I said I was successful in setting up other delegations, just not for a data type. I have an unlocked production ruleset, all the privileges I need etc.etc.etc.
Updated: 30 Apr 2020 5:37 EDT
Ernst & Young
ZA
There is an SR for this: SR-D94598 and it is in status Pending-Engineering. It turns out that in my case the problem arises when I try to delegate the same data type again with another Access Group. Apparently there is some issue with deleting or modifying the delegation once it exists.
Accepted Solution
Ernst & Young
ZA
I've gotten the following response from Pega Support:
Quote:
SME(Matt) has investigated the issue after our call and found that it's a BUG which will be fixed in Pega 8.3.4 patch release.
RCA: Data type delegation is dependant upon the existence of a Rule-Access-Role-Object (RARO) for the delegated data type. When delegating to an accessgroup with the same roles the ruleset of the RARO the code attempts to naively update the RARO.
Updating the RARO will determine if the Ruleset of the RARO is unlocked. If the ruleset is locked then the code will determine that a new RS should be selected. But the RARO cannot be moved to a new ruleset.
For now we suggest the following workaround in order to fix the issue.
I've gotten the following response from Pega Support:
Quote:
SME(Matt) has investigated the issue after our call and found that it's a BUG which will be fixed in Pega 8.3.4 patch release.
RCA: Data type delegation is dependant upon the existence of a Rule-Access-Role-Object (RARO) for the delegated data type. When delegating to an accessgroup with the same roles the ruleset of the RARO the code attempts to naively update the RARO.
Updating the RARO will determine if the Ruleset of the RARO is unlocked. If the ruleset is locked then the code will determine that a new RS should be selected. But the RARO cannot be moved to a new ruleset.
For now we suggest the following workaround in order to fix the issue.
- Cleaning up RARO
- RARO objects have likely been created in a number of rulesets.
- It is advised that the client delete the RAROs that were created. They can look for RAROs for the data types they attempted to delegate
- Cleaning up System-User-MyRules instances
- Find DelegateAG type instances that reference the data type and remove the reference to the data type(s) that were delegated
- Ensure that a ruleset is unlocked when delegating data types
- The ruleset cannot be a branch ruleset.
- I would be a good idea if you had one ruleset at the top of your stack open for this when you delegate.
- Ensure that that ruleset is open when delegating
Unquote.