CreatePolicy Attached Business Rule (ABR) With Non-Segment Role Creation Failure Using Collections (Doc ID 3056868.1)

Last updated on NOVEMBER 01, 2024

Applies to:

Symptoms

On : 11.3.0.30 version, Client Activity

ACTUAL BEHAVIOR
---------------
Usage of a Collection in the Non-Segment Roles section of CreatePolicy to create Roles results in the creation of the Roles without passing the associated table column (like StatusCode) or field values.


EXPECTED BEHAVIOR
-----------------------
With a Transaction using the CreatePolicy ABR, when using a Collection in the Non-Segment Roles section to populate table column/field values.
The expectation is that the Role will be generated using the Client GUID in the key of the Collection and the associated table column/field value will be populated with the paired value of the Client GUID key.


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Create a Transaction with the CreatePolicy ABR.
2. Within the Transaction, create a Collection with valid Client GUIDs as the keys and non-default values as the paired value.
3. Use this Collection in CreatePolicy within tags.
4. Process the Transaction.
5. Navigate to the New Policy ->Role Screen - Verify whether the table column/field chosen has the non-default value sent through the Collection.

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.