Status-driven Conditionality in Matters

Status-driven conditionality allows you to dynamically show, hide, or require specific fields based on the status of a Matter. This ensures that users only see and complete relevant information at the right time in the Matter lifecycle.

✨ What is Status-driven Conditionality?

Status-driven conditionality automatically adapts field behavior depending on the current status of a Matter (e.g., Creation, Open, Closed).

• Fields can appear or disappear depending on status
• Fields can become mandatory only at specific stages
• Users are guided with pop-ups when actions require additional information

For example:

• When a Matter is marked as Closed, a pop-up can require users to fill in a Closing Date before proceeding

✅ Key Benefits

• Improves data quality by enforcing required inputs at the right time
• Reduces clutter by hiding irrelevant fields
• Guides users through business processes step by step
• Prevents incomplete Matter closure

✍ How to Configure Status-driven Conditionality

1️⃣ Access Matter Type Settings

• Go to Matters module
• Open Matter Type configuration
• Select the custom field you want to configure

2️⃣ Define When the Field Should Appear

• Choose when the field should be displayed:
  • At Matter creation
  • When the Matter is open
  • At Matter closure

3️⃣ Set Mandatory Rules

• Decide if the field should be required:
  • Optional
  • Mandatory at creation
  • Mandatory at closure

4️⃣ Save Your Configuration

• Click Save to apply your rules

⛔ What Happens During Usage?

At Matter Creation

• Only fields configured for creation are displayed
• Mandatory fields must be completed before creating the Matter

During Matter Lifecycle

• Fields can appear or change depending on status updates
• Default values may be automatically applied if configured

At Matter Closure

• A pop-up may appear requiring specific fields to be filled
• Mandatory fields block closure until completed

⚠️ Important Behaviors & Rules

• If no fields are configured for creation or closure, a warning message may appear
• Fields configured only for closure do not block Matter creation
• Mandatory fields at closure will prevent closing until completed
• Default values are applied when configured in the Matter Type

⭐ Usage Tips

• Keep creation forms simple by limiting required fields
• Use closure requirements to ensure complete data before finalizing
• Test your configuration with different statuses to verify behavior
• Use clear field labels to guide users in pop-ups

❗ Limitations to Be Aware Of

• Fields configured incorrectly may block actions (e.g., closing a Matter)
• Removing and re-adding a field resets its configuration
• Some behaviors depend on proper Matter Type setup

❓ Need Help?

If you experience issues with field visibility or mandatory rules, contact your administrator or support team.

Status-driven conditionality is designed to make your workflow smoother—configure it thoughtfully to get the best results. ✨