Tools4everBV / Tools4everBV/HelloID-Conn-Prov-Target-Intus-Inplanning
no link with employee
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 2
- Forks
- 0
- Avg merge
- 1m
- Merged PRs (30d)
- 1
Description
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
}
]
}
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the current target connector and how its Create mapping handles the proposed resource field. Verify the expected correlation with Person.ExternalId and the behavior when the resource is missing in Inplanning. Done should link the employee to the newly created user, with the separate employee-provisioning connector considered as a distinct scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100