Crownrelo.com works with organizations, helping smoothly relocate their employees. They offer an employee portal to each of their clients, where employees can perform various tasks related to the relocation. Choosing the specific relocation services they want, submitting documents, payments, and important dates were all available to each employee via this portal.
However, one particular client wanted more from their employee relocation portal, and enquired Crown if they could make it happen. They required the current portal application to be upgraded with:
Because this was one of Crown’s marquee clients, they were keen on getting these enhancements delivered in the most efficient manner possible. The employee portals were built on Drupal, and so Crown approached Srijan to build the new features. Srijan was already working on a Drupal audit from Crown’s Drupal sites, and readily took on the new project.
Employee relocation is part of the diverse services that Crown offers. The portal upgradation involved adding a dynamic timeline for location tracking and further enhancements for a user-friendly interface.
Dynamic timeline for relocation involved
At any given moment, a user logging into her account would be able to see the status of their current relocation. A click on the service icons allowed employees to view details on that particular service like important dates, documents requested and submitted, and next steps.
Enhancements to the employee portal
The portal menu was redesigned to give the employees easy access to the most frequently used aspects - wallet, services, documents, and contacts. Some key new functionalities introduced were:
The dynamic timeline functionality works as a React UI connected to a Drupal backend. The Drupal backend is responsible to make API calls to Crown’s existing Java application, and get relocation data of each user.
The React UI connects to the exposed REST endpoints at the Drupal backend to get different pieces of relocation information, like relocation data per relocation ID, services per relocation ID etc, to display to the user.
⇓
Request/Response cycle - Drupal perspective
Request/Response cycle - React perspective