What's new in Blocks

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.

---

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.

---

Release Notes

v3.7.14 introduces enhancements across Localization, Data Gateway, Workflows, and Construct, focusing on improved visibility, flexibility, and developer productivity. This release brings deeper insight into localization changes, expands data manipulation capabilities, and strengthens workflow transparency and security.

---

Localization – Enhanced Visibility & Translation Control

Localization continues to evolve with improved tracking, auditing, and translation accuracy. These updates provide greater transparency into how content changes over time and how translations are managed.

• Search Individual Fields — Search localization keys and values independently for faster discovery and management.
• Publish Time per Key — Each key now maintains its own publish timeline. View detailed history directly from the key view page.
• Expanded Publish History — From the main localization history tab, you can now:
  • View all keys included in each publish
  • Inspect previous states of updated keys
  • See total key counts per publish
• Migration History Tracking — Track all keys migrated between environments, including timestamps and detailed records in the receiving environment’s history.
• Glossary Support — Define glossary terms to exclude specific words (e.g., technical terms or proper nouns) from auto-translation, improving consistency and accuracy.

These enhancements make localization workflows more transparent, auditable, and reliable at scale.

---

Construct – Expanded Frontend Options

Construct now supports a broader range of development stacks, enabling teams to build applications using their preferred technologies.

• Blazor-Based Construct Support — In addition to the existing React-based Construct, a new Blazor-based front-end option is now available for .NET developers.
• Developers can now choose their preferred scaffolding (React or Blazor) directly via the CLI.

This update increases flexibility and expands Construct’s reach across different development ecosystems.

---

Data Gateway – Expanded Data Control & Developer Productivity

Data Gateway continues to evolve with new capabilities that improve usability, performance, and control over data operations.

• Child Object Access & Validation — Child objects now support independent access modifiers and validation rules, ensuring that reused objects remain isolated and do not inherit unintended configurations.
• Keyboard Shortcuts in Playground — Improved navigation and usability with new keyboard shortcuts for faster interaction.
• Bulk Operations — Efficiently manage large datasets with support for:
  • Insert many
  • Update many
  • Delete many
• “Use in Editor” from Introspection — Insert queries and mutations directly into the playground from the introspection view using the “Use in Editor” action.
• Where Clause Support — Queries now support a where clause with operators such as eq,gt,lt, enabling more flexible and precise filtering.
• Schema Import & Export — Move schema structures across projects with support for:
  • Access modifiers
  • Column-level validators
  • Cross-project portability

These updates make Data Gateway more powerful, flexible, and efficient for real-world data workflows.

---

Workflow – Improved Visibility & Security

Workflow enhancements focus on improving observability and securing execution paths.

• Input/Output Visualization — View the flow of data between nodes, making it easier to debug and understand workflow behavior.
• Webhook Validation — Webhook triggers now support authentication, ensuring only authorized requests can trigger workflows.

These improvements provide better control, transparency, and reliability for workflow automation.

---

Release Notes

v3.7.10 introduces smarter automation with enhanced workflow nodes, improved visibility into inbound and outbound email activity, and the launch of SELISE AI for building flexible, tool-enabled chat experiences. This release also adds a document management system to Storage and includes UI refinements to improve overall usability and operational clarity.

---

Workflows – New and Enhanced Nodes

The Workflows service has been expanded with new capabilities to enable more flexible and event-driven automation.

New Nodes

• Email Trigger Node Automatically trigger workflows when an email is received, allowing teams to build email-driven automations and integrations.
• HTTP Node The existing HTTP node now supports full configuration of:
  • Request headers
  • Query parameters
  • Request body

This enhancement enables richer integrations with external APIs and greater control over HTTP-based workflows. These updates make workflows more powerful, extensible, and better suited for real-world automation scenarios.

Email Service – Inbound & Outbound Visibility

Blocks Cloud’s Email Service now supports visibility into both inbound and outbound emails, giving teams a complete view of email activity directly from the platform.

Inbound emails can be enabled by configuring an incoming mail server (IMAP). Once configured, Blocks Cloud will receive and display incoming messages associated with your service.

Benefits

• Unified email observability — monitor inbound and outbound emails from a single interface.
• Easier debugging — quickly verify whether emails were received or sent successfully.
• Improved reliability — detect misconfigurations or delivery issues early.
• Better operational insight — understand email traffic patterns and system behavior.

This enhancement makes email workflows more transparent and easier to manage in production environments.

SELISE AI

Blocks Cloud introduces SELISE AI, a secure and customizable chat-based AI experience—designed for teams and enterprises that want full control over how AI is built and used.

Key Highlights

• Chat-based AI assistant A conversational agent with a familiar ChatGPT-style interface.
• Built with Construct Developed using Blocks Cloud Construct, enabling seamless integration with platform services.
• User profile and preferences View your profile, change language settings, and personalize your experience.
• Chat history Access and continue previous conversations with full context.
• Tool integration Extend the assistant’s capabilities by adding tools from Blocks Cloud, allowing the AI to interact with APIs and services.
• Model flexibility Choose from a variety of available LLMs. You are not locked into a single model or vendor.
• Try it now Visit selise.ai to experience SELISE AI.

