Automatic Update of Candidate Status based on Bookings

Created by Martin Parkinson, Modified on Wed, 22 Apr at 1:04 PM by Graeme Orchard

From version 1.00.18.186 or later a new facility has been introduced to automatically control the Status of candidates, based upon whether or not they have bookings.


Overview

While a candidate has any current/future bookings (based on Monday of the current week), the candidate's status should be "LIVE" (or some synonym of this). 

If a candidate has had bookings within the past XX weeks, then the status should remain at "LIVE".


If a candidate was added to the system within the past YY weeks but has not been booked, then the Status should not be touched. 

If a candidate has previously been booked, but had no bookings within the past ZZ weeks then the status should be changed to HOLD. (Status specified with parameter TEMPS, Text (7) )

If a candidate is in a specified status (Specified with TEMPS, Text (5) - there can be up to 4 of these) for more than HH weeks then they should be automatically changed to DEL  (status specified with parameter TEMPS, Text (8) )

If a candidate is at any one of several specified statuses, they will be ignored and their status will NOT be changed.

There will be a parameter added to the system to specify the number of weeks of inactivity (defaulting on setup to 8 weeks), plus the statuses mentioned above should be user definable


Info: The update program will be able to be run both ad-hoc from the Maintenance menu and as an automatic Daemon process.




System Setup

In order for the enhancement to work there are some parameters which control the update process, which are listed below:

Parameter set: TEMP


TEMPS, Text(4)
Cand Status for Working Status
Cand Status for Working - Default is LIVE
TEMPS, Text(5)
Cand Status Check for Final status
Cand Status(es) to check before moving to final status - Default is HOLD
(This is the status(es) that are checked before changing to the final status after HH weeks of no status change)
Multiple statuses (up to 4) can be added and separated with a comma. e.g. HOLD,ARC
TEMPS, Text(6)
Cand Status for Recent Work
Candidate Status for Recent Work (The status indicating that candidates have worked recently i.e. within XX weeks) - This is typically set to LIVE.
TEMPS, Text(7)
On Hold Cand Status
Candidate status meaning HOLD. Candidates will be set to this status if no bookings in HH weeks) 
TEMPS, Text(8)
Final Cand Status
Final Cand Status (P45/DEL) - Default is DEL
TEMPS, Integer(2)Number of weeks meaning Recent Work - Defaults to 8    (this is XX above)
TEMPS, Integer(3)Weeks to ignore new cands - Defaults to 8      (this is YY above)
TEMPS, Integer(4)Weeks On Hold to final status - Default to 8   (this is HH above)
TEMPS, Free (3)Status' to ignore (e.g. don't move workers at status DNU). Can Input multiple separated by commas
IMPORTANT (Think carefully so that this tool does not move any candidates i.e. DNU to other status' if not wanted)  **


** NOTE:  With parameter TEMPS, FREE(3) above then if a NEW status is added to the system in-future, you would need to update this parameter with the new status(es) to ensure the Daemon does not interact with them or affect them.




Running the Process

Once the system has been setup using the parameters above, it is possible to run the process to make these changes.

The option can be found in
Maintenance => Tools => Update Candidate Status (Bookings)

Selecting this option will allow a user to manually run the process.


It is also possible to run this Automatically as part of a Daemon process that runs periodically (typically once per day)

If this is to be run as a Daemon process, the program name is CT/CNDSU


NOTE:  If you require this process to be run as a Daemon, please contact Influence as it is best if we setup the automatic process for you.



Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article