You are viewing limited content. For full access, please sign in.

Question

Question

Conditional Decision In Workflow Giving Inaccurate Results

asked on March 14, 2016

I am trying to run a conditional decision that would take different actions based on if the value is under a thousand, between 1,000 and 999,999.99 and over a million.  For some reason the conditional decision is failing on values over a million.

In this first screen shot you will see where it accurately states that 1,729,044.44 is under 1,000.00

The next condition is if the value is over a million, which I suspected the value of 1,729,044.44 would report as true, but it didn't

My last condition checks to see if the value is between greater than 1,000 and less than 999,999.99 (initially I used a between, but that didn't work either) and this time it reported 1,729,044.4 is less than 999,999.99

Does anyone have any advice on how to get Workflow to do the math on this condition correct?

 

 

0 0

Answer

SELECTED ANSWER
replied on March 14, 2016

Hey Jeff,

Are all the tokens you're using numbers? Sometimes Workflow comparisons can give weird results if you start comparing different types. If they're not you can use assign token values to cast it as a certain type.

0 0

Replies

replied on March 14, 2016

As far as I am aware it is comparing the same type. 

 

I broke the workflow out into several steps that I thought would be overkill to confirm what the conditional decision is being ran on..

 

1)A pattern match finds the number

2)It assigns it to a filed value

3)That field value is retrieved so it can be used in my conditional decision

 

I will add a step for assign token values to make sure that the value being compared is a number.

0 0
replied on March 14, 2016

Is the field you're using a text field or a number field?

0 0
replied on March 15, 2016

I think it is a text field because the data is coming from retrieving a PDF text.  

0 0
replied on March 15, 2016

Assigning a token and using "number" worked!  This resolved my issue.

 

Thanks!

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.