SYMPTOMS
Order of execution during processing:
• Processing rules operate on the DocumentProcessingStepPattern
• The DocumentProcessingStepPattern is a combination of a DocumentPattern and Producer
• The DocumentPattern is either a mime-type, extension or ANY
• A Producer is a Performer + Configuration + output pin
CAUSE
Not applicable
RESOLUTION
There are three possible scopes of the DocumentProcessingStepPattern in the processing rules:
(Example)
DocumentProcessingStepPattern type 1
<DocumentProcessingStepPattern producedBy="File System Collector (Default)" outputPin="Collection">
<DocumentPattern PatternType=“MimeType“ PatternText=“text/xml”/>
</DocumentProcessingStepPattern>
A Document of mime-type text/xml is created by the File System Collector with a Default configuration. Reported from the Output Pin Collection.
This is the most precise description of a Document in the current implementation of the Processing Workflow
DocumentProcessingStepPattern type 2
<DocumentProcessingStepPattern producedBy="File System Collector (Default)" outputPin="Collection">
<DocumentPattern PatternType=“Any"/>
</DocumentProcessingStepPattern>
Any Document created by the File System Collector with a Default configuration. Reported from the Output Pin Collection.
In general it will match more documents than the previous one.
DocumentProcessingStepPattern type 3
<DocumentProcessingStepPattern>
<DocumentPattern PatternType="MimeType" PatternText="text/xml"/>
</DocumentProcessingStepPattern>
Any Document of mime-type text/xml created by Any Performer.
This is the most relaxed definition. It will match more documents than the previous one.
PatternType="MimeType“ is treated the same way as PatternType=“Extension” by workflow execution 'Any Document' of extension txt.
APPLIES TO
3.8; 3.9
Comments
0 comments
Article is closed for comments.