Setting up users
Users are first set up in Infor Ming.le and then sent to Workforce Management through the SecurityUserMaster BOD.
When Workforce Management receives the SecurityUserMaster BOD, the WFM user is associated with the Infor Ming.le user by matching the WBU_IDENTITY2 value of the WFM user with the Infor Ming.le ID. If the user does not exist in Workforce Management, the system checks if there's a security role assigned in the BOD for the logical ID of the WFM instance receiving the BOD. The BOD is only processed by Workforce Management if there's at least one WFM security role assigned.
WORKBRAIN.WORKBRIAN_USER mapping
This table shows how the non-nullable fields in the WORKBRAIN_USER table are mapped to the fields from the SecurityUserMaster BOD:
| WORKBRAIN_USER column | SecurityUserMaster BOD field | WORKBRAIN_USER value |
|---|---|---|
| WBU_ID | Not applicable | Auto-generated by WFM |
| WBU_NAME | DistinguishedName | DistinguishedName from BOD |
| EMP_ID | Not applicable | EMP_ID is associated with the new employee created. See Setting up employees. |
| WBL_ID | Property: "Language" | English is used as default language if no match exists |
| WBU_PWD_CHANGED_DATE | The system date when the BOD is processed | |
| WBU_ACTIVE | Status."Security User Status" | Y if Enabled N if Disabled |
| WBU_BAD_LOGIN_COUNT | Not applicable | 0 |
| WBG_ID | SecurityRole | SecurityRole from BOD Security role is specific to the WFM instance processing the BOD based on the logical ID. The value in the Mingle Security Role field is used to match the security group in WFM to the security role in Infor Ming.le. Note: Workforce Management must send WFM security groups to Infor Ming.le before Infor
Ming.le can provision users to WFM.
|
| WBU_EMAIL | EmailAddress | EmailAddress from BOD |
| WBLL_ID | Property."Locale" | English is used as default locale if no match exists |
| WBU_IDENTITY2 | ID | ID from BOD |
| WBU_EXTERNAL_VALIDATION | Not applicable | N |
| CLIENT_ID | Not applicable | 1 |
Since Infor Ming.le is the system of records for user information, the fields in the WORKBRAIN_USER table that are passed by Infor Ming.le should not be modified in WFM as it may cause information discrepancies. You are responsible for ensuring that the fields not passed by Infor Ming.le have appropriate values (for example, Is Power User).
Distinguished Name field changes
We strongly recommend that customers do not modify the Distinguished Name field in Infor Ming.le IFS. If the Distinguished Name field is modified, the Workbrain User Name Change task must be run in WFM to avoid data discrepancies.
In addition, you must ensure that any user names used in the BUDGET_MESSAGE_SENDER, BATCH_EMAIL_SENDER_USERNAME, and SYS_MAIL_RECIPIENT registry parameters are modified accordingly.
For details on running Job Scheduler tasks, see "Job Scheduler" in the Infor Workforce Management Time and Attendance Implementation and Administration Guide.