A disabled field in your Journey will be uneditable, and unclickable. Generally, you can tell a field is disabled on the interface as it will be greyed out.
An example of disabled fields in Loanapp are the following fields in the Setup section:
These fields a visible on screen, as they are important and should be able to be viewed by the user; but also disabled, as they are auto-populated from other systems and the user should not be able to edit them.
How to configure a field to be disabled
To make a field disabled, you need to make sure you are in Draft mode in Platform, find the field you want to make disabled, and scroll across to the Disabled Control:
The Disabled control gives you three options for managing if a field can be edited:
Disabled: Yes - this will mean that the field is DISABLED (not able to be edited) in your journey
Disabled: No - this will mean that the field is enabled, and ALWAYS editable in your journey
Disabled: Conditional - this will mean that the field is Disabled in your journey only when specified conditions are met
You will note in Platform, some fields do not have a Disabled control at all (the control is blank). This will mean that the field is editable by default.
Disabled on Condition
Disabled on Condition allows you to set a json expression to govern conditions that will lock the editing behaviour of the field.
Note that many fields have conditional Disabled logic configured in the standard Platform configuration. These standard conditions are based on best-practice. You are still able to modify these standard conditions if you wish.
As an example for setting conditional logic for the Disabled control, in the following screenshot, a number of the data capture fields for a Company Applicant are set to be Disabled on condition.
As background, Loanapp has a digital ABN lookup service to check a Government database, and populate this detail about a Company Applicant, where possible. So the conditional logic on these fields is set to say:
where the Company details are populated by the ABN Lookup service,
then Disable the field and make it un-editable
But where the Company details are not populated by the ABN Lookup service,
do not Disable the field, and make the field editable
If you click on the condition for any of these fields you will see this logic:
Which is saying:
where the Company ACN is populated by the ABN Lookup Service, Disable the field
But where it isnt populated by this service, do not Disable the field
In the Journey interface, this means that where the ABN Lookup Service has not been triggered/found a relevant record, the ACN field will still be editable:
However, when an ABN Lookup Service has been triggered to find the Company Applicant details:
Then when this detail is populated into the Company Applicant details, the fields will lock down to be disabled and no longer editable:
