July 2026

July 3, 2026

Data Fabric operations now support composite entities

Data Fabric operations — read, create, update, upsert, and query — now work with composite entities. Previously, operations targeting composite entities failed silently or returned errors.

詳しくは、「Maestro での Data Fabric の操作」をご覧ください。

Bindings in Data Fabric expressions

In Maestro BPMN, Data Fabric expressions can now reference process bindings and variables dynamically for both the entity name and the folder path. Previously, the entity name and ?folderPath= segment in a datafabric[...] expression had to be literal strings.

Now they can be binding or variable references resolved at runtime against the workflow's variable store — for example, =datafabric[bindings.EntityName?folderPath=bindings.FolderKey][...].

詳しくは、「Maestro での Data Fabric の操作」をご覧ください。

ProcessType field in Agentic Orchestration DataPipe events

The Agentic Orchestration (AO) DataPipe event payload for process instances now includes a ProcessType field indicating whether the instance is a ProcessOrchestration or CaseManagement process. This lets downstream consumers of the DataPipe stream distinguish process kinds without additional lookups.

Subprocess signal propagation

In Maestro BPMN, cancel, pause, and resume signals sent to a parent process instance now propagate to any active embedded subprocess child workflows. When a parent is paused, the instance status transitions to "Paused" only after the nested subprocess confirms it has quiesced — matching the expected timing.

Resume propagation works symmetrically. Cancelling a parent while a subprocess is in-flight suppresses all downstream elements that would have run after the subprocess completed.

For more information, see Subprocesses and modularity.

GoTo within running subprocess

In Maestro BPMN, the GoTo operation now supports redirecting execution to an element inside a currently running subprocess. The operation routes the transition to the active child subprocess workflow when the source and target elements belong to the same subprocess scope. Transitions that cross subprocess boundaries remain unsupported.

tasksCompletedV2 in RetrieveCaseState

In Maestro Case, the RetrieveCaseState activity response now includes a tasksCompletedV2 field alongside the existing tasksCompleted field. Each entry in tasksCompletedV2 carries both an identifier and a name, using the same identifier format as entries in tasksRunning.

The original tasksCompleted list is unchanged for backward compatibility. tasksCompletedV2 is only populated when the V2 case-management schema is in use.

For more information, see Introduction to Maestro Case.

Instance migration includes subprocess-scoped variables

In Maestro BPMN, when migrating a running instance to a new package version, the variable diff endpoint now returns all InOut working variables — including subprocess-scoped variables and activity output variables — grouped by scope and kind.

Supplied values on the upgrade request overwrite existing carried values and are forwarded to running subprocesses so their isolated variable scopes are updated.

For more information, see Publishing and upgrading agentic processes.

バグ修正

• Fixed an issue where assets configured to resolve from a specific folder returned null instead of the expected value. Workflows that use folder-scoped asset references — for example, runtime.assets["Secret"]?folderId=123 — now retrieve the correct asset.
• Fixed an issue where the original licensing context was dropped when a faulted workflow instance was retried, causing the licensing service to treat the retry as a new transaction and potentially double-count consumption.

重大な変更

• The Document extraction element output variables have been renamed: =ExtractionResult is now =result and =Taxonomy is now =taxonomy. Workflows that reference the previous variable names require updates.