On Execute: Difference between revisions

Revision as of 13:20, 12 September 2022

Rules and examples
On Load On Change On Save On Create Select Form Row Script On Execute On Can Execute Cell Click Button Click On Item Added On Item Completed On Repeat On Delete Form rules Rules on the bulk update form Command rules Questionnaire Designer examples Rules editor Global constants

Warning

Work in progress! We are in the process of updating the information on this page. Subject to change.

App users can execute commands from their app, for example, run a mobile report or delete several records at once. Predefined commands usually function out of the box. However, you can use rules to define their availability and tweak their function. On Execute lets you define actions that the command performs. This rule is triggered when the command button is pressed. For example, It can be filling in some data, hiding fields, etc. On Can Execute rule then modifies conditions of execution for that specific command.

On Execute is available for the following user interface components:

In Woodford, you can edit the commands available for a form. In Questionnaire Designer, you can edit the commands available when filling out a questionnaire.

Commands

List of available form and questionnaire commands can be found here.

Examples of custom commands

Field clearing command

We created a custom command custom_del_street. When clicked, Entity.addres1_line1 field is cleared.

If Condition	Command.Name	Equals	custom_del_street
Then Step	Entity.addres1_line1	Clear

@@ Line 15: / Line 15: @@
 List of available form and questionnaire commands can be found [[Command editor#Available commands|here]].
-===Example of a simple custom command===
+==Examples of custom commands==
+===Field clearing command===
 We created a custom command custom_del_street. When clicked, Entity.addres1_line1 field is cleared.
 {| class="wikitable"