ION content provisioning for BODs

In single-tenant deployments of Workforce Management, the IMS Bod Publishing task sets up the required document flows automatically.

The available document flows are listed in Maintenance > System Administration > ION > IMS Document Flow Configuration with a Document Flow Type of DOCUMENT_FLOW. You can enable or disable a document flow by editing the flow and selecting or clearing the Document Flow Enabled option. However, you cannot enable a document flow if any of the BODs that belong to the flow are disabled.

Note: These document flows should not be modified, renamed, deleted, or deactivated in ION Desk. If a document flow is updated, the flow will be disabled along with any of the BODs that belong to this flow.

The available BODs are listed in Maintenance > System Administration > ION > IMS Document Name Configuration with a Document Type of Change History Bod or Event BOD. You can enable or disable a BOD by editing the BOD and selecting or clearing the Send Document Enabled option for an outbound BOD or the Receive Document Enabled option for an inbound BOD. However, you can only disable a BOD if all related document flows are disabled.

When the IMS Bod Publishing task is run for the first time since the Job Scheduler was started, the BODs enabled for sending or receiving in the IMS Document Name Configuration maintenance form are registered with the WFM connection point if they do not already exist. In addition, the associated document flows in the IMS Document Flow Configuration maintenance form are registered with ION or updated if they have changed since the task last ran.

If registration with ION fails, the task fails with an actionable error.

When you select the Send Document Enabled or Receive Document Enabled options in the IMS Document Name Configuration maintenance form, the ION API is called to register the BOD with ION. If the BOD is in a workflow with other BODs that have not been enabled, these BODs are also enabled and registered with ION.

Note: If the registration with ION fails because a required connection point does not exist, an error is displayed indicating that the required applications are not available for this tenant.