Extend tables of hrsd module

yasserbouat
Tera Guru

3 weeks ago

Hello,

I hope you all re doing great,

I m looking for a mini project or use cases to learn how to extend tables of hrsd module and create new ones and work on them : so please if any one has any ressources please share

Thanks

0 Helpfuls
  • 440 Views
2 REPLIES 2

SupriyaWaghmode
Mega Sage

3 weeks ago - last edited 3 weeks ago

Hi @yasserbouat , 

 

To master extending and creating tables within the ServiceNow HR Service Delivery (HRSD) module, it is important to understand its core architecture. HRSD heavily relies on the Center of Excellence (COE) table structure. 
All HR Case tables inherit from the main HR Core Case table (sn_hr_core_case), which itself extends the base ServiceNow task table. When you want to expand HRSD, you typically either create a New COE (Custom Child Table) or extend HR Core Task
 
Below use cases you can build on Servicenow PDI instance. 
 
🚀 Mini Project Idea: "Tuition & Upskilling Reimbursement Program"
Instead of polluting general HR tables, this use case requires you to manage specialized financial approvals, course certifications, and localized corporate benefits policies. 
 
Part 1: Extending an Existing COE (Adding Custom Fields)
  • The Scenario: When an employee submits a case under the existing HR Total Rewards / Benefits COE (sn_hr_core_case_total_rewards), HR needs to capture specific educational parameters without altering standard payroll behavior. 
  • Hands-on Task:
    1. Open your Personal Developer Instance (PDI) and go to the sn_hr_core_case_total_rewards table.
    2. Create custom fields specific to this service: u_institution_name, u_course_title, and u_estimated_cost.
    3. Crucial HRSD Best Practice Step: Add these fields to the form layout, but configure a UI Policy to hide them globally. Then, navigate to your HR Service configuration and add these fields to the Service table fields slushbucket. This ensures they only appear when the "Tuition Reimbursement" service is actively selected. 
 
Part 2: Creating a Custom COE (Extending the Case Table)
  • The Scenario: Your organization has a highly sensitive, legally bound sub-department (e.g., Union Relations Management or External Contractor Disputes) that requires entirely unique security constraints, specialized assignment groups, and isolated workflows. 
  • Hands-on Task:
    1. Create a brand-new table (e.g., sn_hr_core_case_labor_relations) and set its Extends Table property to sn_hr_core_case.
    2. Register your new table under the COE Configuration registry (sn_hr_core_coe_config) so HRSD recognizes it as a valid Center of Excellence.
    3. Create custom Access Control Lists (ACLs) to strictly isolate this new table so that normal HR Tier 1 agents cannot view its sensitive data rows. 
 
Part 3: Extending HR Task (sn_hr_core_task)
  • The Scenario: During an upskilling case, internal IT needs to allocate a specialized sandbox license, and Finance needs to cut a direct check. Standard HR Tasks do not capture fulfillment variables. [1]
  • Hands-on Task:
    1. Create a custom fulfillment table (e.g., u_hr_finance_fulfillment_task) that extends sn_hr_core_task.
    2. Doing this ensures your custom task still utilizes OOB HR features like HR Templates.
    3. Build an HR Lifecycle Event or a Flow Designer workflow that spins up this custom task when a case moves into "Work in Progress". 
 
Scenario Recommended Approach
Same HR process, only extra fields needed Extend HR Case table
One-to-many related records Child table
Compliance or master data repository New related table
Large HR business process with its own lifecycle Standalone application tables
Employee request requiring HR workflows and COE assignment Extend sn_hr_core_case
Employee Relations specific process Extend sn_hr_er_case

 

Note:

If the record should appear and behave like a standard HR Case, extend an HRSD case table. If it has its own lifecycle, reporting model, or long-term data retention needs, create a separate table and relate it to HR cases when needed. This keeps HRSD maintainable, upgrade-friendly, and aligned with ServiceNow best practices.

 

To successfully complete this practice project, rely on these foundational learning tracks:

 

if my response helped, please mark it as the accepted solution so others can benefit as well. 

 

Thanks & Regards ,

Supriya Waghmode 

martinvirag
Giga Sage

3 weeks ago

I usually just follow my standard table creation method. 
Anything that is extended from the core hr table is good.  The child tables are called COE's.

Don't forget to then configure that COE's form, if you want additional security the COE security and check if it's enabled (so agent can create)

https://www.servicenow.com/docs/r/employee-service-management/hr-service-delivery/configure-hr-cente...
https://www.servicenow.com/docs/r/employee-service-management/hr-service-delivery/hr-coe-security-po...


An example would be:
HR VIP Cases -> special cases that required to be handled separately. Its only visible to a special agent group, add some fields as an extra.

Try to configure the case creator interceptor as well to handle this and a new catalog item.