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

Run does not execute on selecting Run option from BIX extract

SA-88841

Summary


The hasAdminRole When rule performs an authorization check on the Rule-Admin-Extract class. On selecting the Run option from the Business Intelligence Exchange (BIX) extract, the Run option does not execute.

The check is performed to determine if the user has the PegaRULES:SysAdm4 role or if the name of user's access group is pxThread.pxCurrentApplicationName + ":Administrator".



Error Messages



Not Applicable


Steps to Reproduce

  1. In a Pega system with Pega-BIX:07-10-19 ruleset, create a user with the PegaRULES:SysArch4 role. The user must not have the PegaRULES:SysAdm4 role and the access group name must not be pxThread.pxCurrentApplicationName + ":Administrator".
  2. Create an Extract rule.
  3. Execute the rule.


Root Cause



This behavior is as per Pega product design: BIX
This issue was determined to be a product enhancement request.



Resolution



Here's the explanation for the reported behavior:

Currently, the access role validation, in the hasAdminRole rules, only checks for the access role name. The validation does not support privilege checks. This current behavior of BIX either validates the access role name for PegaRULES:SysAdm4 or checks if the users access group name is pxThread.pxCurrentApplicationName + ":Administrator".

An enhancement request, FDBK-62136 is created for consideration by Pega Product Management to specialize the hasAdminRole When rule.
Suggest Edit

Published December 2, 2021

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

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