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

Discussion

Discussion

XPath Expression Tokens are nearly impossible to reference in Workflow 10.4.1 and 10.4.3

posted on September 23, 2020

I have been having trouble with my workflow all week. Each time I narrow the problem down it is an improper reference to a token. Each time I fix the reference, it reverts back again breaking the workflow, just like a ghost in the machine.

I finally determined what causes it, any change to the XMLPath Expression causes references to the tokens from other activities to change. All references to your XMLPath activities reference the last token instead of what you defined.

Here is an example of where I want to get the DocumentID, but after updating the Expression, it wants to get the DocumentTypeName. Why is this? 

I backed up the workflow and moved it from the 10.4.3 customer environment to my local 10.4.1 dev environment and the exact same thing happens.

0 0
replied on September 24, 2020

Hi Chad,

We were able to reproduce this issue and it matches one we already have on file. We've added the information you provided to the bug ticket. Its Workflow bug ID is #209685 so you can check future release notes. 

 

Root cause appears to be a problem with how we handle copy/pasted tokens in the ReadXML activity. It may be the case that if you create each token in the ReadXML activity without using copy/paste then this issue will not occur. If you're able to reproduce this issue using ReadXML tokens that are/were not copied/pasted in the ReadXML activity, then please let us know, as that may be a separate concern from what we've found so far.

 

In any case, we're happy to hear you found a workaround, and thanks again for reporting.

 

 

 

 

2 0
replied on September 24, 2020

Oh thinking back, all tokens were a paste of the first token just to bring over the general configurations so yes that seems right. I tested with a non-copy pasted one that has 2 tokens and it does not happen.

2 0
replied on September 24, 2020

Thank you for confirming the behavior.

1 0
replied on September 24, 2020

Ok, I have a successful workaround now. I had multiple XPath activities each with multiple tokens, now I keep it down to a single token per XPath activity and it prevents any token references throughout the workflow from changing, since they have nothing to change to. It sure was confusing me all week though, I was finding and fixing the same reference issues over and over even though I was the only one working on the workflow.

1 0
replied on September 24, 2020

The issue looks to be caused by copying tokens within the same activity.

0 0
replied on September 23, 2020

Hi Chad, 

Thanks for reporting. Dev is looking into this and will file a bug if they can reproduce the issue. 

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

Sign in to reply to this post.