TABLE OF CONTENTS
- Explanation of terms
- Behavior in the system
- This is how our customers use it
- More articles on this topic
Explanation of terms
With status transitions you determine in which order application statuses may be set. By creating status transitions, you decide from which original status to which subsequent status may be changed.
- You can define the status transitions on the Permissions page. Open a existing permission and click on the Application Status Transitions tab. Here you can add new ones via + application status transition or edit existing transitions via the edit icon at the end of the line.
- A status transition always requires an initial status. This is the status an application is currently on. It also needs a target status. This is the application status that should come after the current one.
- First you need to create a permission. After that, you can define the status transitions, where you decide about initial and target statuses, as well as shortcuts.
- Each status should have status transitions, so that you do not build dead ends. The consequence of a dead end would be that you cannot move an application to another application status. If this should happen to you, simply add an appropriate status transition in the permission.
- We recommend creating a permission with additional status transitions. The naming should contain a reference to the role they apply to. Exemplary designation: Additional status transitions personnel department.
It is possible to enter application statuses together with status transitions in one permission. We recommend however a clean separation. For additional statuses a separate permission, as for additional status transitions. So you can authorize the statuses separately from the transitions on a role.
Behavior in the system
- Whether a permission contains status transitions can be determined by the Status Transitions badge next to the permissions name.
- Each role can have its own status transitions through permission. Without permissions for status transitions - the user cannot change statuses.
- We recommend that for each new status transition you always create these subsequent statuses:
- Self rejected
This way you can't get stuck in a status that doesn't have any follow-on statuses. Experience shows that it can happen at any time in the recruiting process that you have to cancel a candidate or that the candidate cancels himself.
This is how our customers use it
Most customers have at least two additional permission per role in the system. Additional statuses of role XYZ and additional status transitions of role XZY. In the permission with the status transitions, only these are then maintained.
There is usually a permission that contains an extremely large number of status transitions, because this is where all status change options are defined for the HR staff via the status transitions.