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

Question

Question

Validation Warning: "The following attributes produce the same tokens"

asked on June 10, 2015 Show version history

I'm trying to validate a workflow but am getting this warning: 

"The following attributes produce the same tokens: variable1, variable2"

Both attributes are coming from the same Retrieve Laserfiche Forms Content activity. The two associated variables have different names, so I'm not clear what this error is trying to tell me. They should produce different tokens because they have different names.

Both are checkbox multi-value fields on the originator form. 

Any ideas what the warning means, or how I can work around it?

 

Thanks!

1 0

Replies

replied on June 10, 2015

What are the variable names? Workflow names are case insensitive, while Forms uses case sensitive names for its variables. For ex, fields named "Date" and "date" in Forms would be different, but produce the same token in Workflow.

 

1 0
replied on June 10, 2015

They're distinct: "preInterviewDeclineRationale" and "postInterviewDeclineRationale".

0 0
replied on June 10, 2015

Could you post a screenshot of the Choose Fields dialog from Workflow? I can't reproduce it but i'd like to make sure i have the right names for the variables. Or, if you don't want to post it here because it's a public site, have your reseller contact Tech Support and attach it to a case.

0 0
replied on June 12, 2015

Here you go:

0 0
replied on June 12, 2015

Thanks. I'm still not able to reproduce it on the latest versions of Workflow and Forms, but there was one issue fixed for 9.2 that involved checkboxes with "other" option producing this warning even though the names were not identical. If you're on the latest version (9.2.1) already, I'd recommend opening a support case through your reseller so we can take a closer look.

0 0
replied on June 12, 2015

I'm on 9.1, so that may be the issue. I'll remove the other options and see if it works. Thanks for your help!

0 0
replied on June 12, 2015

Yep, that fixed it. I'll see if we can update so I can use the "other" options! Thanks again.

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

Sign in to reply to this post.