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

Question

Question

Assign Field Value Warrning after 10.2

asked on March 23, 2017

After upgrade to 10.2 we seems to have a strange warning telling us that the value specified may not be valid anymore. This template and values haven't changed and nothing I tried makes the warning resolve itself. I have verified that the value is correct, re-saved the template. Any way we can get rid of this issue? Thanks!

There was a similar problem posted in January 2016: https://answers.laserfiche.com/questions/89940/Field-issue-in-Workflow-and-Admin-Console#117682

0 0

Replies

replied on March 23, 2017

Thought I would post as well as we are also seeing this.  We have some client workflows that display that every time on verify or publish.  No matter what we do template/refresh wise it does not go away.

1 0
replied on March 23, 2017

Are the fields being referenced list fields that are using tokens when assigning the value? If so, then this is an issue we're aware of and will be fixed in the next release of Workflow. For now, you can ignore the warning and "publish anyway" as the workflow should still run correctly.

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

Sign in to reply to this post.