- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-07-2019 06:21 AM
New York introduced the HR Job [sn_hr_core_job] table, and the documentation describes how this table's intent is to "store multiple job records per user and capture the job history of users within your organization".
Where does this leave the role of the HR Position [sn_hr_core_position] table? There is little documentation to describe its purpose, and it only has a few fields that seem to be present in the Job table. It is used in Org chart views, though.
Also, the relationships between these tables and the HR Profile table seem to be somewhat repetitive and circular.
How should we use these tables moving forward? We're going to need to add some logic to keep these in sync...
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-07-2019 04:56 PM
The Jobs table is intended to track an employee's job history for use within the HR product. One use case for this would be to evaluate past job against new job for determining required activities during employee transfers. Another example would be for supporting employees that have split jobs/multiple job roles and filing cases against the correct job.
In terms of configuration, each Job record is associated to a Position. Position remains on the HR Profile still for customers not using the Job table. To avoid confusion and conflict between the two areas when using Jobs, there's a "Primary" checkbox field on Jobs records that will automatically sync and update that job record data to the relevant HR Profile fields.
You can learn more on the Capturing multiple job records for a user page in product documentation.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-08-2021 03:09 PM
Hello Nat,
I can't speak for the position code field, but I like I have come across the same requirements of needing to create additional fields to add things like position codes, work groups, etc. without any issue on existing functionality. It's a pretty low risk customization of that table in my experience.
