Skip to content

Conditions

A condition is the test a file must pass for a rule to raise a request. Under When in the rule editor, add one or more conditions, and say whether all or any of them must hold. You can nest groups.

A condition in the builder
A condition in the builder

Send for approval when these conditions hold. Add more to require all (or any) of them. The builder is the same one Forms uses for its logic. Each condition is a fact, an operator and a value.

FactTypeNotes
Each custom fieldIts own typeEvery field the tenant defines.
File extensionTextFor example xlsx.
ShareChoiceThe share the file is on.
Submitter’s groupUser or groupA group the editing user is in.
Raised by formChoiceA form that wrote the file. The lookup must succeed, or the rule leaves an open request alone.
Sensitivity labelChoiceThe Governance label on the file. Offered to sharing rules.

A Sharing that needs approval rule can also test what the request asks for and what the link would be:

  • Adds people in the organisation
  • Adds outside recipients
  • Outside recipients
  • Outside recipients’ domains
  • Days until it expires

is, is not, less than, at most, greater than, at least, includes, does not include, is on, is not on, is before, is after, is empty and is answered. A field offers the ones that fit its type. is empty and is answered take no value.

A condition that will not compile or will not evaluate counts as false. A broken rule never routes everything. The builder checks the condition when you save.

A rule re-checks only when an edit changed a field the rule uses. A condition that uses no field re-checks on every edit.

From the second step on, Only require this step when adds a condition to the step. If these conditions do not hold when the previous step is approved, the step is skipped. The first step always applies, so it cannot carry one. See Steps and approvers.