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

Question

Question

Assign Token Value Pattern Match Tests just Fine but when the WF runs, the Pattern Match is true when it shouldn't be.

asked on November 11, 2015

I have a client that initiates a WF with a form.  The Workflow monitors a field within that form, that allows for a monetary amount (number with commas or spaces only), the word 'none' and the word 'unlimited'.  When the workflow is started, it enters a conditional expression and within the conditional, there is an assign token values activity that checks if that specific field matches the regular expression [\d, \,]*.  When we test the expression with the words 'none' or 'unlimited' it comes up with no match, which is how we want it to work.  When we run the workflow and it encounters the word 'none' the conditional processes as true and says 'none' matches the regular expression [\d, \,]*  .

Is this a known issue with Assign Token Values, where when you test it works just fine, but an actual run it does not work how it should?

I hope I explained this well enough, please ask for clarification if I did not.

Thank you!

0 0

Replies

replied on November 11, 2015

Your regular expression looks for zero or more numbers and commas, so "none" would match. Try changing the * to a + to indicate that you are looking for at least 1 digit.

0 0
replied on November 13, 2015

Thank you, that helped clear up the issue!

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

Sign in to reply to this post.