Add Actor to Landmark via IPA

You can probably just add some logic to run an ISS List-Based Sync. Details are in the ISS Configuration Guide. You can use your existing process to load LSF security, create an XML file of users/actors, then kick off a list-based sync to get the users into ISS and Landmark.

If you're using Landmark Apps (GHR) then you probably need to add Landmark Transaction nodes to create the Landmark Actor/Roles/Identities/Agents. You would still need to run an ISS Sync to get ISS to recognize the users.

We've also created flows that make web calls to ISS, but Infor doesn't like to support it if you run into issues.

If you are using Lawson Talent Management then you will also want to look at using Landmark Nodes to add the agent, context property, user profile and possibly the email address. If you search this forum their are many posts related to this subject. They were very helpful to me in setting up our flow to add users.

If we are using Landmark runtime only for Infor Process Automation, do we also need to add Landmark nodes to our flow? And, if we do that, do we still have to run an ISS Sync? Are you willing to share your flow by sending it to brichman@mhc.net?

I will check the ISS Config guide. I was trying not to have to run a sync as we have 13000 users and the estimate to sync is 4-5 hours. Are you saying no matter what I do I have to sync.

 

Thanks

I will continue searching and hopefully these will help.

 

Thanks

I will gladly share the flow but it only adds the users to LSF. I am trying to build one to add users to Landmark.

 

Thanks

the list-based sync in the user guide shows you how to create an xml file with just the users you want to sync. so you will only be syncing new users, not all of your users.

BarbR, if you are only running IPA then you don't need the Landmark nodes, but you will still need to perform the list based sync to get them to show up in ISS.

Thank you JimY! Can you please confirm that is still true if we are using Employee and Manager Self-Service and managers and staff need the Inbasket to respond to HRUserAction and UserAction nodes? We heard somewhere that we'll have to provision Landmark access in order for them to be able to use the Inbasket. If we only need to perform a list based sync for any LSF RMID that was added, changed, or deleted each day, then we are happy campers!

I can't say for sure, but I believe you will need to use the inbasket.

Thanks JimY, let me clarify my question. Yes, I know that self-service-only Managers will need the inbasket to respond to HRUserAction and UserAction nodes. What I meant to ask is: Is it enough to provision through the LSF userload and then perform a list based sync ... or ... do I need to update my provisioning process flow to do the userload then include Landmark nodes and then perform a list based sync?

How is the authentication taking place? Are they authenticating to the Ldap on the LSF server? When an employee logs in what parts of the application will they be using?

Yes, it's the LDAP on the LSF server, which is ldapbind to the Active Directory for authentication. The employee's I am automating user provisioning for are self-service-only, however the managers will need the Landmark inbasket to respond to process flow tasks from process automation (work flow enabled personnel actions).

Sorry I didn't get back to you sooner. All I can tell you is that we have the Talent Management application so we have to add an Actor id on the Landmark (And much more) side for our employees to access Employee Self Service. Once they log in they can view stuff on the S3 side and also Landmark side (LTM). I guess you could try provisioning them just on the S3 side and test and see if they can still access Employee Self Service.

You are trying to do exactly what I am about to do. We also had the PF in V 9 that added all the users for ESS. Now going to V10. I was hoping that all that I needed to do was to add a node for the Actor and populate it along with the other minor changes I had to do in the for the new services. To now have to also build an XML file to load and then process this seems like a step backwards. We are also only doing S3 in V10 so need limited access. We automate all the ESS users and then for the few managers we do those manually.

Unfortunately you need to run the list based sync for them to show up in ISS. You have to use ISS so that both S3 and Landmark get updated at the same time. If you only have IPA running on Landmark then you may not need to add them to landmark, but you will need to run the list based sync for them to show up in ISS. They are still visible without the sync if you use LSA, but Infor may not help if there is a problem.

Maybe part 2 (command line) or part 3 (Landmark activity node) will help:

https://m3ideas.org/2016/...n-m3-and-ipa-part-1/
https://m3ideas.org/2016/...n-m3-and-ipa-part-2/
https://m3ideas.org/2016/...n-m3-and-ipa-part-3/