1. Actions in field rules 

The actions in the field rules event help define the behavior of fields within a form based on specific conditions. These client actions dynamically respond to user interactions throughout the session, allowing you to control the visibility, accessibility, and values of fields. This streamlines data entry and enhances form usability. These actions are configured based on the selected form event and record event during form workflow creation, determining how individual fields react to user interaction. The list of actions that can be associated with the field rules event is provided below.

1. Hide fields - Hides the field in the form, making it invisible to the user.
   
2. Show fields - Makes the field in the form visible to the user.
   
3. Disable fields - Disables the field, preventing any user interaction.
   
4. Enable fields - Enables the field, allowing user interaction and input.
   
5. Set field value - Automatically sets a predefined value to a field in the form.
   
6. Show/Hide subform actions
   
1. Hide subform add entry: Hides the Add New button in a subform, preventing additional entries.
   
2. Show subform add entry: Displays the Add New button in a subform, allowing users to add new rows.
   
3. Hide subform delete entry: Hides the Delete button in a subform, preventing row deletions.
   
4. Show subform delete entry: Displays the Delete button in a subform, allowing users to remove rows.
   

1.1 Hide fields 

By default, all fields in a form are visible to the user. The hide fields action allows you to set conditions to hide specific fields from the user. This action is a no-code alternative to the Deluge hide fields task.

Note:
The hidden field can be displayed by configuring the show fields action or the Deluge show fields task.

1.1.1 Configure hide fields action 

1. Create a form workflow by selecting the record event and supported form event (Field rules) for configuring the hide fields action.
   
2. Click Add New Action in the workflow builder. The Add New Action window will slide in from the right.
   
3. Select when to run this action. By default, it is set to Always, which means the action will execute for all records. To run the action only for specific records, choose on condition and define the necessary condition or criteria. Learn more about configuring conditions in a workflow.
   
4. Choose the Hide fields action.
   
5. Select the fields you want to hide from the Select Fields dropdown, which lists all the fields in your form, and click Save.
   
6. Click Done in the top-right corner of the screen.
   
   

1.2. Show fields 

The show fields action allows you to display fields in a form based on specific conditions. This is useful for creating dynamic forms that adapt to user input by revealing only the relevant fields. This action is an no code alternative to the Deluge show fields task and can be configured directly via UI.

A field can be shown only if it has been previously hidden using the hide fields action or Deluge hide fields task. You can also configure a condition to show the field when the condition evaluates to true.

Note: Ensure that the field is initially hidden using the hide fields action or Deluge hide fields task. Only then can it be shown dynamically using this action when the defined conditions are satisfied. 

1.2.1. Configure show fields action

1. Create a form workflow by selecting the record event and supported form event (Field rules) for configuring the show fields action.
   
2. Click Add New Action in the workflow builder. The Add New Action window will slide in from the right.
   
3. Select when to run this action. By default, it is set to Always, which means the action will execute for all records. To run the action only for specific records, choose on condition and define the necessary condition or criteria. Learn more about configuring conditions in a workflow.
   
4. Choose the Show fields action.
   
5. Select the fields you want to show from the Select Fields dropdown, which lists all the fields in your form, and click Save.
   
   

   Note: Ensure that the selected fields are initially hidden using the hide fields action or the Deluge hide fields task for this action to work. 
   
6.  Click Done in the top-right corner of the screen.
   
   

1.3. Disable fields 

By default, all fields in a form are enabled, allowing users to input or modify data. The disable fields action allows you to restrict input by disabling specific fields either when the form loads or based on certain conditions. This action serves as an no-code alternative to the Deluge disable fields task. Disabled fields appear grayed out and cannot be edited by the user until they are re-enabled using the enable fields action or Deluge enable fields task. This is useful when certain fields should only be editable under specific circumstances.

1.3.1. Configure disable fields action 

1. Create a form workflow by selecting the record event and supported form event (Field rules) for configuring the disable fields action.
   
2. Click Add New Action in the workflow builder. The Add New Action window will slide in from the right.
   
3. Select when to run this action. By default, it is set to Always, which means the action will execute for all records. To run the action only for specific records, choose on condition and define the necessary condition or criteria. Learn more about configuring conditions in a workflow.
   
4. Choose the Disable fields action.
   
5. Select the fields you want to disable from the Select Fields dropdown, which lists all the fields in your form, and click Save.
   
6. Click Done in the top-right corner of the screen.
   
   

1.4. Enable fields

The enable fields action is used to re-activate fields that were previously disabled using the disable fields action or Deluge disable fields task. This action is triggered when a defined condition evaluates to true, allowing users to interact with the field dynamically. This action is a no-code alternative to the Deluge enable fields task and can be configured directly via UI.

