ION integration (BODs) using IMS for new MT cloud tenants
SCP now implements BOD processing using IMS, in addition to I/O box. BOD processing logic
is updated for supporting the I/O Box and IMS based BOD processing.
I/O Box BOD processing is the default and IMS based BOD processing is used only when ibp.ion.ims = true for a tenant. The ibp.ion.ims property is a tenant Property, as opposed to an application property.
This feature impacts the following usages of BODs by SCP where IMS BOD processing is enabled
- Workflow BODs: Workflows issued from SCP for cycle period and scenario process steps (Process.Workflow, Acknowledge.Workflow).
- Security BODs: Users, Roles and permissions from Infor OS (Sync.SecurityUserMaster, SyncSecurityPermissionMaster, SyncSecurityPermissionMaster).
- Alert BODs: Event Notifications generated by Event Generators (Process.PulseAlert, Acknowledge.PulseAlert).
Note: This feature is enabled for new MT Cloud tenants only. From this release, the ibp.ion.ims
property and hence default BOD processing in SCP is as follows:
- SCP On-Premise and Single-Tenant have ibp.ion.ims property = false and use I/O Box BOD processing.
- Existing tenants in Cloud MT have ibp.ion.ims property = false and continue to use I/O Box BOD processing.
- New tenants in Cloud MT have ibp.ion.ims = true and IMS BOD processing is used.
You are not required a new role or privilege access to use this feature.