Community Feedback
We love to hear your feedback. Your suggestions and ideas are important to us. Our feedback forum is a great place to post your ideas and vote on others. Please share your detailed use case and how the proposed enhancements can increase value to your business. We do read all of your posts, but may not be able to respond to all comments.
More information on the status of submitted ideas can be found here
Frequency - occurs 1 - 2 times per week.
The most significant impact risk is the poor candidate experience when the process is changed on the job card. When the first Application Status is triggered in the Request to Nominate/Activate process, candidates receive a message referencing their “offer.” This is highly inappropriate for external sourcing scenarios—such as a Request to Fill—where no offer exists.
This misalignment not only confuses candidates but also undermines the credibility of our recruitment process.
Ensuring that job card configuration and recruitment process selection are controlled/restricted is essential to maintaining a consistent, accurate, and candidate‑appropriate communication flow
There are two distinct job card types within the system: the custom job card used for Activations and the standard job card used for Request‑to‑Fill (Merit) processes. Each job card contains fields and data elements that are specific to its associated recruitment workflow. To maintain data integrity and ensure accurate candidate communication, the system must enforce strict validation so that only recruitment processes aligned to the selected job card type can be chosen. Recruitment processes that do not correspond to the job card type must be prevented from being selected. This can be achieved, but defaulting the process based on the job card selected, and making the recruitment process on the job card read only.
I wouldn't mind having the ability to set the Recruitment Process base on Team of User