Conditional Custom Properties

Conditional properties are about setting the visibility of a property based on the answer to another property. This can be compared to the skip logic feature that changes which question a user sees next, based on how they answer the current question. Conditional properties therefore provide a way to build complex forms by setting dependencies between custom properties.

In this article, we'll provide a scenario as an example, and go through the steps on how to create your own conditional custom properties. 

How Conditional custom properties are applied in a process

SCENARIO: The team manager has created a board to manage change requests. One key question is whether the change impacts existing applications, and if it does, which applications. Conditional properties have been used to only have to select the impacted application if the change indeed relates to an existing application.

• In the example below, the parent property'New Application' is set to identify whether 'yes' or 'no', the change request is related to a new application that will be built. The way the user/developer answers the 'New Application?' question will determine which questions they see next.

As per the example, the answer Yes will not provide another set of questions. But if the answer is No, then the conditional custom property applies with a necessary follow up question appearing for the developer to answer.

Based on the previous answer being 'No', the conditional property will have a list of options to align the correct areas that the request will be associated with.

That forms part of the conditional custom property process for each selected property. If a property is selected, there will be a value that is associated as a selection.

Step 1. Create the parent property

Each property starts off with the 'parent property' which is used as the base value that the child properties are applied/associated to. 

• Start by setting up the parent property that will be used as the primary conditional property. In this example, the 'New Application' is the parent property.

To define the specific details of parent/custom properties, you can have a view of understanding more on how to define/set up a custom property and complete all the fields by clicking here. 

Step 2. Set up a conditional custom property

Once the parent has been set up as 'New Application' to represent which application is associated with the new build, the child property can be created.

The child property will be set up as 'Applications affected by change' which will be the conditional property assigned to create the skip logic process. Based on the scenario example above.

• Continue by adding the options in the Property Value section that you want presented in the list of your conditional dependency.
  
  

To set up the conditional dependency between the two properties, you'll use the Property Dependency settings in the Conditional Property section.

• Select the parent property as the property dependency - in this case 'New Application'.
• Select the value that the conditional custom property is dependent on. In this case 'No'.
  
  

• With the conditional values set and the other property fields completed, the property can now be saved.

Conditional Custom Property Rules

The following points detail the rules around using conditional custom properties:

• Conditional custom properties can be set on any custom properties, including board properties.
• Conditional custom properties can only be set up against properties of type option or valued option (i.e property types that have a set list of values). 
• The parent property can be a custom property of the principal the custom property is added to. 

  • Custom properties: these are various custom property fields that have been added as additional reporting fields to better represent your organisation's data.

• A conditional custom property can only be linked to one parent property.  

  • However, it is possible to select more than one value for the parent property.
    • If more than one value is specified, this means that the current property will only be displayed if the linked property has one of the selected values.
• Deleting a primary property will remove the conditional configuration on the child properties.
  • A message will be displayed to the user to review the child properties if they exist.
• Updating the values of a parent property will inform the user if any child properties are impacted by the change.

Deleting Custom Properties with dependencies

The properties created will now have associated child/dependency properties. 

In the event that the properties are being updated, the previous properties can be deleted and in the case of conditional custom properties, the properties that are being deleted will notify the person editing them. This is due to them having linked child properties to them. 

• To delete the property, use the edit option to open the property.
  
  

If the parent property 'New Application' is deleted, a message will prompt you to confirm whether you'd like to delete or not as there are child properties linked to it.