1 ACCEPTED ANSWER
Hi Seth,
In this scenario, where you want to implement custom keyword-analysis rules to determine if the document needs manual indexing or not (i.e. something more complex than just if required keyword(s) have value(s) or not, which you could do without scripting) you could do so using the form definition level VB script hook:
This context runs after Advanced Capture is finished with the document, but before it is updated to the database. It will run the 'FormAppliedMain' context (Sub) in the specified VB script, and from here you can access the standard Client API Document object to get the document information and keywords. So something like this:
Sub FormAppliedMain
Dim thisdoc
Set thisdoc = OCRDoc.Document
' do whatever analysis you want on the Document object or its keywords, etc.
End Sub
However - the Document doesn't have a property that allows you to programmatically change the indexing status of the document (change it from indexed to unindexed or vice-versa) but what you can do is tell Advanced Capture that you want to change the document type. So you may want to consider creating a new document type (or types) that has the same keyword types assigned to it (I assume you don't want to lose any extracted/pre-existing keyword values when this 'fault' condition occurs, you just want to be able to route these documents to manual index in lieu of bypassing it?) and then use the script to change the document type to this other type that means 'the same as before, but failed my custom requirement rules' which you can then use scan queue rules (a CPD decision queue that follows Advanced Capture, for example) that sends the document(s) of this/these new 'fault' document types to manual index. So continuing from my example code above:
Sub FormAppliedMain
Dim thisdoc
Set thisdoc = OCRDoc.Document
' do whatever analysis you want on the Document object or its keywords, etc.
If <document is OK> Then
' do nothing, the document will stay as-is and be archived/updated
Else
' failed the requirements, so change the document type to type <B> that means something is wrong
OCRDoc.DocumentTypeName = "name of my fault-occurred but same keywords DT"
' or could set by DocumentTypeID instead of name, if you so desire
End If
End Sub
Then after AC runs, your next queue can sort out these doc type(s) that mean failed, and send them to manual index - or whatever you need to have happen.
Hi Seth,
In this scenario, where you want to implement custom keyword-analysis rules to determine if the document needs manual indexing or not (i.e. something more complex than just if required keyword(s) have value(s) or not, which you could do without scripting) you could do so using the form definition level VB script hook:
This context runs after Advanced Capture is finished with the document, but before it is updated to the database. It will run the 'FormAppliedMain' context (Sub) in the specified VB script, and from here you can access the standard Client API Document object to get the document information and keywords. So something like this:
Sub FormAppliedMain
Dim thisdoc
Set thisdoc = OCRDoc.Document
' do whatever analysis you want on the Document object or its keywords, etc.
End Sub
However - the Document doesn't have a property that allows you to programmatically change the indexing status of the document (change it from indexed to unindexed or vice-versa) but what you can do is tell Advanced Capture that you want to change the document type. So you may want to consider creating a new document type (or types) that has the same keyword types assigned to it (I assume you don't want to lose any extracted/pre-existing keyword values when this 'fault' condition occurs, you just want to be able to route these documents to manual index in lieu of bypassing it?) and then use the script to change the document type to this other type that means 'the same as before, but failed my custom requirement rules' which you can then use scan queue rules (a CPD decision queue that follows Advanced Capture, for example) that sends the document(s) of this/these new 'fault' document types to manual index. So continuing from my example code above:
Sub FormAppliedMain
Dim thisdoc
Set thisdoc = OCRDoc.Document
' do whatever analysis you want on the Document object or its keywords, etc.
If <document is OK> Then
' do nothing, the document will stay as-is and be archived/updated
Else
' failed the requirements, so change the document type to type <B> that means something is wrong
OCRDoc.DocumentTypeName = "name of my fault-occurred but same keywords DT"
' or could set by DocumentTypeID instead of name, if you so desire
End If
End Sub
Then after AC runs, your next queue can sort out these doc type(s) that mean failed, and send them to manual index - or whatever you need to have happen.
