FSM (CSF) & HR Talent (HCM) - Customer Community

Join

Have you been able to schedule maintenance jobs without individual user accounts?

Unknown
Unknown
in Social Groups**

Hello, we have several jobs in GHR that run on a daily or in the case of the BOD sweep, every 5 minutes.  However, each of these jobs currently have to be scheduled by an individual user with the right security access.  This has created a mess for us in the past because if people leave, their accounts get deactivated and someone else has to set-up all the jobs again.  Some of these jobs include absence management (plan close), learning management exports from GHR to LMS, BOD Sweep, Rebuild Reporting Relationships, etc.

Has anyone been successful in setting these up as some kind of service account?  Our legal and IT teams are reluctant to set-up a "generic" user and share the password details to key HR Admins due to the risk of sensitive personal data being made available to too many people.  This is an understandable concern, but I am wondering if anyone has been able to solve this issue in another way.  

I think you in advance for any feedback!  

Answers

  • Unknown
    Unknown

    Our IT team has an IT user account to run Async jobs. We give it a false email address and create the password to log in and create/schedule our jobs.

    I understand the lack of willingness for companies to do this, but there is a future issue people miss.

    John Doe creates Async jobs and scheduled jobs to run in GHR. John Doe leaves the company for a better job opportunity. They are no longer active in GHR. Their JOBS are no longer active in GHR. The work grinds to a halt.

    Limit who can access the jobs account, and limit what actions that account can schedule and run. If the business does not agree with this policy still, then you will have an uphill battle ahead. 

  • lila-elizalde
    lila-elizalde Member Posts: 9

    a business practice to avoid people rotation issues. is that job schedules are normally set under the lawson user id - who will lever leave image

  • Unknown
    Unknown
    https://community.infor.com/discussion/comment/54593#Comment_54593

    The lawson ID is, by necessity of the software, a highly privileged ID.  It's better to create a service account, with far less system and application access, especially since multiple non-IT users will require access to the password for this account.

Categories