I got the HR certification a long time ago, and all I can remember about this area is that it’s Cases all the way down.
Oh! And that saying “Incident” or “Ticket” in front of an HR person would get you fired immediately.
For more technical advice and best practices, watch Sabrina Ethridge’s nullEDGE session, who has been focused on HRSD for the past 5 years.
Key takeaways
- COE tables without services preconfigured need extra work: form fields, notifications, inbound actions.
- Use the Manage HR Catalog module to create a record producer, template, and service all at once.
- Variables are auto-mapped if their names match HR Profile fields.
- The generic lookup table can help you avoid exceeding your custom table limit and lets HR update choice values themselves without waiting for releases.
- Not everything needs its own field.
And I’d like to highlight the final remark from the Q&A:
Don’t put HR information in ITSM tables
You might not get fired for misusing the concepts, but you will run into security and licensing problems sooner or later.
References
- Sabrina Ethridge: LinkedIn
- nullEDGE Website
- nullEDGE YouTube channel
- My LinkedIn posts #nullEDGEAdvent (any feedback is welcomed!)
- Intro to my nullEDGE advent calendar adventure
