HIS Workflow XML Messaging | Receive Non-XML Message - Web Services Publishing - English - Foundation 22.1 - OnBase - external

Web Services Publishing

Platform
OnBase
Product
Web Services Publishing
Release
Foundation 22.1
License

This operation allows you to compose a document using non-XML message data from an existing message item type. The non-XML data is transformed into XML format through a Unity Script and then used to compose the document. Creating a Receive Non-XML Message operation also automatically creates an HIS on-ramp using the configuration settings from the operation.

Note:

This operation is the only way to send a batch of messages on a single request. The Unity Script object that stores the results is a collection, and multiple XML Document objects can be added to it. Since the script executes on each operation call, this means it is possible to parse a single string into one-to-many XML documents.

Note:

This operation is intended for use with the HIS Workflow XML Messaging feature, which is a separate feature from the Enterprise Integration Server and does not have a corresponding operation in the Enterprise Integration Server documentation.

After selecting the Receive Non-XML Message web operation action in the Create Web Operation wizard, the Select Non-XML Message Item Type dialog box is displayed.

  1. Select the source Non-XML message item type to be used with this operation.
    Tip:

    You can filter the list of available message item types by typing text into the Find field.

  2. Click Next. The Select target XML Message Item Type dialog box is displayed.
  3. Select the XML message item type that will be used to transform the Non-XML Message Item Type.
    Tip:

    You can filter the list of available message item types by typing text into the Find field.

  4. Click Next. The Please enter operation details dialog box is displayed.
  5. Specify the name that you want to be displayed for your operation in the Display Name field. The specified name will be used to display the operation in the Integration Services tab of OnBase Studio.
  6. Specify an XML-compatible name for your operation in the XML Compatible Name (follows XML validation rules) field. Unicode characters are not supported.
  7. Click Next. The Select Normalization Unity Script dialog box is displayed.
  8. Select the Unity Script that will be used to transform the non-XML message contents into an XML message item of the target message item type. The selected Unity Script must be configured to correctly handle namespaces.
    Note:

    Only configured HIS Unity Scripts are available for selection. Contact your first line of support for more information on configuring HIS Unity Scripts.

    Tip:

    You can filter the list of available Unity Scripts by typing text into the Find field.

  9. Click Next. The Select Life Cycle dialog box is displayed.
  10. Select the Workflow life cycle that will process the message items received by this operation, and then click Finish.
    Note:

    Only life cycles configured with a Content Type of Message Items are available for selection.

    Tip:

    You can filter the list of available message item types by typing text into the Find field.

  11. The newly created web operation and on-ramp are now available in the Integration Services tab of OnBase Studio.
    Note:

    Only users with permission to access the selected message item type will be able to execute the created web operation.