ProcessFlow: potential bug in conditional decide statements

Question

question

Laurenz Peleman asked Dec 11, '17 Phil BoBo edited Dec 12, '17

ProcessFlow: potential bug in conditional decide statements

Hello everyone

I noticed some strange outcomes while using the Conditional Decide option in a Decide activity in ProcessFlow. I want to make a decision based on the non-zero value of a token label labelName by setting "token.labelName?" as Condition. This results in the following code

int condition = /** \nCondition: *//***tag:expression*//**/token.labelName?/**/;
if (condition)
	return /** \nIf Condition is true: *//***tag:true*//**/1/**/;
return /** \nIf Condition is false: *//***tag:false*//**/2/**/;

Strangely, while token.labelName is a non-zero value, condition equals 0 and the Decide activity returns the wrong exit. If I replace condition in the if statement by an explicit token.labelName?, the conditional decide is correct.

Kind regards

Laurenz Peleman

Software Version:

Choose One

processflow conditional decide

· 1

Jordan Johnson ♦♦ commented · Dec 12, 2017 at 04:09 PM

I couldn't replicate this issue. Can you post a model that demonstrates the issue?

0 ·

Answer 1 · 2017-12-12T17:04:56Z

Phil BoBo answered Dec 12, '17 Phil BoBo edited Dec 12, '17

What version of the software are you using?

The pick option was fixed in 17.0.6 and 17.1.3. From the Release Notes:

Updated conditional statements in picklists so they aren't put into ints. This allows you to use current.labels["labelname"] directly in a picklist's condition field.

But even despite this change, the code you posted still returns 1 for non-zero label values and 2 for zero label values and non-existent labels.

conditional-decide-labels.fsm (16.3 KiB)

question