Incorrect Option Text For Combo Fields Of Activities Spawned From Requirements (Doc ID 2465672.1)

Last updated on OCTOBER 26, 2018

Applies to:

Symptoms

On : 11.1.0.0 version, General

ACTUAL BEHAVIOR
---------------
Incorrect option text for combo fields of activities spawned from requirements

When a requirement spawns an activity, any combo fields on the spawned activity do not get the correct option text. Thus, the entry fields tab of the processed activity does not accurately reflect the real value that was spawned in.

Scenario 1 works properly:
- GoodOrderCheck transaction spawns Decline transaction
- It uses a TYPE=VALUE, DATATYPE=TEXT math variable to populate a spawn field called ApplicationInfoCode
- Decision reason is a combo box with options driven by an AsCode SQL
- The option text is correctly populated
- The Entry Fields tab of the processed activity displays the correct description for the corresponding code value

Scenario 2 does not work:
- Milliman Request transaction spawns Decline transaction
- It uses a TYPE=VALUE, DATATYPE=TEXT math variable to populate a spawn field called DeclineReason
- Decision reason is a combo box with options driven by an AsCode SQL
- The option text is NOT correctly populated
- The Entry Fields tab of the processed activity DOES NOT display the correct description for the corresponding code value

See text files and screen shots in attached zip file.


EXPECTED BEHAVIOR
-----------------------
 Option text of an activity spawned from a requirement should display the description corresponding to the code value.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Configure a transaction with a combo field with options driven by an ordered query against AsCode
2. Configure a requirement to spawn the transaction via SpawnActivities, populating the combo field with any of the code values from the query except the first one in the list (because this seems to be the default that is used)
3. Trigger the requirement to spawn the activity
4. Process the activity
5. Query AsActivity field and confirm that the code and option text do not match
6. View the Entry Fields tab of the processed activity and confirm that the code and option text do not match

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, The app falsely suggests to the user that the transaction operated on an incorrect value.

Cause

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