HR application
AllAboard
New starter? The app sorts out the right access and the right development path by itself.
- Role
- Mendix developer (skill sets, AFAS sync) and front-end developer
- Period
- October 2023 – April 2024
- Client
- ANWB, HR
- Type
- HR application (internal)
- Key technology
- Mendix 10, REST/JSON, scheduled events
About the project
Everyone who joins or leaves ANWB comes with a boarding file, covering a development path, access rights and training. AllAboard keeps track of all of it. It's a big app, with hundreds of pages and more than a thousand microflows, and several teams work on it. I took on two parts that save HR a lot of manual work, plus the front-end.
What I built
- Skill sets based on the profile. Work stream, type of employee, location and season (peak or regular) decide which skill sets belong to an account. The app links them automatically, which also settles the access rights and the basic development path. An extra check makes sure nobody ends up with duplicate access rights.
- Nightly sync with AFAS. Every night the app pulls employee, contract and address data from AFAS, checks it against its own records and updates whatever differs. It spots when a contract is about to expire, gets extended or ends, and it links employees to their manager. Each run leaves a log behind, and the app clears out old logs on its own.
- Front-end: I wrote the styling myself, including the boarding overview and the import and export of access rights.
Tools used
- Mendix
- Mendix 10.24scheduled eventsmicroflowsimport mappings
- Integrations
- AFAS (REST/JSON)published REST service for exporting access rights
- Front-end
- SCSSAtlas
What I learned
- 01
Building a nightly sync you can rely on: with an external HR system, including logging and error handling.
- 02
Turning complicated business rules: into automatic assignment, so HR no longer has to do it by hand.
- 03
Working in a large, existing codebase: shared by several teams.