I am setting up some objects in Salesforce to help us with our HR processes. I have created a few different custom objects. First is Position which will house all of the positions we have within our agency. Next is Position Posting. This is the detail in a master-detail with Position. It is where supervisors can 'request' a new posting be done for that position. For instance, if we have "Case Worker" as a position and we have a case worker leaving, the supervisor can go into the Case Worker position record and create a Position Posting record with information relevant to the current vacancy. This way, we are not re-inventing the wheel every time we want to post one of our common positions.
Then, I have created a Candidates object. This is where the HR manager can store info about the candidates who apply for jobs. Because Candidates can and often do apply for multiple positions, I created another object called "Job Application." This is the detail in a master-detail with Candidates and looks up to the Position Posting record. This way, on a Candidate record, we can see all of the positions a candidate has applied for in the Job Applications related list and we can look at a Position Posting record and see all of the Candidates who have applied in the Job Applications related list on Position Posting.
The HR manager wants the supervisors to review the candidates (the Job Applications object) and have them approve or reject the candidate for interview.
I am struggling with building this approval process and routing this to the appropriate approver.
First, I created a couple of lookup fields to User on Position Posting. This would be "Supervisor 1" and "Supervisor 2." Then I realized-those lookup fields aren't available to me in an approval process built on Job Application. I could create approval processes with entry criteria based on department and then specify certain users as approvers but I don't like building things in Salesforce built on specific users as our staff come and go.
I thought about creating a couple of lookup fields on Job Application that would not be on the page layout but that I could trigger with Process Builder to update when a job application record is created with the IDs of the supervisors on Position Posting.
In actuality, what I'd really prefer to do is have the approver be based on our role hierarchy. There are certain roles I would want to always be the approver for certain positions. However, there's no way I can see to set it up based on role. I made a picklist but I can only use that for approval submission criteria, not approver.
What would you all do in this instance? Should I try the process builder update and create a couple of hidden lookup fields on Job Application? Or is there a better way I am missing?
Any advice or input is appreciated. Thank you!
1 réponse
I have done what you are talking about with populating related user fields on the records that need approval with information to keep them hidden and use in the approval process.
You can reference information from the owner of the record would that help in your scenario with the requrements you have?
