DNA User Guide › Audit Menu–Policy Compliance Check › Business Process Rule Concepts

Business Process Rule Concepts

A Business Process Rule (BPR) expresses business, provisioning, or security constraints as a logical condition that can be applied to the entities and links in a CA RCM configuration. Consider the following example:

<Purchasing> forbidden to be <Subcontractor Payments>

You can apply this statement to a CA RCM configuration to help ensure that workers, with privileges to order stock from subcontractors, do not have roles with privileges to issue checks to those subcontractors.

Typically a BPR is defined by specifying the following information:

• The type of rule–CA RCM provides a broad range of rules that let you examine and compare various entity values. The role type used in the example mentioned previously is Restrict access of users to roles by role access. This type of rule restricts the roles a user can have based on other roles they already have.
• The logical condition–in our example, users with certain roles are forbidden from having other roles. But you can also use this type of rule to allow or require users with certain roles to have other roles.
• Data sets and limit values–in our example, we define a set of roles related to purchasing functions, and another set of roles that grant payment privileges.

A Business Policy is a set of BPRs. This policy (saved as a .bpr document) exists independently of any specific configuration. The rules that comprise the policy can be adapted and applied to any CA RCM configuration to verify its logic, integrity and compliance with policy.

More information:

Business Process Rule Types