- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-12-2015 12:54 PM
For example, if a retired employee calls with a question about benefits, how is that user tracked? How do people who are no longer employed with the company access any kind of HR ESS?
Or is the function of the HR Management plugin only meant for managing active employees?
If it is intended to also manage retired/terminated employees, how is data maintained?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-13-2015 04:42 AM
We have customers allowing retired employees access to self service today.
Based on an a retirees role, their access to catalog items and knowledge base articles are limited to the type of interactions they would then have with HR - i.e pension, letters of employment etc. We have a self registration plugin where retirees who no longer have an AD account could have a local account or this could be driven by an offboarding workflow (optimal), where their role would be changed and a new local password sent to their personal email in their HR profile.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-12-2015 02:47 PM
Hi Dan,
Great question! The HR plugin can be used to manage both active and inactive employees. The data itself is only a reflection of whats in the source system, so as long as the integration between them is good, the data will be current (it wont change though).
However, termed employees cannot access ESS but, they can be referenced in tickets.
Does that answer your question? PM me and I can explain further or answer any other HR questions you may have.
Best,
John
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-12-2015 07:14 PM
Actually, you can make knowledge articles public. So even for a user who no longer has an active account, they could look up information on a portal without logging in.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-13-2015 11:08 AM
Yes, yes, of course. Thank you for the clarification there, Eric!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-17-2015 07:25 AM
Thanks, John. Yes, integration is the root of our issue. Some background...our sys_user table is populated with LDAP integration. Only active employees who have an active directory account are in our instance. Now that we are expanding with the HR plugin we face that challenge that not all active employees are in active directory (ex: factory floor employees).
SAP is our single source for all employees, active/retired/term/AD/non-AD etc.
What would be best practice/strategy for a transformation map to:
- Populate the hr_profile table and the sys_user table with employees who don't belong in active directory
- Append the sys_user table with additional HR data for active directory users while maintaining the LDAP integration as master SN ESS authentication?
Thank you all for such quick and informative replies!!
