This system was built for a need, employees were not leaving their shifts even though they stopped working … and only after an hour or more they would opt out of their shift.

The main issue is that the employee’s replacement has already arrived and replaced said employee that needs to finish his shift. So the employer was paying extra hours and the employees were not even there.. (sometimes requesting their friends to log them because they “forgot”).

The request was simple: We need to prevent employees from staying on shift in the computer even though they left… Now – since the current system manages the ins and outs of all and the existing CRM software company were reluctant to add the feature. I was approached and asked if I can offer an outside solution.

So with access given to their DB via their CRM software company to run queries of Employee ID and current status, I created a system that holds only the missing information – HOW MANY EMPLOYEES ARE ALLOWED NOW FOR THIS BRANCH? – 2? 1? how many are in shift currently at said branch? 2? so no one can enter a shift (same employee status) until the one that needs to leave , leaves.

The System is built from two main sections:

1. PermissionCheckUI – where the manager adds branches and sets shift quotas.
2. PermissionCheckApi – checks the DB that holds the data that was created in the former bullet and then checks with the company’s CRM to see who is in on this branch and returns a true or false answer.

The PermissionCheckApi receives an API call from the CRM when an employee wants to enter a shift and returns to the CRM a true or false answer.

The pictures below show only the front end part of the system. The PermissionCheckApi does most of the heavy lifting.

Skip to content

newSite