I am using the is greater than inequality in my conditions and getting unexpected results. For instance, how can a number be greater than 10000 and less than 5000?
The issue is that when the workflow was originally created and published, the Amount field was text. However, it was later changed to a number field. The problem is that the workflow won't automatically update itself so any tokens that had already been used/set in activities will still reflect the field value as the original format, i.e. text.
You can just remove "Amount" from the initial "Get Field Values" activity and then also remove all %(GetFieldValues_Amount) tokens in all conditional sequence activities, i.e. Tier2, Tier3, etc. Then save or publish the workflow. Now add the "Amount" field back into the "Get Field Values" activity and then add the %(GetFieldValues_Amount) tokens back as well and republish once more. Now the workflow should run correctly.
Are your tokens defined as strings or numbers?
I meant in Assign Token Values where you defined the token:
Oh, I did not create it, I retrieved it from the document.\
Is it a text field?
It is a number field. I might need to contact support, can't see that I set anything up wrong here. 400 is not greater than 10000
It looks like it's being evaluated as string rather than numbers, so, yeah, going through Support and attaching a briefcase with the fields might be easier.
The issue is that when the workflow was originally created and published, the Amount field was text. However, it was later changed to a number field. The problem is that the workflow won't automatically update itself so any tokens that had already been used/set in activities will still reflect the field value as the original format, i.e. text.
You can just remove "Amount" from the initial "Get Field Values" activity and then also remove all %(GetFieldValues_Amount) tokens in all conditional sequence activities, i.e. Tier2, Tier3, etc. Then save or publish the workflow. Now add the "Amount" field back into the "Get Field Values" activity and then add the %(GetFieldValues_Amount) tokens back as well and republish once more. Now the workflow should run correctly.
It is fixed, looks like the Amount field was at one time in String format even though it is a Number field now. I started with an existing workflow as a template to build this workflow, so even though I set the field as a number, it may have been text at the time the previous workflow was built.