Rule Chaining Patterns

1. Try multiple ways of finding a record #

Try multiple ways of finding a record

If multiple rules have the same slice output field, then rules will be skipped after one of the rules has been able to fill the slice output field.

2. Try to find a record, else create one #

Try to find a record, else create one

If multiple rules have the same slice output field, then rules will be skipped after one of the rules has been able to fill the slice output field. This is not limited to one rule type.

3. Try to find a record and update the record #

Try to find a record and update the record

The lookop slice input field is a required slice input field for the update rule. So if no record is found, it will also not update.

4. Try to find a record and update the record if found, else create one #

Try to find a record and update the record if found

If found, the update record has its required slice input field filled and will execute. The create rule does not have room to store the new record id and will be skipped.

If not found, the update record does not have its required slice input field and will be skipped. The create rule however does have room to store the new record id and will execute.

Note that it’s important that the update rule comes before the insert rule. Else the update rule will always be executed. Also if it was not found but created.

5. Try multiple ways of finding a record and update the record if found, else create one #

Try multiple ways of finding a record and update the record if found, else create one

Combination of previous patterns.

Copyright © 2024 all rights reserved, powered by Sliced Bread Software B.V.