Note: Ensure that the field is initially disabled using the disable fields action or Deluge disable fields task. Only then can it be enabled dynamically using this action when the defined conditions are satisfied. 

1.4.1. Configure enable fields action

1. Create a form workflow by selecting the record event and supported form event (Field rules) for configuring the enable fields action.
   
2. Click Add New Action in the workflow builder. The Add New Action window will slide in from the right.
   
3. Select when to run this action. By default, it is set to Always, which means the action will execute for all records. To run the action only for specific records, choose on condition and define the necessary condition or criteria. Learn more about configuring conditions in a workflow.
   
4. Choose the Enable fields action.
   
5. Select the fields you want to show from the Select Fields dropdown, which lists all the fields in your form, and click Save. 
   
   Note: Ensure that the selected fields are initially disabled using the disable fields action or the Deluge disable fields task for this action to work. 
   
   
6. Click Done in the top-right corner of the screen.
   
   

1.5. Set field value

The set field value action allows you to assign a predefined value to a field in the form. It serves as a no-code alternative to the Deluge set field value task and is useful for automatically populating fields with default or context-specific values based on conditions defined in the workflow.

When configured, the field is pre-filled with the specified value either when the form loads (if no condition is applied) or dynamically, when the user action meets the specified conditions during form interaction. For example, if a condition is set to check whether the 'Country' field is 'India' and the user selects 'India,' the predefined tax value (such as '18%') will be automatically applied to the 'Tax' field.

Note:

1. This action sets a field with a predefined value dynamically based on specified criteria. If no criteria are configured, the field is prefilled with the value when the form loads. It does not disable or lock the field.
   
2. To make the field read-only after assigning a value, you can combine the set field value action with the disable fields action. This ensures that the prefilled value cannot be modified by the user.
   
3. Alternatively, to set a field value when the form loads without any criteria, use the Initial value option in the field properties.
   
4. Ensure that the value set using the set field value action stays within the field’s maximum digit or character limit to avoid errors during form submission.
   
5. You cannot set values using the set field value action for the following field types:
   
1. Basic fields: Drop down, Radio, Multi select, and Check box.
   
2. Advances fields: Decision box, Image, Audio, Video, File upload, QR/barcode, Auto number, Formula, Signature, lookup, and subform.
   
3. Special fields: Add notes, Users, Integrations, and AR.
   
4. AI fields: Prediction, Keyword extraction, Sentiment analysis, OCR, and Object detection.
   

1.5.1 Configure set field value action

1. Create a form workflow by selecting the record event and supported form event (Field rules) for configuring the set field value action.
   
2. Click Add New Action in the workflow builder. The Add New Action window will slide in from the right.
   
3. Select when to run this action. By default, it is set to Always, which means the action will execute for all records. To run the action only for specific records, choose on condition and define the necessary condition or criteria. Learn more about configuring conditions in a workflow.
   
4. Choose the Set field value action.
   
5. Select the field in the Field name dropdown and assign a value to it in the Field value field.
   
6. Click add icon (+) to set value to another field and delete icon () to remove it. Click Save after configuring the preferred fields with values.
   
7. Click Done in the top-right corner of the screen.
    

1.6. Hide subform add entry action

Note: This action can only be configured for forms with subforms.

The hide subform add entry action hides the + Add new button in a subform dynamically, preventing users from adding new entries to the subform. This is useful when additional entries should not be allowed based on specific conditions.

Note: The hidden add entry button can be displayed by configuring the show subform add entry action. 

Example: In a Creator Payroll application, the employees are required to submit expense details through a subform in Expense Reimbursement form. If the total expense amount exceeds the allowed reimbursement limit, the hide subform add entry action can be triggered to prevent adding more entries. This ensures compliance with the organization’s reimbursement policy.

1.6.1. Configure hide subform add entry action

1. Create a form workflow by selecting the record event and supported form event (Field rules) for configuring the hide subform add entry action.
   
2. Click Add New Action in the workflow builder. The Add New Action window will slide in from the right.
   
3. Select when to run this action. By default, it is set to Always, which means the action will execute for all records. To run the action only for specific records, choose on condition and define the necessary condition or criteria. Learn more about configuring conditions in a workflow.
   
4. Choose the Show/Hide subform actions.
   
5. Choose Hide subform add entry action
   
6. Select the subform field in for you want to hide subform add entry from the Select Fields dropdown, which lists all the subform fields in your form, and click Save.
   
7. Click Done in the top-right corner of the screen.
   

1.7. Show subform add entry

Note: This action can only be configured for forms with subforms.

