E1: ORCH: Nested Rules are not Working as Expected when Using Iterate Over
(Doc ID 2678594.1)
Last updated on JUNE 11, 2020
Applies to:JD Edwards EnterpriseOne Orchestrator - Version 9.2 and later
Information in this document applies to any platform.
Customer created an orchestration to import a csv file for multiple records where they have nested rules defined to act on the data according to one field.
When they test with 1 record with Mode A = Add , then the orchestration does not detect this.
The first check in the Orchestration is a verification for C= Change
When the rule result is false then the next rule will check for A but it is not detecting that it is A for ADD
When there are 2 records with Mode A = Add , then the orchestration doesn't detect the first record but only the second one.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document