Skip to main content

v3.7.16 – Localization Visibility & Workflow Logic Enhancements

cloudMay 4, 2026

Release Notes​

v3.7.16 introduces enhancements across Localization and Workflow automation, improving translation visibility, glossary management, and conditional workflow execution. This release focuses on providing teams with greater control over multilingual content and enabling more intelligent, data-driven automation flows through advanced workflow logic.

Localization​

Localization workflows now provide deeper visibility into translation status, glossary application, and event-driven integrations. These updates improve translation governance, operational awareness, and overall localization accuracy.

  • Webhook Configuration from UI — Localization webhooks can now be configured directly from Blocks Cloud without requiring API calls. Previously, webhook setup was only available through the Save Webhook API.
    • Current webhook support includes notifications for completed auto-translation jobs.
    • This enables easier integration with external systems and translation pipelines.
  • Missing Translation Filter — A new filter allows users to quickly identify localization keys with incomplete translations.
    • For example, if a key contains English and German values but is missing an Arabic translation, the key will appear when this filter is enabled.
    • This improves translation completeness tracking and quality assurance processes.
  • Glossary Type Tagging on Keys — Keys now visibly indicate which glossary scopes are applied to them.
    • Keys affected by a global glossary display a global glossary tag.
    • Keys within modules using a module-level glossary display a module glossary tag.
    • This provides better visibility into translation behavior and glossary inheritance.

These enhancements make localization management more transparent, auditable, and easier to maintain at scale.

Workflow​

If Node – Conditional Logic for Dynamic Workflows​

The If Node introduces conditional branching capabilities within workflows, enabling automation flows to make decisions dynamically based on incoming data.

This allows workflows to evaluate runtime conditions, route execution paths intelligently, and build more advanced event-driven automation scenarios.

Key Capabilities​

  • Data-Driven Condition Evaluation
    Conditions can reference outputs from previous workflow nodes using the platform’s data binding syntax.

  • Support for Multiple Data Types
    Conditions can be evaluated against:

    • String
    • Number
    • Array
    • Boolean
    • Date & Time

  • Flexible Conditional Operators
    Depending on the selected data type, users can apply operators such as:

    • Equal / Not Equal
    • Contains / Not Contains
    • In Array / Not In Array
    • Greater Than / Less Than

  • Dynamic Comparison Values
    Users can define custom comparison values directly within the condition configuration.

  • Multiple Conditions with Logical Operators
    Workflows can combine multiple conditions using:

    • AND logic (all conditions must match)
    • OR logic (any condition can match)

  • Input & Output Visualization
    Like other workflow nodes, the If Node provides full visibility into:

    • Incoming payloads via the Input panel
    • Evaluated outputs via the Output panel

This improves debugging, observability, and workflow validation during execution.