The show subform add entry action displays the + Add new button in a subform dynamically, allowing users to add additional entries. This action is useful only when the button was previously hidden using the hide subform add entry action and needs to be conditionally revealed based on user input or business logic.

Note: Ensure that the Add new button is initially hidden using the hide subform add entry action. Only then can it be shown using this action when defined the condition are satisfied. 

Example: In a Zoho Creator audit application, When the auditor selects 'Additional checks required' in a field audit form, the show subform add entry action is triggered to display the Add new button in the checklist subform. This allows the auditor to add custom checklist items relevant to the specific audit scenario, keeping the form streamlined and expandable only when additional scrutiny is needed.

 1.7.1. Configure show subform add entry action

1. Create a form workflow by selecting the record event and supported form event (Field rules) for configuring the show subform add entry action.
   
2. Click Add New Action in the workflow builder. The Add New Action window will slide in from the right.
   
3. Select when to run this action. By default, it is set to Always, which means the action will execute for all records. To run the action only for specific records, choose on condition and define the necessary condition or criteria. Learn more about configuring conditions in a workflow.
   
4. Choose the Show/Hide subform actions.
   
5. Choose Show subform add entry action.
   
6. Select the subform for which you want to enable the 'Add Entry' option from the Select Fields dropdown, and then click Save.
   

   Note: Ensure that the selected subform field's add entry is initially hidden using the hide subform add entry action for this action to work.

   
7. Click Done in the top-right corner of the screen.
   

1.8. Hide subform delete entry 

Note: This action can only be configured for forms with subforms .

The Hide subform delete entry action hides the delete button () in a subform dynamically, preventing users from removing any existing entries. This is useful when subform data should remain intact once entered, especially in scenarios where deletion may compromise data accuracy or violate audit requirements.

Note: The hidden delete button can be displayed by configuring the show subform delete entry action. 

Example: In a Creator Inventory Management application, warehouse staff record received goods in a subform within the Goods Receipt form. To maintain inventory accuracy, once an item entry is added, the hide subform delete entry action can be triggered to prevent users from deleting the received entries. This ensures that all recorded goods remain traceable and auditable.

 1.8.1. Configure hide subform delete entry action

1. Create a form workflow by selecting the record event and supported form event (Field rules) for configuring the hide subform delete entry action.
   
2. Click Add New Action in the workflow builder. The Add New Action window will slide in from the right.
   
3. Select when to run this action. By default, it is set to Always, which means the action will execute for all records. To run the action only for specific records, choose on condition and define the necessary condition or criteria. Learn more about configuring conditions in a workflow.
   
4. Choose the Show/Hide subform actions.
   
5. Choose Hide subform delete entry action
   
6. Select the subform field in for you want to hide subform delete entry from the Select Fields dropdown, which lists all the subform fields in your form, and click Save.
   
7. Click Done in the top-right corner of the screen.
    

1.9. Show subform delete entry 

Note: This action can only be configured for forms with subforms.

The show subform delete entry action displays the delete button in a subform dynamically, allowing users to remove existing entries when needed. This is useful in scenarios where users should have the flexibility to manage subform data dynamically such as correcting errors or updating form details.

Note:
This action is typically used in combination with conditions to control when deletion is to be permitted.

Ensure that the delete button is initially hidden using the hide subform delete entry action. Only then can it be shown using this action when the defined conditions are satisfied.

Example: In a Manufacturing Quality Control app, inspectors use a subform in the Inspection Form to log inspection failures. After form submission, the Hide subform delete entry action is triggered to prevent edits. However, if the 'Allow delete entries' option is enabled, typically by a supervisor, the Show subform delete entry action is triggered, allowing entry deletion when necessary. This provides controlled flexibility for managing inspection records.

1.9.1.Configure show subform delete entry action

1. Create a form workflow by selecting the record event and supported form event (Field rules) for configuring the show subform delete entry action.
   
2. Click Add New Action in the workflow builder. The Add New Action window will slide in from the right.
   
3. Select when to run this action. By default, it is set to Always, which means the action will execute for all records. To run the action only for specific records, choose on condition and define the necessary condition or criteria. Learn more about configuring conditions in a workflow.
   
4. Choose the Show/Hide subform actions.
   
5. Choose Show subform delete entry action.
   
6. Select the subform field in for you want to show subform add entry from the Select Fields dropdown, which lists all the subform fields in your form, and click Save.
   Note: Ensure that the selected subform field's delete entry is initially hidden using the hide subform delete entry action for this action to work. 
   
7. Click Done in the top-right corner of the screen.
   

2. Related topics

1. Form workflow actions
2. Configure notification actions for form workflows
3. Configure data access actions for form workflows
4. Configure integrations for form workflows
5. Configure Deluge script for form workflows