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

Question

Question

Workflow doesn't resolve the token if its value is blank

asked on October 1, 2015 Show version history

We have a form with a collection. Upon submission, the form is first stored in the repository with a basic identifier, and then a workflow is invoked which grabs the rest of the values from the process.

The workflow retrieves the values from the form. Single values are assigned to metadata fields. Collection values are assigned iteratively inside a for-each loop.

We noticed that for one of the fields, if the multi-value token's value at that iteration is blank, workflow puts the token itself into the field. Screenshot below:

Both Estimated Return Date and Estimated Daily Rate fields are part of the collection. For the second item in the collection, they are left blank. You'll note that the date field behaves correctly, but the currency field contains the token itself as the second value, when it should also be blank.

Is this a known issue? We are on the latest version.

0 0

Answer

SELECTED ANSWER
replied on October 1, 2015

This is a known issue in 9.2. It's fixed for version 10.

1 0

Replies

replied on October 1, 2015

This is why I love Laserfiche. smiley

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

Sign in to reply to this post.