Choose where you’d like to start

Enable | Disable

Overview
Syntax
Example
- Example 1
- Example 2
Use Case Scenarios
- Scenario 1: Enabling field in a job application form

Note: This task is applicable only to Zoho Creator.

Overview

The Disable deluge task disables a specified field on the form. The disabled field will be grayed out, and the user will not be able to add data to that field.

The Enable deluge task reverses the Disable action and re-enables a disabled field for users to fill it out in the form.

Note:

To disable fields for a set of users, you can define field permissions.

Syntax

To disable a field

disable <field_link_name>;

To disable a subform field

disable row.<subform_field_link_name>;

To enable a field

enable <field_link_name>;

To enable a subform field

enable row.<subform_field_link_name>;

Param	Explanation
<field_link_name> & <subform_field_link_name>	Link name of the field which needs to be disabled or re-enabled. Points to keep in mind for this parameter: Since the Autonumber field type is not displayed in a form, it cannot be specified in this task. For composite field types like Name and Address, the action of disabling/enabling the main field will be applied to all its subfields, by default. To enable/disable a particular subfield you must specify it along with the main field, for example: disable Name.last_name; The action of disabling/enabling the Section field type is not supported.

Param

Explanation

<field_link_name> & <subform_field_link_name>

Link name of the field which needs to be disabled or re-enabled.

Points to keep in mind for this parameter:

Since the Autonumber field type is not displayed in a form, it cannot be specified in this task.
For composite field types like Name and Address, the action of disabling/enabling the main field will be applied to all its subfields, by default. To enable/disable a particular subfield you must specify it along with the main field, for example: disable Name.last_name;
The action of disabling/enabling the Section field type is not supported.

This task can be used in the following events

When a record is Created
Workflow event	For form fields	For subform fields
On Load	Yes	No
On Validate	No	No
On Success	No	No
On User input	Yes	No
On user input of a subform field	No	Yes
Subform on add row	Yes	Yes
Subform on delete row	Yes	Yes
When a record is Created or Edited
Workflow event	For form fields	For subform fields
On Load	Yes	No
On Validate	No	Yes
On Success	No	No
On User input	Yes	No
On user input of a subform field	No	Yes
Subform on add row	Yes	Yes
Subform on delete row	Yes	Yes
When a record is Edited
Workflow event	For form fields	For subform fields
On Load	Yes	No
On Validate	No	No
On Success	No	No
On User input	Yes	No
On user input of a subform field	No	Yes
On Update	Yes	No
Subform on add row	Yes	Yes
Subform on delete row	Yes	Yes
When a record is Deleted
Workflow event	For form fields	For subform fields
On Validate	No	No
On Success	No	No
Other workflow events
Workflow event	For form fields	For subform fields
On a scheduled date	No	No
During approval process	No	No
During payment process	No	No
In a Custom Function	No	No
In an Action item in report	No	No

Example 1

The following snippet disables the "Total Amount" field.

disable Total_Amount;

Example 2

The following snippet disables the cost field in the subform of the order placement form.

disable row.cost;

Scenario 1: Enabling field in a job application form

Consider a job application form where there is a decision box field to distinguish the experienced and fresher candidates category. Based on the user input of the decision box field, the number field to record the years of experience will be enabled or disabled. If the candidate selects the category as experienced, the number field wiI ll be enabled to to get work experience.

if ( category == "experienced") 
{ 
enable experience_in_years; 
} 
else 
{ 
disable experience_in_years; 
}

Get Started Now

Execute

Deluge

The fastest programming language for developers