Skip to content

Smart eForms Dynamic Logic Properties

Dynamic Logic Properties are properties on data types that allow the dynamic control of when:

  • Fields are read only
  • Fields are required
  • Fields are visible
  • Field 'Options' are available (Enum, Array, Multi-Enum and Checklist data types)

The conditions for setting these values are checked automatically when data in the field is changed.

Conditions are configured via the Fields Editor in Form Version.

Dynamic Options

For Enum, Array, Multi-Enum, Checklist fields it is possible to define different sets of Options (Items) that are available for the field depending on which condition is met.

This is sometimes referred to as Dynamic Picklists.

This also takes into account the order of the Options.

The best way to explain this is with an example. This example has two fields:

  1. Enum data type called Season. This will have Options/Items named as per the seasons.
  2. Array data type called Colour. This will have a set of Option/Items of various names of colours.

Selecting a Season will control the values that can be selected in the Colour field as per the following:

  • Spring
  • Cream
  • Honey
  • Biscuit
  • Light Tan
  • Ginger
  • Corn Yellow
  • Yellow Ochre
  • Summer
  • Cameo Rose
  • Lilac Pink
  • Cyclamen
  • Dusty Orchid
  • Musk Rose
  • Dolphin Grey
  • Greystone
  • Autumn
  • Macadamia
  • Honey
  • Walnut
  • Camel
  • Tan
  • Sienna
  • Brick Red
  • Winter
  • Ice Blue
  • Cobalt Blue
  • Sapphire
  • Navy
  • Lobelia
  • Light Emerald
  • Emerald

Click the + button on the ** Dynamic Logic Options ** on the Colour field as per the following image:

Smart eForms Dynamic Logic Options 1 - Light Smart eForms Dynamic Logic Options 1 - Dark

This will display all the Colour Options. We are setting the available values for the Season = 'Spring'.

This is also where you can control the order of the Options. Drag and drop them in the order you require.

Smart eForms Dynamic Logic Options 2 - Light Smart eForms Dynamic Logic Options 2 - Dark

Now define the Conditional Logic required to display the Colours for Spring.

Smart eForms Dynamic Logic Options 3 - Light Smart eForms Dynamic Logic Options 3 - Dark

Smart eForms Dynamic Logic Options 4 - Light Smart eForms Dynamic Logic Options 4 - Dark

This has completed the logic for the Spring Colours.

Repeat this for Summer, Autum and Winter colours.

Smart eForms Dynamic Logic Options 5 - Light Smart eForms Dynamic Logic Options 5 - Dark

The end results should look at follows:

Smart eForms Dynamic Logic Options 6 - Light Smart eForms Dynamic Logic Options 6 - Dark

Click the 'Save' button at the top of the screen and add the Season and Colour fields to your required page layout.

You should now be able to test that when you select a specific Season you will only have a subset of the Colours to select from.

Dynamic Read only

Dynamic Read only allow you to set a field to be read only depending on the value of another field.

An example for this can be: If the Status field holds the value of Disabled, the Name field will be read only.

First, we create the 2 fields: A Name field of type Text and a Status field of type Enum. Status field will have the following values:

  • Open
  • Active
  • Disabled

Click the Edit button on the ** Condition Making Field Read only ** on the Name field as per the following image:

Smart eForms Dynamic Read only 1 - Light Smart eForms Dynamic Read only 1 - Dark

Now click And to define the Conditional Logic to make Name field read only as per the following image:

Smart eForms Dynamic Read only 2 - Light Smart eForms Dynamic Read only 2 - Dark

Click the 'Save' button at the top of the screen.

You should now be able see the Dynamic Read only logic.

Smart eForms Dynamic Read only 3 - Light Smart eForms Dynamic Read only 3 - Dark

Dynamic Required

Any fields can have a Dynamic Required logic. Dynamic Required allow you to set a field to be required depending on the value of another field.

Let's take a look at an example: When user selects payment method, if the method of Credit Card is selected, the field Credit Card Number will be required.

The Payment Method field will have the following values:

  • Cash
  • Credit Card
  • Bank Transfer

The Credit Card Number will be a Text input field.

Click the Edit button on the ** Condition Making Field Required ** on the Payment Method field as per the following image:

Smart eForms Dynamic Required 1 - Light Smart eForms Dynamic Required 1 - Dark

Now click And to define the Conditional Logic to make Credit Card Number field required.

Smart eForms Dynamic Required 2 - Light Smart eForms Dynamic Required 2 - Dark

Click the 'Save' button at the top of the screen.

You should now be able see the Dynamic Required logic.

Smart eForms Dynamic Required 3 - Light Smart eForms Dynamic Required 3 - Dark

Dynamic Visibility

Dynamic Visibility is a feature that allow you to make a specific field only visible to users depending on the users' input value of one or another fields.

Let's take a look at an example. If the user checks the checkbox Use a different postal address, another address field called Postal Address will be visible.

Hence, we have 2 fields to look at:

  • Use a different postal address: Boolean type.
  • Postal Address : Address type.

Click the Edit button on the ** Condition Making Field Visible ** on the Postal Address field as per the following image:

Smart eForms Dynamic Visibility 1 - Light Smart eForms Dynamic Visibility 1 - Dark

Now click And to define the Conditional Logic to make Postal Address field visible to users.

Smart eForms Dynamic Visibility 2 - Light Smart eForms Dynamic Visibility 2 - Dark

Click the 'Save' button at the top of the screen.

You should now be able see the Dynamic Visibility logic.

Smart eForms Dynamic Visibility 3 - Light Smart eForms Dynamic Visibility 3 - Dark

See also