Specifying new users

  1. In Infor Ming.le:
    1. An administrator assigns security roles to a user
    2. Automatically, a SecurityUserMaster BOD is published
  2. In ION, the SecurityUserMaster BOD is transported from Infor Ming.le to LN company 0000 using the data flow Mingle_LN0000 (data flow must be active).
  3. In LN:
    1. Role Assignments are updated in LN when the SecurityUserMaster BOD is received.
    2. Convert to Runtime takes place if the AMS parameter is set to Yes, which is the default.
    3. The resulting User AMS Companies (ttams460) are published to Data Lake by a publisher. Publishers can be viewed in the Publish Changes (ttdpm5125m000) session. Publishers are verified and restarted, if required, by the AUTO_STARTPUBLISHERS job.
  4. In Birst, the LN Foundation Extract and Process workflow extracts User AMS Companies (ttams460) from Data Lake and processes Birst spaces to update LN Analytics.
    Note: If you use Foundation, PCL and QM, we recommend using the LN Analytics Extract and Process workflow, which also handles User AMS Companies. The Extract and Process Workflow is scheduled (nightly) to run automatically.
Note: 
  • New LN users cannot see fact data (measures) before an extract and process workflow is run.
  • New non-LN users can immediately see data. The LNBIRST-Exemption All Security role does not require running an extract and process workflow.
  • Changes in role assignments for existing users are not effective before an extract and process workflow is run.