Automating job posting removal
Administrators can specify that job postings are removed from a requisition when a candidate enters a workflow step.
- Manage Filled Openings
- Remove Postings Upon Entering
- If the Manage Filled Openings field is Offer Status, then the # Filled field increments when the offer status for the application is Accepted. If the offer status does not change to Accepted, then the # Filled will not increment and the # remaining does not reflect the change.
- If the Manage Filled Openings field is Hire, then the # Filled field increments when the hire action is completed. If the hire action is initiated but has not been approved and completed successfully, then the # Filled does not increment, and the # remaining does not reflect the change.
The Remove Postings Upon Entering field on the requisition determines when the postings are automatically removed. When a candidate is moved into the workflow step that is indicated in the Remove Postings Upon Entering field, the system checks the # Remaining field on the requisitions. If the field is 0, then the postings are automatically removed. If the field is not 0, then the postings are not removed. The # Remaining field has to be zero before the candidate is moved into the Remove Postings Upon Entering field workflow step.
Example: The Manage Filled Openings field is set to Offer Status. The # of openings for this requisition is 1. When the Offer Status is changed to Accepted for the first application, the # Filled increments by one, resulting in # remaining =0. Then, when the application is moved to the Preboarding workflow step, the postings are removed because # remaining = 0 before the application was moved into the Preboarding step.
In this same example, if the Offer Status were never changed to Accepted, then the # remaining would not =0 and so on. Even if an application were moved to Preboarding step, then the postings would not be removed automatically.
See Creating a workflow.