With the AFAS integration, users can:
- Profile synchronization: supplement profile fields by linking Embrace with AFAS Insite/Outsite (already available)
- View tasks on the homepage via the AFAS tasks widget (note: in development)
- View vacancies on the homepage by automatically publishing them from AFAS (note: in development)
- Search information directly in AFAS with the Embrace search engine (note: in development)
Also see the factsheet for more information: click here
Configuration
To set up the connector, Embrace needs the following information:
- Participant number
- Token
- Desired language code* (optional, default set to Dutch)
*available languages English, Dutch, French and German.
Once the participant number and Token have been entered, we retrieve the available fields from your AFAS system. All fields that can be mapped will then appear under the 'field mapping' tab. Embrace needs to know from you which fields are desired to be synchronized. The 'IdP-field' column is entered by Embrace.
The mandatory AFAS fields are; PersonID, FirstName, LastName and Email:
| AFAS-field* | IdP-field |
| PersonId | afas-userid |
| FirstName | FirstName |
| LastName | LastName |
*These are the usual AFAS fields to link, but other fields may also be used. For LastName, sometimes a different field is used because LastName does not always include prefixes.
Other fields you can have synchronized include, for example:
| AFAS-field | IdP-field |
| birth-date | |
| department | |
| EmploymentEnd | |
| hire-date | |
| job-title | |
| manager* | |
| mobile-phone | |
| office | |
| city | |
| country | |
| office-phone | |
| postal-code | |
| street-address |
*The Manager field is based on the email address. The email address must be pushed from AFAS.
The field names are customer-specific; please provide which field names you use. In Embrace management you can add fields and then enable or disable them for the sync.
The synchronization runs every night.
It is possible to start the synchronization manually, but this option should be used very sparingly. Always do this in consultation with Embrace to ensure performance.
Troubleshooting
- Prefixes missing in Embrace: Embrace does not have a separate field for prefixes. When surnames and prefixes are in the same field in AFAS, this works as expected. When these are in separate fields, the customer must add a new field to the connector that combines prefixes and surnames into one field. You then link that field to the LastName field in Embrace.