Specifying a new intermediate step action

Specifying a new action for writing the database.

Complete these steps:

  1. On the Documents tab, click Add.
  2. Select the scenario Intermediate step.
  3. Define the statement used to handle the data from the incoming document. Use a stored procedure.
    In the statement, specify the [Data] placeholder to refer to the incoming data. This is replaced by the DataArea from the incoming document. For example, when using SQL Server the statement can contain: EXEC ProcessItem '[Data]';

    The statement must provide an XML result set, containing the DataArea for the document to be sent.

    For details, see "Specifying Statements for Database Connection Points" in the Infor ION Technical Reference Guide (U9829US).

  4. Click Test to test if the statement details specified are correct.
  5. Specify a BOD XML in the dialog box that is displayed.
  6. Click OK to run the test.
    You are informed if errors occur. If the test has finished successfully, the resulting BOD is displayed. You can check the database whether the data is handled as expected.
  7. Select the document to be received. If the document is not defined in the ION Registry, add the required metadata.
    The verb is automatically chosen as 'Sync' and cannot be changed.
  8. Select the document to be sent. If the document is not defined in the ION Registry, you can generate the definition.
  9. Click Generate to generate the document metadata into the registry.

    A message is shown with the result. You can adapt data types before the data is generated in the registry. Select one of the elements as the ID and click OK to generate the metadata.

    Note that if a custom document exists with the same name, the existing definition is overwritten.

    Note:  When using this scenario, the modeling in the document flow is different than usual:
    • In the database activity properties, you must select the Send Document based on Incoming Document check box
    • Select the procedure to be used.
    • The activity can only have one document type as input. The output document of the activity is selected automatically.

      The active connection point differs. Select Connect > Active Connection Points.

    • A specific connection point is used, using the original logical id with an additional postfix.