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

Question

Question

Is a constraint field with hyphens not considered empty to workflow?

asked on March 11, 2015

Hi there, 

 

We've got a client that has a roll number field with a constraint of \d\d\d\d-\d\d\d-\d\d\d-\d\d\d\d\d

 

With the hyphens in there, if a document does not have the roll number filled in, it shows up in the field as:

   -   -   -     

I believe workflow is confused with this because it seems that it thinks the field is not empty. We have a workflow that is linking documents to other documents in the repository that have the same roll number in common. With trying this out, it creates thousands of links under one document and there is nothing filled in on the roll number.  We have the conditional sequence to only run if the roll number is not empty. So we also tried matching a regular expression instead, but both are giving us the 3000 links. 

 

What am I missing or doing wrong? 

0 0

Replies

replied on March 11, 2015

The hyphens are for display in the Client, they're not the field value. What exactly is the problem you're seeing in Workflow? Have you looked at the condition evaluation?

0 0
replied on March 11, 2015

Thanks Miruna, I actually had the wrong field in the search criteria so it was bringing back all results. I've got it working now, thanks for your reply. 

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

Sign in to reply to this post.