Conditional Fields and Relations
Conditional Fields
Overview
We have the functionality to set-up Conditional Fields on Fact Sheets, which are activated (displayed) only when the activator field has the necessary value(s) selected.
For example, in the below image the text field "Conditional Field Result" is set to be activated only when "Conditional Field" has the value "Yes". It is called the "Trigger Value".

The field "Conditional Field Result" is hidden (deactivated) when "Conditional Field" has the value "No".

FAQs
- The activator field can only be of type SINGLE_SELECT or MULTIPLE_SELECT
- Conditional fields will only be displayed after the saving of the activator field and not during change
- We can configure multiple Trigger Values in Activator field for the functionality to work
- The base fields of a Fact Sheet, eg. Description, can not be made conditional fields
- If a Conditional Field is also a Mandatory Field, then the field being “Mandatory“ is only applied when the activation conditions are fulfilled
- Mandatory subscription roles can not be made conditional
Conditional Relations
Overview
It is also possible to create a conditional relation. This is an example for a 2 way conditional relation using subtypes of Application Fact Sheet type.
"businessSolutionApplicationRelation": {
"from": {
"factSheetType": "Application",
"multiplicity": "*",
"activatedBy": {
"category": [
"businessSolution"
]
},
"name": "relBusinessSolutionApplicationToApplication"
},
"to": {
"factSheetType": "Application",
"multiplicity": "*",
"activatedBy": {
"category": [
"application"
]
},
"name": "relApplicationToBusinessSolutionApplication"
},
"fields": {
"description": {
"validators": null,
"type": "STRING"
}
},
"constrainingRelations": null,
"constraints": []
},
Usecases
Please reach out to support through our Support Form Submission or reach out to your CSM to implement a use-case with conditional fields.
Updated about 1 month ago