Common Rules Use Cases
's Rules engine allows administrators to apply client-specific business logic to positions during the sync process. Rules are structured as If/Then statements and run after company, skill, and flex mappings have been applied. Rules can be assigned either account wide or at the credential level, and each rule is assigned a priority number that determines the order in which rules are applied.
Administrators with elevated permissions can create, edit, and delete rules directly in VMS Sync Admin Tools without contacting VMS Sync Support.
A few common Rules Use Cases include:
- Ignore reqs based on a specific VMS field value
- Apply rule logic to new, existing, or all positions
- Set an ATS field to a static value
- You can use a VMS field value to set ATS field values conditionally
- Set an ATS field to a VMS value
- Replace: Single VMS field
- Template: Multiple VMS fields
- Append VMS values to an ATS field
Was this helpful?