Documents

There are two variants of documents tab displayed based on selected database connection point type.

On the Documents tab of the stored procdure type of database connection point, you can specify:

  • How incoming documents must be handled.
  • How documents must be produced based on data from the database.
  • Multiple actions to read or write the database.

This table lists the supported scenarios in a database connection point:

Scenario Description
Read data from the database that is based on a schedule and publish a document containing the data.
Write database scenario. Receiving a document and based on that write the database.
Request/reply scenario. When handling a Process BOD, an Acknowledge BOD must be sent in reply. This scenario is proven to work only with Microsoft SQL Server database.
Using the database as an intermediate step in a flow. A document is used to trigger a stored procedure, and a new document is published using the resulting data. This scenario is used in multiple situations, such as:
  • A document containing customer data is coming in. Based on this document you can read the open orders for the customer, and send these orders to a next step in the flow.
  • A document containing employee data is coming in, but the data is not complete yet because the salary information is stored in a separate database. The employee data is sent to the stored procedure of the database connection point. The stored procedure retrieves the employee ID from the document, reads the employee's salary from the database and adds the value to the document. The document is passed on to the next step in the flow.

This scenario is proven to work only with Microsoft SQL Server database.

On the AnySQL modeler type Documents tab, you can create a new model for how documents must be produced based on data from the database. Extraction of data from the database is based on a schedule.