Creating a Custom Non-XML On-Ramp - EIS Workflow Messaging - Foundation 24.1 - Foundation 24.1 - Ready - OnBase - external - OnBase/EIS-Workflow-Messaging/Foundation-24.1/EIS-Workflow-Messaging/Configuration/On-Ramps/Custom-On-Ramps/Creating-a-Custom-Non-XML-On-Ramp - 2024-03-25

EIS Workflow Messaging
Platform
OnBase
Product
EIS Workflow Messaging
Release
Foundation 24.1
License

Non-XML on-ramps require a normalization Unity Script to convert non-XML messages into XML messages.

To create a custom non-XML on-ramp:

  1. Connect to the appropriate repository in OnBase Studio.
  2. Right-click the HIS On-Ramp node in the Integration Services tab of the Repositories pane, then select New | Custom Non-XML On-Ramp. The Create HIS On-Ramp dialog box is displayed.
  3. Enter a name for the on-ramp in the Name field.
  4. Select the target message item type for incoming non-XML messages from the Non-XML Message Item Type drop-down list.
  5. Select a message normalization option to convertt non-XML messages into XML messages. The following options are available:
    • Use Auto Transformation: select this option to use auto transformation to convert non-XML messages into XML messages. Select the desired transformation from the Use Auto Transformation drop-down list.
    • Message Normalization Script: select this option to use a Unity Script to convert non-XML messages into XML messages. Select the desired Unity Script from the Message Normalization Script drop-down list.
  6. Select the target message item type for converted XML messages from the Message Item Type drop-down list.
  7. Select the destination life cycle for converted XML message items from the Life Cycle drop-down list.
  8. If needed, you can select the Support Message Properties option to save header information from incoming messages to the Workflow property bag. This information can then be used for other Workflow functions, such as setting Workflow properties from the message header values.
  9. Click OK to save the custom on-ramp.