Workflow Events
A virtual set of rules to be executed sequentially that lives inside a workflow object, there are 7 different events possible, each event is triggered upon different stages within the lifespan of a document:
- onScan
- Executed for each document after it has been discovered (as soon as its parent document discovers it)
- onAddUpdate
- Executed once the document is identified to have one of the following actions based on its incremental state: add or update
- onDelete
- Executed once the document is identified to be deleted (action: delete)
- onSubJob
- Executed for any sub job created by Aspire components, this is the event to place any rule that should be executed only for subjobs. (Available from Aspire 5.1)
- onPublish
- Executed after onAddUpdate, onDelete oronDelete onSubJob, this is the event when all common publishing rules should be placed regardless of the document action
- onError
- Executed if any stage within the connector framework or workflow rule fails while processing a job.
- onIdentity
- Executed for each identity extracted in an Identity crawl.
- onIdentityError
- Executed if any stage within the connector framework or workflow rule fails while processing an identity job.
- onStart
- Executed only for the crawl start job. Rules that must be executed only at the beginning of the crawl should be added here. (Available from Aspire 5.1)
- onEnd
- Executed only for the crawl end job. Rules that must be executed only at the end of the crawl should be added here. (Available from Aspire 5.1)
Event Items
Each event is composed by of a set of items. Each item defines an action to execute in the event, and in some cases they can contain nested event items. There a are three types of event items:
Reference
These items are references to rules that will be executed in the event, each reference contains the id the ID of the rule to execute. References to rules of type "Folder" “Folder” can contain nested references or exit items.
Exit
The exit items are used to finish the execution of the event at a specific point. Any job processed by this item will exit the workflow event, but it does not mean that the job will be terminated, the . The processing of the job will be continued by the next stage, pipeline, or event.
Condition
Conditions are items used to control the flow of a job. If a job matches the condition statement, the job will be processed by the items contained by the condition, if not, it will continue to the next item in the workflow. Conditions items are always nested to references of rules of type "Choice" “Choice”, and they can contain other references and exit items. All condition items are associated to the template "Condition"“Condition”.