Rules Best Practices

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