SELISE AI empowers teams to build, extend, and operate AI assistants that fit their workflows—without sacrificing flexibility, security, or control.

Deployment

If your domain is not verified then the message that was previously shown in the Overview page of your environment, will now be shown in the modal of the Configure button in the same page.

Storage — Now with a Document Management System (DMS)

Blocks Cloud Storage now includes a built-in Document Management System (DMS), providing a structured and centralized way to manage files across the platform.

• Service-based organization All files uploaded to Blocks Cloud are automatically organized into their respective service folders. For example:
  • Knowledge base files appear under the AI service.
  • Language files appear under the Localization service.
• Preconfigured service folders A dedicated folder is automatically created for each Blocks Cloud service to ensure consistent organization.
• Default view The default folder displays all files and folders for quick access and easy navigation.
• Storage providers
  • Azure is the default storage provider.
  • Additional providers can be configured as needed.
• File preview Preview supported file types directly within the platform.
• Bulk uploads Upload multiple files at once to save time and streamline workflows.

This update brings better structure, visibility, and usability to file management across Blocks Cloud services.

Release Notes

v3.7.9 continues to evolve Blocks Cloud into a modern, extensible platform for building, securing, and operating intelligent systems. This release introduces visual Workflows for automation, Roles and Permissions for fine-grained access control, and meaningful upgrades across AI, localization, and platform APIs.

Together, these enhancements bring greater control, transparency, and composability—allowing teams to automate processes, govern access across data and applications, and gain deeper insight into AI behavior, all while staying aligned with current industry standards for platform engineering and AI operations.

---

Roles and Permissions

Blocks Cloud introduces Roles and Permissions to give teams fine-grained control over access across data, APIs, and user interfaces. This capability aligns with modern security and governance standards, ensuring the right users have the right access—no more, no less.

Access Control Areas

Roles and permissions can be applied across three key aspects of the platform:

1. Data Connect
   • Control access to data using row-level and schema level permissions.
   • Ensure sensitive data is visible only to authorized roles.
2. Endpoints
   • Define who can access and invoke specific API endpoints.
   • Enforce consistent authorization rules across services.
3. Front-End
   • Control access to front-end pages and resources.
   • Tailor UI visibility based on user roles.

Benefits

• Stronger security through least-privilege access control.
• Centralized governance across data, APIs, and UI.
• Cleaner separation of responsibilities for teams and collaborators.
• Scalable access management as applications and organizations grow.

Workflows

Blocks Cloud now introduces Workflows, enabling teams to orchestrate automation and integrations through a visual, node-based experience—similar to modern workflow tools used across the industry.

Nodes Available

Workflows are built by connecting reusable nodes that can be arranged in any configuration:

• HTTP — Send HTTP requests to external services or APIs.
• Webhook — Receive incoming HTTP calls with user-defined input and output schemas.
• Email — Send emails as part of automated flows.
• AI — Invoke any agent configured in Blocks Cloud directly within a workflow.

Key Capabilities

• Flexible, visual node-based composition for building automation flows.
• Support for custom input and output definitions, enabling predictable integrations.
• Combine AI, external APIs, and notifications in a single workflow.

Benefits

• Faster automation without writing glue code.
• Seamless AI integration—use agent as first-class workflow components.
• Greater flexibility to connect services, react to events, and automate processes.
• Extensible foundation for future workflow nodes and integrations.

AI

The assistant now provides live feedback after a prompt is submitted, indicating the current stage of processing so users know the request is actively being handled.

• The assistant now provides live feedback after a prompt is submitted, indicating the current stage of processing so users know the request is actively being handled.
• Ask AI in Tracing and Logs also has real-time responses
• Improvements in AI conversation history
  • See workflow steps
  • See duration in each step
  • See the tools that were used, if any, along with the input and output parameters
  • See the used retrieval calls, if any, along with the chunks
• The Tools sections input and output parameters has been improved and supports nested objects
• The output parameters can be reduced based on output parameter limits. This helps reduce token calls
• Tools dashboard tab is now active. See useful information like:
  • Total Requests
  • Success Rate
  • Success Requests
  • Failed Requests
• Configuration improvements

Microservices endpoint changes

Some microservice endpoints have been updated in this release. The previous endpoints will remain supported for a limited period to ensure backward compatibility.

We recommend updating your integrations to use the new endpoints as soon as possible, as the legacy endpoints will be deprecated and removed after the announced deprecation window.

Localization Service Webhook

Get notified every time the auto-translation is complete. Use the following endpoint to set up your webhooks.

curl --location 'https://api.seliseblocks.com/uilm/v1/Config/SaveWebHook' \
--header 'Authorization: Bearer <your-token>' \
--header 'Content-Type: application/json' \
--data '{
  "itemId": "<uuid>",
  "createDate": "<iso_8601_timestamp>",
  "lastUpdateDate": "<iso_8601_timestamp>",
  "url": "<webhook_url>",
  "contentType": "application/json",
  "blocksWebhookSecret": {
    "secret": "<webhook_secret>",
    "headerKey": "<signature_header_name>"
  },
  "isDisabled": false,
  "projectKey": "<project-key>"
}'

Bug Fixes

• Fixed key duplication when migrating language keys form one environment to another
• Fixed only keys are IDs were being exported when exporting to Excel format