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

Question

Question

Constraints and custom errors

asked on November 6, 2013

Hello,

I have a customer who wants to be able to have a custom error thrown in Quick Fields per a constraint of 7 digits. This is easily accomplished through the Metadata Management. However, when the users run a QF session that populates the selected field with the constraint, it will not throw an error for that field if the field is blank/empty. If there are characters in that field, and they do not meet the constraint criteria, an error is thrown- but the blank fields are allowed to file and store as if they do not have any issues. I set the field to required, but because of this- when users are scanning the documents into LF initially, they have to populate the field with something- thus defeating the purpose of QF. This is not an option. 

 

Is there a way I can set an error to occur in QF should a field be blank short of setting the field to be required?

 

Thanks, 

Hunter

0 0

Answer

APPROVED ANSWER SELECTED ANSWER
replied on November 6, 2013

Actually, you can set the field as required and give it a custom constraint in the QF session itself (from the Manage Metadata dialog in the document class) rather than making it required in Laserfiche. That way, the initial scan can file the docs with blank fields, but as QF processes them, they won't be allowed to leave QF without a value.

1 0
replied on November 6, 2013

Also, I believe you can tell Quick Fields how to handle metadata arguments between quick Fields and LF Server templates/fields. It would error on storage attempt when set properly

0 0

Replies

replied on November 6, 2013

This is a pretty annoying issue I have had in the past as well. 

 

What I would do is a pattern match and then a conditional so that if the token does not match what you wanted, that it will fill the field with a specific value that you know to search for in LF Client and correct later. 

 

Or you can use a conditonal to test if the token you have matches a regular expression and if it doesn't, it will set the token to something besides blank so that you get an error before submitting.

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

Sign in to reply to this post.