Specific Approval Sequence Runs as Parallel when the Flow Dictates it should be a Series

(Doc ID 2006991.1)

Last updated on NOVEMBER 07, 2017

Applies to:

Oracle BigMachines CPQ Cloud Service - Version 2013 Winter to 2015 R2 [Release 2013 to 2015]
Information in this document applies to any platform.


Upon inspecting all the reasons, the approval workflow does not follow the expected behavior or design. It may be limited to this specific workflow below:

Note: The workflow above is in the simplest form. You may need to remove sibling or other child nodes to check if your approval flow follows this design.

Expected Behavior:

Actual Behavior:

Simple Condition 3, Simple Condition 6, and Simple Condition 7 require an approval and are in parallel with each other. Notice that the actual behavior bypasses Simple Condition 5 even though this is required in sequence and returns false.

Other Observations:


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms