Local and Global Conditions

What is a condition?

Conditions are rules in Ironclad that evaluate workflow data to determine what happens next. In Workflow Designer, conditions check whether something is true or false based on workflow data, which usually comes from properties populated by launch form answers and other workflow inputs.

In practice, conditions help you control workflow behavior. For example, you can use them to:

• generate the right document
  
• route the workflow to the right approvers
  
• show or hide content in a template
  

• show or hide questions or sections on a form
  

   

Global Conditions vs. Local Conditions

There are two types of conditions: local conditions and global conditions.

A local condition belongs to a specific workflow configuration. It is created and managed in Workflow Designer in the context of that workflow and is best for logic that only applies there. Some conditions might be local only, meaning they cannot be converted to global. This is most common when a condition references documents or parent/child/related record properties.

A global condition is a reusable condition that can be managed centrally in Conditions Manager and reused across workflow configurations. Updates to a global condition can be pushed to the configurations that use it, which reduces duplicate setup and ongoing maintenance.

In summary:

• use a local condition when the logic is specific to one workflow
• use a global condition when the same logic should be reused across multiple workflows

Conditions in Conditions Manager

Conditions Manager provides a centralized place to manage conditions.

In Conditions Manager, you can:

• view both local and global conditions
• make qualifying local conditions global
• update a global condition and push the change to every configuration that uses it
• delete global conditions
• see which workflow conditions and other configurations use a given condition

In summary, Conditions Manager brings local and global conditions into one library view, helping you identify repeated logic, decide what to promote to global for reuse, and manage those global conditions in one place.

Local conditions can only be updated in the relevant workflow configuration, which you can identify through Conditions Manager.

Conditions in Workflow Designer

You manage local conditions in Workflow Designer. Local conditions belong to one workflow configuration, so you must edit them in that workflow configuration.

Workflow Designer is where you apply both local and global conditions to your workflow configuration. You can use conditions to control forms, documents, approvals, signing behavior, and other parts of the configuration.

In Workflow Designer, conditions can control things like:

• clauses and other document language
• form questions and sections
• signer and role behavior based on workflow data
• document generation

You can create global conditions in Workflow Designer. When you do, they also appear in Conditions Manager.