AFAS doesn't have a standard API that we can implement in our product. AFAS instead supports custom "connectors". These are API endpoints that a customer can design themselves. The customer, therefore, has the choice of which data is returned from these endpoints. Oneteam only takes data from AFAS and doesn't send mutations back to AFAS.
Subject | Supported? | Note |
Synchronizing communities | Yes | Requires customer implementation. |
Synchronizing functions | Yes | Requires customer implementation. |
Synchronizing users | Yes | Requires customer implementation. Allows only 1 community and function per user to be synced.* |
Display employee schedule | No |
|
Updates employee schedule after Flexchange shift approval | No |
|
*: you're able to select another community for a user in the Oneteam app, however, it won't be synchronized with AFAS.
How does the synchronization of employees work with Oneteam?
A big part of a successful Oneteam implementation within your organization will be user management. To automate the user management, Oneteam offers a User Sync API. This application will invite your employees to the right community and function group within Oneteam. If the employee will be moved within your organization, we will also reflect those changes within Oneteam. Employees that are no longer in service, will also be automatically removed within Oneteam. Oneteam only 'listens' to signals from AFAS, except for appointing more communities to an employee, which needs to happen within the Oneteam platform.
What does Oneteam need from an organization?
The customer needs to create 3 separate connectors to allow for automatic syncing of users, functions, and networks to Oneteam. Optionally only a selection of these 3 connectors can be created to allow for syncing of a selection of one or of these 3 datatypes.
The data returned from these connectors will be used directly to create communities, users, or functions. So if 15 communities are returned from a connector, 15 communities will be created in Oneteam. After creating the connectors the customer also needs to create an access token (AFAS token) to allow the development team to access the connectors.
Click here for a detailed article about this conversion in the AFAS Help Center.
What will Oneteam do?
Since the customer needs to create the connectors for us, we first need to supply them with the required specifications for the AFAS connectors. These can be found here;
When this is done, please check in with your contact person at Oneteam. The connectors will then be checked by our team of specialists and after, when confirmed correct, we will come back to you to undergo the next implementation steps.
If you have any questions or comments, feel free to contact us via our live chat! 👉