Question

Forms - Troubleshooting Conditions

Forms

Updated May 17, 2021

asked on May 12, 2021 • Show version history

How do we troubleshoot a condition in forms if we know that it is true but evaluating to false?

For example I have a customer form with a conditional decision (exclusive gateway) that has a default path and a /dataset/_initiator="Workflow" path. \

The history shows that it followed the default path even though the initiator of the process (Workflow Start Event) shows Action by "Workflow".

In the Workflow designer I would go to the Conditions tab to look how it could possibly say
[False] Process Initiator (Workflow) = Workflow

Since this statement can not be False.

0 0

Answer

SELECTED ANSWER

replied on May 12, 2021 • Show version history

Are you sure the condition is correct? In my processes, it shows as Started by "Workflow" in the instance history but I think that is more like a display name.

In the actual gateway my conditions are always as follows:

/dataset/_initiator="_workflow"

2 0

replied on May 13, 2021

Note that you can change the user in Invoke Business Process on the Workflow side:

2 0

Replies

replied on May 12, 2021

Forms doesn't have a condition expression evaluator like workflow does. One thing you could try is adding a field on your form, setting the default value to /dataset/_initiator, and seeing how it appears in the Monitor page, variables view. The Started by column in action history may have some display name "Workflow" over the real value under the hood that the gateway is using.

2 0

replied on May 12, 2021

Jared is right. What I did to find the "actual" value is that I added a test form with a field that defaults to the initiator user name.

Then, I created a user task assigned to myself with the same form so I could see what the "actual" value was after workflow invoked the process.

I don't think the value would show up until a user task or something because as far as I know default values aren't populated like that when workflows starts a process.

2 0

replied on May 17, 2021

The _ was the character we were not seeing anywhere in the logs. Adding the _ did the trick! This is why the conditions tab is so helpful in the workflow designer.

Thank you!

0 0

You are not allowed to follow up in this post.

Question

Question

Forms - Troubleshooting Conditions

Answer

Replies

Sign in to reply to this post.