When Attempting to Edit a Workflow Setup Condition Trigger Element, a Text String Value Can No Longer Be Entered, the Field Will Only Accept Whole Numbers, Whereas Previously a String Could Be Enetered (Doc ID 2993810.1)

Last updated on DECEMBER 19, 2023

Applies to:

Symptoms

After a Unifier environment was upgraded to Unifier version 23.10 when attempting to Edit a Workflow Setup Condition Trigger Element, a text string value can no longer be entered, the field will only accept whole numbers. In older Unifier versions back to at least 23.7 a text string could be entered for the value of this workflow conditional. For example, if "DP_Element1" (data picker for the business process) = 'StringABC', then go to a specific action. However, now when creating a new workflow and a new workflow setup, the only values that can be entered in the field are numbers. Example: "DP_Element1" can be "12345" but can no longer have a text string entered such as "StringABC".

EXPECTED BEHAVIOR
----------------------------
When creating a new Workflow Setup, the expectation is that a conditional can be created using the data picker and a string value can be entered and not just a numerical value.

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

1. Login to the Unifier environment.
2. Navigate to Properties > Admin Mode > Setup > Business Process > BP1 > Workflow Setup > Open Setup "ExistingWorkflow".
3. In the "Workflow Setup" window click on the "Workflow Condition1" > Under "Trigger Element(s)" note "DP_Element1", the Value is currently "StringABC". So Unifier used to allow a string here.
4. Select the Trigger Element and try to edit the Value, only numbers can be entered such as "12345" and no strings > Close this Workflow Setup window.
5. Click New > Create a new Workflow called "NewWorkflow" (This is a copy of "ExistingWorkflow" with no changes) > Select the same "Workflow Condition1" > Trigger Elements, click on/open "DP_Element1" > So even int a new Workflow Setup, this field no longer supports strings, only numbers/integers can be entered.

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.