Create ConfirmBOD

This error handling process step creates a ConfirmBOD message to be sent to an IONDBOut. Create ConfirmBOD has no editable properties, it creates a ConfirmBOD using hard coded values, manifest data, and received (.rcv) file. The user defined XML document for ConfirmBOD is created in the format [XPath] = [value]. These Xpath values must match the Target XPath defined in Agreement Detections.

If you add this process step, you must also define the IONDBIn/IONDBOut channels that will poll ION messages from specified ConnectionURL

Values

There is a maximum of 24 elements and attributes set in ConfirmBOD and you can set several values in different ways. This is indicated by 1), 2), 3), and others.

For ConfirmBOD values, use these guidelines:

  • hard coded

    For example "2.6.2"

  • a value for a mapping manifest item, set in the mapping

    For example, "map:ionFromLogicalId"

  • a value for an agreement control property, set for the agreement, or one of its parent groups

    For example "ionFromLogicalId"

  • taken from the original BOD

    That is the received file, the XPath points where to retrieve this value from the original BOD.

    For example: /pre:*/pre:DataArea/pre:*/pre:TenantID

    Where: "pre" is an internal namespace prefix, and the asterisk (*) for the wildcard.

If a mandatory value is not found, the process will stop. Then, it will throw an exception with an error message, for example, "No FromLogicalId found"

ConfirmBOD XMLSpecifications

Using the Tenant ID as an example, here is how Create ConfirmBOD process flows:

/ConfirmBOD/DataArea/Confirm/TenantID = 1) mapping manifest item "map:ionTenantId" 2) mapping manifest item "map:m3beTenantID" 3) original BOD TenantID (/pre:*/pre:DataArea/pre:*/pre:TenantID) 4) exception "No TenantID element found."

  • First, it will try to get the value for the manifest item "map:ionTenantId" that is set in a mapping.

  • If a value is not found, the process tries to find a value for another manifest item set in a mapping, "map:m3beTenantID".

  • If still not found, the process tries to retrieve the value for the TenantID element in the original BOD, for example from/SyncItemMaster/DataArea/Sync/TenantID (namespace prefixes is omitted) if the original BOD is a SyncItemMaster.

  • If still not found, the Create ConfirmBOD process will stop. Then, it will throw an exception with the message, for this example, "No TenantID element found.".