'OC' decision rules can create several sub-levels, which means that the decision maker does not see what is being decided (4331177)

Scenario:

The following system roles are configured:

• E1 - with the additional property P1
• E2 - with the additional property P2
• E3 - with the additional property P3

E1 is available in the IT Shop with the decision guideline: "Compliance checking simplified".

ComplianceRule r1r2 checks whether an Employee has Eset with P1 and P2. The exception decision maker is GRUBY.

ComplianceRule r1r3 checks whether an Employee has Eset with P1 and P3. The exception decision maker is MM.

An Employee already has E2 and E3.  This Employee orders E1 and the rule violation for r1r2 and r1r3 occurs.

The CR step only indicates that at least one compliance rule has been violated, but not which other rules, and the decision maker does not know which step they are deciding on.  The decision maker must always examine the entire situation.

This is a product defect (34861).

WORKAROUND

None

STATUS

This will be fixed in a future release of the product. If you require this immediately corrected, please contact Support for a hotfix referencing the defect ID 34861.