​@Uzumaki One way to do this is to temporarily modify the Process generated by your learning instance. Go to Automation > Document Workspace Processes > {your learning instance name}, then open the Process with {your learning instance name}.

Temporarily change step 3 in the Process to “Not Equal To”.

Now, the logic for validation is backwards. Documents that should pass will go to validation; documents needing validation will pass. Use this only for testing and remember to set it back to “Equal to” when you’re done.

​@Uzumaki One way to do this is to temporarily modify the Process generated by your learning instance. Go to Automation > Document Workspace Processes > {your learning instance name}, then open the Process with {your learning instance name}.

Temporarily change step 3 in the Process to “Not Equal To”.

Now, the logic for validation is backwards. Documents that should pass will go to validation; documents needing validation will pass. Use this only for testing and remember to set it back to “Equal to” when you’re done.

Thank you Aaron, I will try this.
 

Hi ​@Uzumaki,

The simple way is to add a field that is not present in the document and mention it as mandatory. Or you can add any optional field value or table value as mandatory on a temporary basis in order to make your extraction go into the validation stage.

Good suggestion, I will try that too. Thanks