The current connector does not create a link between the employee (human resource) and the user. This was in my case needed.
In this case I added the field resource and made the assumption it will always be the same as the externalID used for correlation.
When the resource couldn't be found in inPlanning it will return a error.
For a full integration with inPlanning it would be nice to develop a separate target connector that can be used for provisioning employees.
{
"Name": "resource",
"Description": "use to link employee with new created user",
"Type": "Text",
"MappingActions": [
{
"MapForActions": [
"Create"
],
"MappingMode": "Field",
"Value": "\"Person.ExternalId\"",
"UsedInNotifications": false,
"StoreInAccountData": false
}
]
}
The current connector does not create a link between the employee (human resource) and the user. This was in my case needed.
In this case I added the field resource and made the assumption it will always be the same as the externalID used for correlation.
When the resource couldn't be found in inPlanning it will return a error.
For a full integration with inPlanning it would be nice to develop a separate target connector that can be used for provisioning employees.