Setting up the completion workflows

Some document flows come with data completion workflows. The purpose of these workflows is to complete data that might be missing in the BOD that is sent from the Infor Application.

Some proprietary formats require information that is not maintained in the Infor Application or not available as an element in the BOD. In these situations, for specific proprietary message formats, there are completion workflows where this information can be entered. The information is updated into the BOD before the transformation so that the information in the BOD is complete.

See your ERP's integration guide for more information on the completion data required.

An example of information not commonly available in an Infor Application is the Software Vendor ID, which is the identity of Infor as a company as assigned by a government.

The workflow contains one decision table per additional information type that can be added into the BOD. The decision table is empty when initially installed into the environment.

In the same way as when you configure the detection workflow, you can setup a different output value that is dependent on input values. In most cases, the available input values are Accounting Entity and Location ID. You can either leave these fields empty if the same value is used for all accounting entities or locations, or you can configure these fields if there is a difference between the accounting entities or locations.

The Conditions columns can be changed into what suits the implementation best, for example, make exceptions on specific accounting entities. The parameter for the Actions column must not be changed. You must keep the selected parameter and only change the output value in the Actions column for each row in the table.

Some Infor Applications maintain some of the information that is available for completion in the workflow. In this case, specific decision tables can be left empty. The transformation always look for the standard element in the BOD for the information before retrieving the information from the completion area in the BOD.

Workflows that are for proprietary message formats and not required in the installation can be run without any configuration. All workflows that are used by the document flow must be activated. Since the specific branch of the document flow is never used, the workflow can remain empty but active.