Outbound user BODs: Issues to check

The most common reasons for outbound user BOD issues are shown in the table:

Problem What to check
Process.SecurityUserMaster BOD is not created for some Actors when Send BOD for All Actors is used. Verify that the unsent Actors have an email address and an identity on the primary authentication service. These attributes are required for the Send BOD for All Actors action.
A user BOD was processed but the user or a role for the user was not created or updated in Infor OS Portal (or Infor Ming.le).
  • Use ION Desk OneView to verify that the BOD was sent to Infor OS Portal (or Infor Ming.le).
  • Use ION Desk to check for Confirm or Error BODs.
  • Review the Process.SecurityUserMaster BOD to make sure that roles assigned to the user exist in Infor OS Portal (or Infor Ming.le).
Process.SecurityUserMaster BOD is not created when an Actor is created. Make sure that Infor Mingle Create action was used to create the Actor. This action is the only method that will generate the Process.SecurityUserMaster BOD.
Process.SecurityUserMaster BOD is not created when an Actor is updated.

The update must include changes to any of the following attributes for an Actor:

  • First Name
  • Last Name
  • Email
  • Roles

A Process.SecurityUserMaster BOD is generated only if one of these attributes is updated.

Verify that the attribute IsMingleUser is set to true. You can do this by adding the IsMingleUser attribute to the Actor List view
The Actor is not set up as an Infor OS Portal (or Infor Ming.le) user.

Another reason for the Process.SecurityUserMaster BOD to not be generated is if the Actor is not a user in Infor OS Portal (or Infor Ming.le). Check this by:

  • Verifying that the attribute IsMingleUser is set to true. You can do this by adding the IsMingleUser attribute to the Actor List view.
  • Making sure the Actor has been assigned the security class PersonalizationAccess_ST.
Error message: Cannot process BOD as Variation ID [#] must be greater than current Variation Id [#] If you receive this message after attempting to add or delete Landmark user roles, the most likely reason is that a temporary processing mismatch occurred in ION. This is a normal situation that will correct itself. You can ignore the message.