Enterprise Document Composition requests are made through Workflow's Compose Document action, scripting, or the Unity API. Requests can be synchronous or asynchronous. Asynchronous requests are queued in the database, which is polled by the Document Composition Service. Synchronous requests are processed immediately. It then sends the composed document back to the Application Server, which archives the document into OnBase.
For more information on making Enterprise Document Composition requests through the Unity API or scripting, contact your first line of support.
Although synchronous and asynchronous requests are processed in the same manner, there are distinct differences between the two:
-
Synchronous requests are processed immediately after they are received. Requests are not returned until the document has been created and archived. Synchronous requests are intended for processes in which the user is required to view or modify the document or metadata before continuing. Synchronous requests are queued in the order they are received. If too many synchronous requests exist in the queue, the service call may time out and the Client may not receive the response.
-
The Document Composition Service records the request and returns it immediately. The response only indicates whether or not the request was successfully recorded. Any errors in the actual processing are recorded in the Enterprise Document Composition error log. Asynchronous requests are intended for less interactive processes, such as a nightly batch process. There is no limit to the number of asynchronous requests that can be queued for processing.