I have been working on a workflow and had configured 2 tokens in a Pattern Matching activity. The second token in the activity had its input value set to the first token. When I ran the workflow the 2nd value was never populated. I then separated them out into their own Pattern Matching activities and had the same result. I eventually configured the 2nd one to go off the document name and it populated the value. Is this a bug?
Question
Question
Can't Create a Pattern Match Token from Another Pattern Match Token?
Replies
What's the exact version of Workflow you are using? Can you provide a screenshot of the workflow rule and how the Pattern Matching activity is configured?
I ran a generic test and wasn't able to recreate the issue. See below:
I have changed the workflow so I could get it up and going, but really it was pretty similar to the one below, with the exception that it was setting the input value from another pattern matching token.
Here is what the token setup of the one that was feeding the one above looks like:
Workflow Designer 9.2.0.167
So you are getting the "Form Date" based off of the entry name using the pattern
[^-]*
and then you are getting the "Form Year" from the "Form Date" using the pattern
^\d\d\d\d
Can you provide a sample entry name that we can test with?
2015/04/14 - Parent Compact - Smith, Blake
I'm not able to recreate the issue in Workflow 9.2.0
Please open a support case with your reseller if you'd like to further investigate the matter.