Capturing multiple job records for a user

  • Release version: Washingtondc
  • Updated February 1, 2024
  • 2 minutes to read
  • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Capturing Multiple Job Records for a User

    The new Jobs (snhrcorejob) table in Employee Service Management enables organizations to capture multiple job records for users. This feature allows HR cases to be linked to specific job records, enhancing the management of employee job histories and associated cases.

    Show full answer Show less

    Key Features

    • Multiple Job Records: Store and manage multiple job records for each user, enabling a comprehensive job history.
    • Job References: The HR Profile table references the Jobs table, linking each user's primary job to their job records.
    • HR Case Integration: The HR Case table allows referencing specific job records when creating cases, ensuring relevant job details are captured.
    • Lifecycle Event Support: Create lifecycle event cases that can specify which job record they pertain to, facilitating accurate processing of transitions (e.g., from intern to full-time).

    Key Outcomes

    By utilizing the Jobs table, ServiceNow customers can ensure that HR cases are accurately associated with the correct job records. This leads to improved case management and more efficient handling of employee transitions, which ultimately enhances the HR service delivery process.

    Capture multiple job records for a user with the new Jobs (sn_hr_core_job) table. When creating HR cases, you can specify which job the case pertains to. For example, say that you have a payroll discrepancy case and the employee has two associated job records. When the case is created, you can specify which job the case is for.

    Jobs table overview

    Beginning in the New York release, you can use the new Jobs (sn_hr_core_job) table to store multiple job records per user and capture the job history of users within your organization.

    Jobs table and HR Profile table

    The HR Profile table has a reference to the Jobs table for the user's primary job.

    Table 1. HR Profile (sn_hr_core_profile) table
    Field Description
    primary_job
    • Job start date
    • Job end date
    Reference field to the Jobs (sn_hr_core_job) table.

    For example, the following HR profile record is for Eva Seahorn. Eva was first hired as a UX designer in May 2017. In August 2018, Eva left the company. In June 2019, Eva was rehired as a marketing director. Eva has two associated job records, with the marketing director position as Eva's primary job.

    • In the Employment Information related list, information about the primary job is displayed.
    • In the Jobs related list, all of the associated job records are displayed.
    Note:
    The employment start date represents the first day the user was employed with the organization. The job start date represents the first day of the user's current primary job. Because Eva left the organization in August 2018, but was rehired in June 2019. This represents Eva's new employment start date.

    HR profile record with multiple job records.

    Jobs table and HR Case table

    The HR Case table has a reference to the Jobs table for the subject person's job.

    Table 2. HR Case (sn_hr_core_case) table
    Field Description
    subject_person_job Reference field to the Jobs (sn_hr_core_job) table.

    In the case of Eva Seahorn, for example, Eva was rehired as a marketing director in June 2019. Eva has two associated job records. When an onboarding case is created for Eva, the subject_person_job field enables you to specify which job the onboarding case pertains to. The onboarding case would be for the marketing director job Eva was rehired for.

    Supporting multiple jobs in a lifecycle event

    Use the Jobs table to create lifecycle event cases where you can specify which job the case pertains to. For example, say that you have an intern that is being transferred to a full-time position. The intern has two associated job records. When an onboarding case for the full-time position is created, the case is associated with the full-time job record, ensuring that downstream activity sets and activities are triggered based on information from that relevant job record. For more information, see Support multiple jobs in a lifecycle event.