User-input driven Conditionality in Matters

Learn how to configure smart, dynamic forms in DiliTrust Matters so that only the most relevant fields are shown to users based on the information they enter. This guide covers both the administrator configuration and the end-user experience.

✨ What is User-input driven Conditionality?

When filling out a Matter form, not every field is relevant in every situation. For example, if a matter concerns a domestic case, there is no need to display a "Foreign Jurisdiction" field. Showing too many fields at once creates confusion and slows down your team.

User-input driven Conditionality solves this by allowing administrators to set up smart rules on their Matter types. These rules automatically show or hide specific fields based on what a user selects in a trigger field — in real time, while the form is being filled in.

Example: If the field "Matter occurred in France?" is set to Yes, then the fields "Jurisdiction", "Foreign Jurisdiction", "City", and "Postal Code" are automatically revealed in the form — in the order defined by the administrator.

⭐ Key Benefits

• Cleaner forms — Users only see fields that are relevant to their specific case.
• Fewer input errors — Reducing irrelevant fields means less chance of incorrect or unnecessary data being entered.
• Faster matter creation — Legal teams can fill in forms more quickly with a streamlined, context-driven experience.
• Better data quality — The right information is captured for the right matter types, every time.
• Flexible ordering — Administrators can define the exact order in which conditional fields appear, ensuring a logical flow for users.

✅ Who Can Configure Conditions?

Conditional settings are configured by users with administrator access to Matter type configuration. End-users filling in matters do not configure conditions — they simply benefit from the streamlined forms that administrators have set up.

If you are not sure whether you have administrator access, please contact your DiliTrust workspace administrator or your internal legal operations team.

☝ How to Configure a Condition on a Field (Administrator)

Follow these steps to set up a conditional rule on a field within a Matter type:

Step 1 — Open your Matter type configuration

Navigate to your Matter type settings. You can access this from the administration panel by selecting the Matter type you want to configure (e.g., Litigation, General Matter, or a custom type).

Step 2 — Open the Field Settings of your trigger field

Click on the field that will trigger the condition — that is, the field whose value will determine whether other fields appear. For example, a field such as "Legal domain" or "Matter occurred in France?".

In the field settings panel, you will see two tabs: Field settings and Conditional settings. Click on Conditional settings.

Step 3 — Add a condition

If no conditions have been configured yet, you will see the message: "No conditions configured. You can add a condition to show another field when a specific value is selected."

Click the + Add condition button.

Step 4 — Define the trigger value(s)

In the "When value is one of" selector, choose the value(s) from the trigger field that will activate the condition. For example, select Yes if you want fields to appear when the user selects "Yes".

⚠️ Important: Only the exact values you select will trigger the condition. If a user selects a different value, the conditional fields will remain hidden.

Step 5 — Select the fields to reveal and define their order

In the "Then show fields in this order" selector, choose one or multiple fields from the same section that should become visible when the condition is triggered.

The fields will be displayed to the user in the order you define here. You can use the numbered ordering (e.g., 1. Jurisdiction, 2. Foreign Jurisdiction) to control the sequence clearly.

Step 6 — Save your configuration

Once you are satisfied with your condition setup, save the field configuration. The condition is now active on your Matter type.

✅ Tip: You can add multiple conditions on the same trigger field by clicking + Add condition again. Each condition can trigger different sets of fields for different selected values.

✌ How It Works for End-Users (Filling a Matter Form)

From an end-user's perspective, the experience is seamless and intuitive:

• When opening a Matter creation form (or editing a matter), users see only the fields that are relevant by default.
• As soon as the user selects a specific value in a trigger field, any conditional fields linked to that value automatically appear in the form — in the order defined by the administrator.
• If the user changes the trigger value to one that does not trigger the condition, the conditional fields are hidden again.
• Conditional fields that are mandatory are clearly marked with a * (red asterisk) — users must fill these in before they can save or submit the form.
• If a mandatory conditional field is left empty, an error message appears below the field to guide the user.

Example walkthrough:

1. User opens the "Create a matter" form for a Litigation matter type.
2. User fills in the field "Matter occurred in France?" and selects Yes.
3. Immediately, the fields Jurisdiction, Foreign Jurisdiction, City, and Postal Code appear in the form, in the order defined by the administrator.
4. User fills in those fields and saves the matter.
5. All conditional field values are correctly saved and visible in the matter details page.

✋ Tips and Best Practices

• Plan your conditions before configuring them. Map out which fields should trigger which other fields, and the order in which they should appear. This avoids the need for repeated edits.
• Keep sections organized. Conditional fields must belong to the same section as the trigger field. Make sure your Matter type sections are well structured before adding conditions.
• Avoid chaining conditions. A field that is already shown as a result of a condition (i.e., a "conditioned field") cannot itself be used as a trigger for another condition in the same Matter type. Plan accordingly.
• Test your configuration. After setting up conditions, simulate the matter creation flow as an end-user to make sure fields appear and disappear as expected.
• Communicate changes to your team. If you update the conditions on an existing Matter type, inform your team so they are aware of the updated form experience.

⚡ Current Limitations

• Conditions are section-scoped. You can only configure conditions between fields that belong to the same section within a Matter type. Cross-section conditionality is not currently supported.
• No chaining of conditional fields. A field that is already revealed by a condition cannot itself be used as a trigger field for another condition.
• Exact value matching only. Conditions are triggered by an exact match of the selected value(s). Partial matches or range-based conditions (e.g., "greater than X") are not supported for this feature.
• Conditions apply only to eligible field types. Not all field types support conditional settings. The Conditional settings tab is visible on all fields; however, the feature is only active for supported field types (e.g., select/list fields). If a field type does not support conditionality, the tab will display an informational message.
• Fields already used in conditions cannot be reused. A field that is already targeted by a condition in the Matter type cannot be selected as a target in another condition.

❓ Frequently Asked Questions

Can I set up multiple conditions on the same field?

Yes. You can add multiple conditions on a single trigger field. For example, if the field "Legal domain" has three possible values (Commercial, Employment, Criminal), you can configure a separate condition for each value, each revealing a different set of fields.

What happens to conditional field values if the trigger value is changed after creation?

If a user edits a matter and changes the trigger field value after creation, the conditional fields linked to the previous value will no longer appear. The values already saved in those fields will be preserved in the system but will not be visible unless the triggering condition is met again. We recommend communicating this behavior to your users.

Can I make a conditional field mandatory?

Yes. When configuring the field itself (in the Field settings tab), you can mark it as mandatory. When a conditional field is mandatory, users will be required to fill it in once it appears — the field will display a red asterisk (*) and an error message if left empty.

Will conditions apply when creating a matter AND when editing it?

Yes. Conditions apply both during matter creation (the creation popup/form) and in the matter details page when editing fields. The same display logic applies in both contexts.

Is the order of conditional fields important?

Yes. The order in which fields are listed in the "Then show fields in this order" selector determines the order in which they appear in the form. We recommend defining a logical, sequential order to guide users through the information naturally.

Can I remove or edit an existing condition?

Yes. Administrators can return to the Conditional settings tab of any trigger field and modify or delete existing conditions at any time. Changes take effect immediately for any new matter creation or editing session.

What if I don't see the "Conditional settings" tab on a field?

The Conditional settings tab is available on all field settings panels. If you do not see it, check that you are in the Matter type configuration view (administration panel), not in the Matter details view. If the issue persists, contact your DiliTrust administrator or reach out to our support team.

✍ Need Help?

If you have questions about configuring conditions or experience unexpected behavior, please contact the DiliTrust support team through your help center portal or reach out to your dedicated Customer Success Manager.