Question
IBM
CN
Last activity: 28 Feb 2023 4:13 EST
A when rule can not be accessed by an access group
Hi, may kindly suggest what's the possible reason of below issue?
We have a case type that can be run normally under a user of a access group A, however it reported an error under a user of access group B.
The error msg like "A processing error has occurred ... Object key... Stack Trace"
As traced, seems it's caused by a when rule used by a attachment category is not accessible (by access group B), but not sure.
Per your experience, what's possible reason? Thanks.
Bits in Glass
IN
@MaxonL16591286 Can you check the particular attachment category rulefor any privilege if that privilege is available for Access group A and not access group B. If that is the case, that could be the cause for the issue.
IBM
CN
Hello, should not be this reason.
Even I hardcode the when rule to always true, the problem still exist. Per trace, seems Pega try to locate the when rule in base class, however the when rule is defined in case type class.
Also, if I call the when rule directly from a DT defined in case type class, it's normal, no issue found.
So the issue can be refined as below. Appreciate kindly help soon as we need solve it urgently. Thanks!
///
Under some access groups, a when rule used by a attachment category is inaccessible when Pega need to call it for the attachment category access. Seems the direct reason is Pega try to locate this when rule in base class which does not exist. The when rule is defined in case type class.
Under other access groups, this issue does not happen, every thing is normal.
///
IBM
CN
f.y.i, we save the when rule to @baseclass can bypass this issue.
However, of course, it's just a temporary bypass.
Looking forward answer, thanks.
Pegasystems Inc.
IN
@MaxonL16591286 I remember going with the same approach in one of my scenarios as well. Should be a good enough solution.
IBM
CN
Does "good enough solution" refer to "save the when rule to @baseclass"?
We don't expect that. We would like to know why some AG encounter such issue, what's the root cause? Is it related to some roles (diff roles under diff AG)?
Taking this solution will let the case type specified when rule save in so general common class : baseclass.
Pegasystems Inc.
IN
Please raise a Support Request with log details and someone should be able to help you with the query.
On a high level it just trickles down to the concerned when rule not being picked in the rule resolution for the AG.