Version 4.X

The nbParralelsOutput parameter does not influence the order of output for a document. This parameter is to be used for very fast validation in Capture (e.g. automatic document validation) it allows you to parallelize the sending of several documents to Portal.

Validations

There are two cases in Capture:

• A classic document validation: In this case the nbParralelsOutput parameter can be taken into account to send several documents to the outputs in parallel (As mentioned above, the only use is during an automatic validation where the sending takes longer than the validation in Capture, this allows to speed up the process by parallelizing it on the different documents and not the different outputs)
• A task validation: Where this parameter is not taken into account

Exit Trigger Order

In both of the above cases, whether or not they are parallelized by multiple documents, the outputs are executed in the following order:

• Submitting Portal outputs (and sending feedback)
• Sending Windows outputs (If it exists)
• Sending scripted outputs (If any)

There is no parallelization at this level, the only exception is that the return of the scripted output is not expected before finishing the webservice.

Validating a Job via Capture

When a user validates a Portal task via Capture, the order in which it is triggered is as follows:

• Document Validation:

• Portal output: sending new info and comments
• (After Portal’s return) Scripted Output
• (After Portal returns and runs scripts) Back OK to the console
• Validating the task on Portal