A Guide to Person Assignments
Person assignments allow you to make assignments of system entities for one or more persons.
Assignments
Assignments are as varied as the system entities they represent, and while there are logical groupings of assignments that behave in similar ways, some assignments request and response models are very different from others.
Aggregated assignments
Aggregated person assignments allow you to consolidate the management of person assignments. You can retrieve all of one or more person's assignments, update, add, or delete assignments for multiple people, and retrieve the names of all available assignments. Refer to the Guide to Aggregated Person Assignments for more information.
Assignment differences
The following table outlines the basic differences between assignments.
Assignment | Person Identity in Object | Effective or Non-Effective Dated with Notes | Default Logic | Batch Create or Update Support | Batch Read Support | Part of People Extension? |
---|---|---|---|---|---|---|
Process Profile Assignments | Present | Non-effective dated; history not required | Empty Profile | Does not support multi_create; supports multi_update and reset in update | Yes | Yes; ProcessEmployeeProfile in EmployeeDataExtension |
Attendance Admin Assignments | Present | Non-effective dated; history not required | null | Does not support multi_create; supports multi-update and reset via multi_delete | Yes | No |
Attendance Profile Assignments | Present | Effective dated with end date and merge support; does not support multiple assignments on same date | Empty Profile | Does not support multi_create; supports multi_update and reset in update | Yes | No |
Attestation Profile Assignments | Not Present; takes employee objectRef | Effective dated without explicit end date | Empty Profile with ID of -1 | No | No | No |
Cascade Profile Assignments | Present | Non-effective dated | null ID | Does not support multi_create; supports multi-update and reset via multi_delete | Yes | No |
Percentage Allocation Rule Assignments | Present | Effective dated without expiration date; multiple assignments are not possible for same date, but can span dates | Empty Profile | Supports multi_create, multi-update, and reset via multi_delete | Yes | No |
Employee Adjustment Rule Assignments | Present | Effective dated without expiration date; multiple assignments are not possible for same date, but can span dates | Empty Profile | Supports multi_create, multi-update, and reset via multi_delete | No; has GET all | No |
Employee Job Preferences Assignments | Not Present; takes person number | Non-effective dated | no default mapping | Does not support multi_create; supports multi_update and reset in update | Yes | Yes; PreferenceProfileDataExtension in EmployeeDataExtension |
Employee Preferences Assignments | Present | Non-effective dated | null | Supports multi_upsert and reset in upsert | Yes | No |
Leave Admin Assignments | Present | Non-effective dated | null | Does not support multi_create; supports multi-update and reset via multi_delete | Yes | No |
Leave Profile Assignments | Present | Non-effective dated | null | Does not support multi_create; supports multi-update and reset via multi_delete | Yes | No |
Paycode Value Profile Assignments | Present | Non-effective dated | null | Does not support multi_create; supports multi-update and reset via multi_delete | Yes | No |
Minor Rule and School Calendar Assignments | Present | Non-effective dated | null | Supports multi_upsert and reset in upsert | Yes | No |
Schedule Group Profile Assignments | Present | Effective dated with start and end date; supports gaps between assignments, multiple assignments in a given period, merging for the same assignment, and overlapping different assignments | null | Supports multi_upsert and reset via multi_delete | Yes | No |
Skill Assignments | Present | Effective dated; no end date support; supports multiple assignments on same date | no default mapping | Supports multi_upsert; does not support reset in upsert | Yes | No |
Certificate Assignments | Present | Effective dated; supports expiration date; supports multiple assignments on same date and gaps between assignments | no default mapping | Supports multi_upsert; does not support reset in upsert | Yes | No |
Telestaff Assignments | Present | Non-effective dated | no default mapping | Supports multi_create, multi-update, and reset via multi_delete | Yes | No |
Schedule Rule Set Assignments | Present | Effective dated without end date; does not support multiple assignments on same date | no default mapping | Supports multi_upsert | Yes | No |
Schedule Rule Override Assignments | Present | Effective dated with expiration date; supports multiple assignments on same day for different profiles and gaps between assignments | no default mapping | Supports multi_upsert and reset via multi_delete | Yes | No |
Forecasting Category Profile Assignments | Present | Non-effective dated | Empty Profile | Does not support multi_create; supports multi-update and reset via multi_delete | Yes | Yes; Part of Scheduling Data Extension |
Format
Each topic introduces a system entity assignment and steps through the process of retrieving a list of the system entities that can be assigned, assigning them to a person, retrieving such assignments, updating the assignment, and deleting the assignment. Not all system entities support all of these options.
The nuances and unique characteristics of call bodies are highlighted and discussed.
Updated over 1 year ago