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

Question

Question

Pattern matching output not passing as field value

asked on March 4, 2015 Show version history

I have quite a silly situation where I have a simple test workflow, which does the following:

- Read hospital number field value (which should be something like this 123456789

- Apply the pattern matching to divide the hopstial number in to three part, part1: 123, part2: 456 and part3:789.

- Pass values back to the hosptial number field like this: part1 part2 part3 (all tokens with space in between).

I kind of not make this working? Pattern matching returns right values while testing.

What am I missing here?

WF.png
WF.png (21.95 KB)
0 0

Answer

SELECTED ANSWER
replied on March 4, 2015 Show version history

Got it working now :)

I am now creating a multi value token and then extracting all three indexes individually.

WF 1.png
WF 2.png
WF 3.png
WF 1.png (9.62 KB)
WF 2.png (18.99 KB)
WF 3.png (18.9 KB)
0 0

Replies

replied on March 4, 2015

Seems like an issue with my pattern matching.

Below gives the right results for First part.

WF.png
WF.png (23.56 KB)
0 0
replied on March 4, 2015

What's not working about it?

0 0
replied on March 4, 2015

If the input document field Hospital Number has value: 123456789, then for the very first example at the top, it doesn't return anything. ('AssignField Values' doesn't assign any value to the field, though I am passing all three tokens from Pattern Matching). 

But for the second example above, it does passes the first value but doesn't pass the rest two values?

 

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

Sign in to reply to this post.