v3.7.15 – Workflow Data Integration, Localization Control & Identity Enhancements
Release Notes
v3.7.15 introduces deeper integration between Workflows and Data Gateway, enhanced localization control through glossary management, improved identity onboarding flexibility, and expanded developer tooling via CLI updates.
This release strengthens Blocks Cloud’s position as a unified platform by enabling event-driven data workflows, improving translation accuracy, and providing greater control over authentication and application scaffolding.
Workflow – Data Nodes
Workflows now integrate directly with Data Gateway through the introduction of data-aware nodes, enabling event-driven automation and seamless interaction with persistent storage.
This enhancement allows workflows to react to data changes in real time and perform operations directly on stored data—eliminating the need for intermediary services or custom backend logic.
New Nodes
Data Trigger Node
The Data Trigger Node enables workflows to be triggered automatically based on changes in Data Gateway collections.
- Listens to insert, update, and delete operations
- Configurable per specific collection
- Enables real-time, event-driven workflows based on data activity
This allows teams to build reactive systems such as audit pipelines, notifications, synchronization processes, and downstream data workflows triggered by changes in persistent storage.
Data Action Node
The Data Action Node allows workflows to directly perform operations on Data Gateway collections.
- Supports operations:
- Get
- Insert
- Update
- Delete
- Configurable per target collection
For schemas protected by access modifiers, the node can:
- Use client credentials configured in Blocks Cloud IAM
- Automatically authenticate using those credentials
- Execute operations securely without manual token handling
This enables secure, automated data manipulation within workflows while respecting existing access control policies.
Localization – Glossary
The Localization module now includes a Glossary system, providing precise control over how specific terms are handled during auto-translation.
Blocks Cloud’s auto-translation engine detects untranslated values and generates translations across enabled languages. However, certain terms—such as technical keywords, brand names, or domain-specific terminology—should not be translated or should follow specific rules.
The Glossary feature allows users to define and control these terms explicitly.
Glossary Scopes
-
Global Glossary
Applies to all localization keys across the application -
Module-Level Glossary
Applies to all keys within a specific module -
Key-Level Glossary
Applied manually to individual keys for fine-grained control
Users can define whether glossary terms:
- Should be excluded from translation
- Should be translated in a specific way
This ensures higher translation accuracy, consistency, and control across multilingual applications.
IDP – Configurable Sign-Up Flow
Blocks Cloud now provides greater flexibility in how users register and access applications through configurable sign-up flows.
Administrators can now:
- Enable or disable self-service user registration
- Define the allowed authentication methods for sign-up
Supported Sign-Up Methods
- Email and Password
- Single Sign-On (SSO) (requires prior configuration in Blocks Cloud)
When self-sign-up is enabled, users can register directly into the associated Construct application using the configured methods.
This enhancement allows organizations to align user onboarding with their security policies and identity strategies.
CLI
The Blocks CLI has been enhanced to support multiple frontend scaffolding options, improving flexibility for developers.
Previously, the CLI supported only the React-based Construct. With this update:
- Support for Blazor-based Construct has been added
- Users can now choose their preferred framework during project setup
This allows developers to align application scaffolding with their preferred technology stack, supporting both JavaScript and .NET ecosystems.