Rules Best Practices

VMS Sync'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.

Learn more about Rules Best Practices below. For additional information on how rules are applied see How Rules are Applied.

Priority

Higher priority rules run first. To avoid rule interference, general conditions should have a higher priority, while specific conditions should have a lower priority.

  • A rule with Priority = 100 runs before a rule with Priority = 1.
  • Priority supports both zero and negative values.
  • It's recommended to add non-sequential rule priorities.
    • Example: 10, 100, 200, 300 instead of 1, 2, 3, 4

For example, a credential has multiple buyers, and you want Buyer A assigned to User A and all other Buyers assigned to User B.

  • You can add a higher priority rule to assign User B to most reqs, and a lower priority rule to overwrite this value with User A when appropriate.
    • Rule 1 (Priority 100) = no IF condition, THEN atsFields.owner = User B ID
    • Rule 2 (Priority 10) = IF buyerDetails.company = Buyer A, THEN atsFields.owner = User A ID

Use IDs

Rules that set ATS values should be saved as IDs (rather than names) in the ATS database.

Example: owner, type, clientCorporation, category, etc

To learn how to create Rules, see Adding New Rules.