My Oracle Support Banner

A Business Process Workflow Doesn't Work Based On Trigger Conditions Configured; Instead the Workflow Defaults To the Resolving Condition (Doc ID 2958567.1)

Last updated on JULY 14, 2023

Applies to:

Primavera Unifier Cloud Service - Version 9.7 and later
Primavera Unifier - Version 9.7 and later
Information in this document applies to any platform.

Symptoms

ACTUAL BEHAVIOR:

A Business Process (BP) workflow does not work based on the Trigger Element(s) configured. The workflow defaults to the resolving condition instead of the intended step or condition.


EXPECTED BEHAVIOR:

The BP workflow process should work as expected based on the Trigger Element(s) configured.

The issue can be reproduced at will with the following steps:

  1. Log in to Unifier.
  2. Navigate to Project_ABC > BP XYZ Node > Open and Accept the BP_XYZ record > Select the value e.g. 'Option_1' from a conditional routing field (Data Element) on the form > Send > Select Workflow Action to the next step e.g. Approve.
  3. Note: The conditional routing field above is configured as a Trigger Element within the BP Workflow Setup.
  4. Observe that the BP_XYZ record defaults to the resolving condition instead of the expected step or condition based on the value 'Option_1' selected on the form.

Changes

 

Cause

To view full details, 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 a vibrant support community of peers and Oracle experts.