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

Question

Question

Condition Rule Not Working As Expected

asked on November 24, 2015

I am having an issue getting some conditions on a Conditional Decision to work as expected.  For one branch of our workflow, I added a Conditional Decision that if the document being processed is in a certain Document Type, has a Batch Number, and either the Check Number or Check Amount fields are empty, it should send the document to a manual review folder.  Else it files away the document.  I'm doing this by having an "All conditions are true" for the Document Type and Batch Number, then a "If any of these conditions are true" for either the Check Number or Check Amount being empty.

The problem is that documents that should bypass it because they have both Check Number and Check Amount values are going to the manual review folder.  I would expect that to occur only when one or both of those fields has been left blank.  I've tried changing around the conditions a couple of different ways, but the documents are still all going to the manual review folder, even when they have both check numbers and check amounts.

Can anyone see what is going wrong based on the conditions below?

Thank you very much for your help.

0 0

Answer

SELECTED ANSWER
replied on November 30, 2015

I can't reproduce it. If both the Check Number and the CheckAmount have values, then the document goes through the second branch.

Could you post a screenshot of the condition evaluation for this case?

Any chance you have the wrong field? You are referring to "Check Amount" in your description, but the condition is using a field called "CheckAmount".

0 0

Replies

replied on November 24, 2015

Look in the instance details to see how the conditions were evaluated.

0 0
replied on November 24, 2015

That is the issue I'm coming across.  The document is going down that path, both in results and looking at that particular instance, even though it should not be.  My document has both a Check Number and Check Amount (verified by both looking at the document and tracking that as a token in the database in some tests).  Because it has both values populated on the document, I would not expect it to match the condition that one of those fields has to be empty to go down that path. 

0 0
SELECTED ANSWER
replied on November 30, 2015

I can't reproduce it. If both the Check Number and the CheckAmount have values, then the document goes through the second branch.

Could you post a screenshot of the condition evaluation for this case?

Any chance you have the wrong field? You are referring to "Check Amount" in your description, but the condition is using a field called "CheckAmount".

0 0
replied on December 1, 2015

Thank you, Miruna.  It looks like the "Old Stuff" troll struck again.  There are two fields for Check Amount in our system, one with the space and one without, which were set up for two different templates in the past.  The workflow was looking at the wrong one.  Thank you for your assistance!

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

Sign in to reply to this post.