Skip to main content

Despapeliza

  • sales@despapeliza.io
Despapeliza
Menu
  • Home
  • Products
    • Legale CLM
    • Legale GRC
    • Legale Sign
    • Legale AI
    • Legale API
    • Legaliza
    • Digitization
  • Solutions
    • Legal
    • Human Resources
    • Occupational Risk Prevention
    • Sales
    • Finance
  • Resources
    • Governance
    • What is a CLM?
    • What is a GRC?
    • E-Signature Regulations
    • Blog
  • Contact
  • Schedule Demo
  • USA
  • LATAM
  • BRA
  • For People
  • What’s New
  • Home
  • Products
    • Legale CLM
    • Legale GRC
    • Legale Sign
    • Legale AI
    • Legale API
    • Legaliza
    • Digitization
  • Solutions
    • Legal
    • Human Resources
    • Occupational Risk Prevention
    • Sales
    • Finance
  • Resources
    • Governance
    • What is a CLM?
    • What is a GRC?
    • E-Signature Regulations
    • Blog
  • Contact
  • Schedule Demo
  • USA
  • LATAM
  • BRA
  • For People
  • What’s New
Schedule Demo
Menu
  • USA
    • LATAM
    • BRA

Blog

Blog > Conditional rules in Legale: signing workflows and notifications based on your data

Conditional rules in Legale: signing workflows and notifications based on your data

Legale conditional rules make a signing workflow or a notification adapt to each document’s data. Depending on how a form is answered or what a CSV file contains, the workflow can decide who signs and run or skip a step, and the notification can go to a different person or with different content.

Conditional rules in workflow steps

Each step in a workflow linked to a form can have rules that decide whether it runs and with what logic:

  • Data source: conditions use values from smart documents (smart templates) or CSV files.
  • Comparison: set manually or defined by the user, with operators such as equal, different, greater than or contains.
  • Result: depending on the evaluation, the workflow decides who must sign, whether the step runs or whether it’s skipped.

This lets you build automations where signer assignment and steps depend on data collected in electronic forms or defined in a CSV. For example, a contract could add an approval step only when the amount exceeds a value you define.

Conditional notifications

Forms also let you make notifications conditional: you compare a form variable with a value and chain more conditions to decide when each notification is sent and with what content.

  1. Open the form and go to Notification → Condition.
  2. In Variable, choose the field, for example {{RUT}}.
  3. In Logical condition, choose the operator, for example =.
  4. In Value to compare, type the value.
  5. Choose the data source: a field or a fixed value (Field or Fix).
  6. With Add condition (+) you add more rules and combine them.
  7. Set up the email, subject, suffix and message, and save.

Conditions are evaluated when the notification is sent, so the variables must match fields that exist in the form.

What you gain with conditional rules

  • Notifications with context: each alert responds to the document’s data.
  • Less manual work: the workflow routes itself, with fewer errors.
  • Reusable templates: the logic stays configured and is easy to maintain.

The “Filled” operator

To check whether a field has information, conditional fields in smart documents have the Filled operator. The condition is met when the referenced field has any value.

Conditions when sending data to an API

In CSV → Data to API automations you can also combine several conditions per field, choosing whether the value comes from a smart document or the CSV and joining them with AND, OR or NOT connectors. We explain it in Data to API in Legale.

Frequently asked questions

Where does the data the rules evaluate come from?

From smart documents and their forms, or from the CSV files you use in automations.

What can a conditional rule change?

Who signs, whether a workflow step runs or is skipped, and when and with what content a notification is sent.

Can I combine several conditions?

Yes. In notifications, with Add condition (+), and in Data to API, with the connectors between conditions.

What happens if the variable doesn’t exist in the form?

The condition is evaluated when the notification is sent, so check that each variable matches an existing field.

If you’d like to review how to automate your signing workflows with conditional rules, contact us.

E-signature

Menu
  • Global compatibility
  • Our E-signature
  • Advanced e-signature with PSC
  • Remote Advanced E-signature
  • E-signature Connection Engine
  • Countries we operate in

Notary connection

Menu
  • Online notary authorisation
  • Notaries connected by jurisdiction
  • Documents you can send to a notary
  • Evidence and records for every process
  • Legal framework: Law 19.799

Developers

Menu
  • Developer center
  • API documentation
  • Tutorials
  • Training course for developers

Support

Menu
  • Support
  • Get support

Research + Development

Menu
  • Discover our R&D project with CORFO

Terms

Menu
  • Terms and Conditions
  • Privacy policy
  • Cookies settings

Company

Menu
  • Work with us
  • Legal framework

Partners

Menu
  • Strategic alliances
  • Integrated solutions

Security

Menu
  • Ethical hacking and monitoring
  • Security policy
  • Personal data protection
  • Service level agreement (SLA)
  • ISO 27001
  • ISO 9001
  • SOC 2
  • Trust center
  • ISSA alliance

Contact Us

Our team would love to help you find the perfect fit of products and solutions.

  • sales@despapeliza.io
  • administracion@despapeliza.cl
Linkdin Youtube

All right reserved 2017 – 2024 © Despapeliza LLC. 7345 W Sand Lake RD STE 210, OFC 6837, Orlando, FL, EE. UU.