PMT uses a standard API that we implemented in our product. This makes it easier to implement new customers since they won't have to change anything in their PMT implementation. PMT has a separate server for each store of a customer. This means that each community has its own server/store.
Supported functionality
Subject | Supported? | Note |
Synchronizing communities | Yes |
|
Synchronizing functions | Yes |
|
Synchronizing users | Yes | Currently, users can in theory have a membership to multiple communities, but only if they have the same email address in each PMT environment |
Display employee schedule | Yes | In the current PMT version, users need to log in with their PMT credentials before they're able to see their schedule in Oneteam |
Updates employee schedule after Flexchange shift approval | No |
|
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.
Common exceptions / User cases
In order to have a single user access multiple communities, the user, therefore, needs to have the same email address on both stores. That way we can link this user to each community.
A user can be in PMT twice: once as an intern and once as a regular user (medewerker). This causes two accounts to be created in Oneteam. Solution: give 1 account a fake email address, so Oneteam doesn't make a link to both accounts.
Flexchange exchanges that are created, will be created for a specific shift from PMT. Users won't be able to select their own times and functions. The users that are allowed to respond to the exchange are retrieved from PMT, to make sure only eligible users can take over a shift. Rules that can impact take over ability: CAO rules, max amount of hours in contract, working hours for minors (no working after 19:00). These rules can be disabled by an admin in PMT, which will impact the eligible users.
In the current PMT version, users will need to log in with their PMT credentials before they're able to see their schedule in Oneteam. If users have trouble logging in (and receive an error), or won't get the pop-up to log in, the development team can reset their PMT login token in Oneteam.
Implementation process steps
Receive signed authorization ("machtiging" to allow the use of PMT) form from Sales Rep
Send the PDF File to Support | Retail Solutions support@rwrs.nl
Retail Solutions (PMT) will then give our API user access to that organization and give connection details for that organization.
Development-team will add the integration to the organization, using the connection details provided by PMT.
The organization is ready to start using its integration. Users, functions, and communities can be created with the integration.
What is needed from the organization?
The customer needs to provide an authorization (machtiging), which will be acquired by a Oneteam Sales Rep during the signing process.
What will Oneteam do?
Send the authorization (machtiging) to the Retail solutions, so that they can add permissions to our API user. The development team will need to add the connection details to the organization in Oneteam.
If you have any questions or comments, feel free to contact us via our live chat! 👉