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

Question

Question

Workflow Validation Bug?

asked on September 2, 2022 Show version history

I have a 2 workflows that when I open them in the Workflow Designer (10.4.2.246) and click the Validate button, the validation works correctly. I can see the progress window run through all the different activities to validate them.

If I click it again, it comes up for a second or two and then disappears without fully validating the workflow.

I can verify this by also removing a value from the ‘Retrieve Business Process Variables ’ activity in which I know that token is used in a Find Entry activity further in the workflow. I can remove the variable, validate the workflow and the first time it works.

If I validate it again, it does not come back with anything wrong.

I am guessing this is a bug and hope it is fixed in a newer version of Workflow.

0 0

Answer

APPROVED ANSWER
replied on October 10, 2022

Laserfiche was able to identify and narrow down this behavior. It appears to be if an Assign Field Value Activity has a list type field, the validation will fail. This has been logged as bug 398178. As for now it seems the work around is clicking into that Assign Field Value activity and then just clicking "Okay".

1 0
replied on April 17, 2023 Show version history

Any update on when a fix for this will be released? It really slows down our development time with Workflow and is still present in version 11.0.2209.835.

0 0

Replies

replied on September 2, 2022 Show version history

Workflow 11's List of Changes says:

  • Fixed lots of small bugs.

This might be one of them.

Workflow 11 Update 1 also fixes lots of small bugs, though this one doesn't explicitly appear on the list.

If you happen to have a Workflow 11 test server (or an upgrade a dev/test server to Workflow 11), I'd do that and see if the issue persists. If it does, please have your SP open a support case to report the potential bug that references this Answers post and includes copies of the workflow process (wfi) files that you've reproduced the issue with. Please also reply back here with any findings so it's more readily searchable for others.

The Workflow team is stretched pretty thin at the moment, so if this is still a bug in Workflow 11, any testing you're able to do yourself dramatically raises the odds of it getting on the "small things to fix" list instead "small things to investigate if/when time permits" backlog.

Thanks!

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

Sign in to reply to this post.