On Save
| Rules and examples |
|---|
|
| Warning | Work in progress! We are in the process of updating the information on this page. Subject to change. |
The On Save rules are checked when you save a record. Rules are client-side scripts that are executed when a user of the mobile app interacts with the app. Rules are no-code business logic, which are managed using the rules editor, usually in Woodford.
On Save rules are available for the following user interface components:
- Forms
- Editable views
- Questionnaires
- Process of On Save execution
- User initiate saving process.
- On Save rules are executed.
- Validation of whether the record can be saved (rules may interrupt save).
- If valid, the record is saved.
Forms
On Save rule on forms usually serves as a final field validation or they can automate changes in related records.
- Rule execution
- When you save a record.
Views
On Save rules can be used with views, but only when the Editable field is set. (Editable field, list, or editable grid is a feature that allows users to edit one or more records directly from the view, without a need to go to the form of a record.)
Questionnaires
Editing rules allow you to further customize the questionnaire form’s design and usage (hide or disable form fields, assign values to them, etc.).
- Rule execution
- When you save the questionnaire
- When you complete the questionnaire
Commands
- ErrorMessage
- A string variable where you can set an error message for form. In case of On Save event, this stops the saving.
ErrorMessage Assign Web site URL cannot be empty!
- WarningMessage
- A string variable where you can set an error message for form. In case of On Save event, this does not prevent saving, user can decide to continue.
WarningMessage Assign Web site URL is empty! Continue anyway?