Hi SailPoint Community,
I’m working on integrating a new source using the HCM SaaS connector and I’m facing a specific scenario related to employees with multiple assignments.
For example, an employee might be based in Italy but temporarily transferred to France. In this case, we expect the employee to have two active employment relationships: a primary one in Italy and a secondary one in France.
This should be a standard Supported Feature for this connector.
Based on my understanding, the following attributes in the HCM SaaS connector should handle this scenario based on the following attributes:
- WORKRELATIONSHIP_PRIMARY_FLAG
- ASSIGNMENT_ACTION_CODE
- ASSIGNMENT_EFFECTIVE_START_DATE
- ASSIGNMENT_EFFECTIVE_END_DATE
- ASSIGNMENT_PRIMARY_FLAG
- ASSIGNMENT_STATUS
More on these attributes here.
I assume that these attributes would be duplicated for each assignment, creating two sets of values for an employee with multiple assignments.
I have a few questions:
- Is my understanding of how multiple assignments are handled in the HCM SaaS connector correct? Should I expect to see duplicate sets of these attributes for employees with multiple assignments?
- Should I configure these attributes as multi-valued in my SailPoint account schema to accommodate multiple assignments?
- When importing employee data from HCM (via the standard CSV file), can I expect to see two entries for an employee with multiple assignments, one for each assignment?
Any insights or best practices for handling multiple assignments using the HCM SaaS connector would be greatly appreciated.
Thank you for your help!