Every placement created is named after the flow that created it. Scope a policy rule on "placement.name" and you control which policy an employee gets whether it is a job board applicant, a walk-in, or someone whose hire status just changed.
The following list contains every value that TempWorks writes to "placement.name", and the flow that produces each one.
*Note* For more information on configuring rules within policies, please see the article titled Onboarding - Policy Rule Operators.
List of Placement Names
| Value | Written when... | Additional Information |
|---|---|---|
| Assignment | An assignment syncs in from TempWorks. | Comes from the assignment sync, not from anything the employee does. This trigger is always on. |
| Candidacy | An employee applies through a job-apply link that carries one or more job orders. | A posting listing several job orders creates one placement per order on the same registration, each named Candidacy. |
| General Application | An employee applies through a job-apply link with no job order on it. | The careers-page, social and kiosk path. The employee picks a branch first, and you get a single placement. |
| Hire Status (status) | An employee's hire status in TempWorks changes to one you've selected on the hire-status placement trigger. | The status is appended in parentheses. For example, Hire Status (Active). When the status name isn't available, the raw status code lands there instead. |
| Candidate Status (status) | An employee's status against a specific job order changes to one you've selected on the job-order candidate-status trigger. | Also parenthesised. Because the webhook carries the order, the placement resolves to a job and a customer. |
Using a Name in a Policy Rule
To utilize a name within a policies rule, you will need to direct the rule's fact at "placement.name" and match the value.
- "equal": Select for one flow.
- For example, "placement.name equal Candidacy" assigns the packet only to job board applicants.
- "in": Select to cover several.
- For example, "placement.name in Candidacy, General Application" gives one policy to every applicant, however they had been added.
- "contains": Select for a family of statuses.
- For example, "placement.name contains Hire Status" catches every hire-status placement regardless of which status fired it.
*Note* An "equal" match against "Hire Status" is unable to be utilized. Hire-status and candidate-status placements always carry the status in parentheses, so the stored value is "Hire Status (Active)" instead of "Hire Status". You will need to use "contains" for the whole family, or "equal" against the full value including the parentheses.