Important
This repository contains the connector and configuration code only. The implementer is responsible to acquire the connection details such as username, password, certificate, etc. You might even need to sign a contract or agreement with the supplier before implementing this connector. Please contact the client's application manager to coordinate the connector requirements.
Warning
This is a private repository due to need for own credentials as implementor for this connector (or the usage of our internal credential proxy)
Warning
*You need to sign a contract with the supplier before implementing this connector
- HelloID-Conn-Prov-Target-Topicus-Somtoday-ConnectAPI-Employee-Readme
HelloID-Conn-Prov-Target-Topicus-Somtoday-ConnectAPI-Employee is a target connector. Topicus-Somtoday-ConnectAPI-Employee provides a set of REST API's that allow you to programmatically interact with its data.
- CustomProperty:
- When using Somtoday Source, you need a custom property in your system to save the UUID of the employee, so you can use the UUID as the correlation key. More information can be find here HelloID Docs
The following settings are required to connect to the API.
Setting | Description | Mandatory |
---|---|---|
ClientId | The ClientId to connect to the API | Yes |
ClientSecret | The UserClientSecretName to connect to the API | Yes |
Instelling | The name of the organization in SomToday | Yes |
BaseUrl | The URL to the API | Yes |
TokenUrl | The Token URL to the API | Yes |
The correlation configuration is used to specify which properties will be used to match an existing account within Topicus-Somtoday-ConnectAPI-Employee to a person in HelloID.
Setting | Value |
---|---|
Enable correlation | True |
Person correlation field | Custom.SomTodayUUID |
Account correlation field | uuid |
More information about
UUID
correlation in section: HR target Source
Tip
For more information on correlation, please refer to our correlation documentation pages.
The following lifecycle actions are available:
Action | Description |
---|---|
create.ps1 | Correlates existing Employees |
update.ps1 | Create/Updates accounts for the Employee, and updates the properties |
configuration.json | Contains the connection settings and general configuration for the connector. |
fieldMapping.json | Defines mappings between person fields and target system person account fields. |
The field mapping can be imported by using the fieldMapping.json file.
As an implementer, you need your own set of credentials before you can implement this connector. Therefore you need to sign a contract with the supplier.
A School (also known as an 'organization' within Somtoday) might have multiple departments (or vestigingen). Accounts are correlated based on the '_setting.currentSchoolName' value in the fieldMapping.
The create.ps1 does create employees but only accounts for the employees; So managing the employee is not in the scope of this connector. When an employee does not exist the connector throws an error.
Since this connector is often used with the Somtoday Source connector, the current version uses the employee's UUID -with a custom property- to correlate the account in Somtoday. However, the connector can be used with other source systems. To achieve this, you should add a field in the field mapping and use it as the correlation key or value. This should be an existing property in Somtoday. For example, externnummer
or medewerkernummer
.
The connector manages the accounts of employees in Somtoday. Therefore, it does not create or update employee records but only creates accounts for existing employees.
Currently, it is not supported in the connector for a Somtoday employee to switch between schools. If this is a common situation, it can be implemented, but it requires some modifications to the code. For example, the AccountReference needs to be updated when a school change occurs. If this happens only occasionally, you could remove the account from HelloID and re-run the creation script.
The following endpoints are used by the connector
Endpoint | Description |
---|---|
/oauth2/token?organisation= | Retrieves the oAuth token |
/rest/v1/connect/vestiging | Retrieves organizations for which the token is authenticated |
/rest/v1/connect/vestiging//medewerker | Retrieves all employees for a specific department |
/rest/v1/connect/vestiging//medewerker//account | Updates and retrieves Account information |
Tip
For more information on how to configure a HelloID PowerShell connector, please refer to our documentation pages.
Tip
If you need help, feel free to ask questions on our forum.
The official HelloID documentation can be found at: https://docs.helloid.com/