Added

Approval and Process catalogs can filter company-wide and Legal Entity records within existing permissions. Operation requirements show their inherited source and group template setup guidance once per operation; Demand Planning conditions remain entity-specific.
Dashboard, report, signature-template, and personal Agent-task libraries use the same company-wide versus Legal Entity record filter without expanding the caller's authorized organization set.
Operation approval settings share scoped revision history across App and Process entry points, including App-owned conditional policy contexts. Template-owned lines and human line preparation keep formal approval on the existing Approval engine.
Process actions accept separately authorized resource targets and preserve their origin. Schema tasks support frozen initial values and server-enforced fixed fields. Supplied default procedures retain company revisions and expose readiness and upstream-version availability.

Upgrade required

Apply the tenant migrations for operation requirements, conditional contexts, template route ownership and Process template provenance. Adopt the bundled SDK 0.6.4 and coordinated App releases together. Only bindings with an implemented approval-free path may enable requirement settings.
Conditional-only and company-only requirement scopes preserve common-data rules. Durable operation idempotency is opt-in; apply the nullable-expiry migration before enabling it. Existing HTTP retry retention remains unchanged.
Approval preparation retains the actual child-operation subject without replacing the Process origin. Deprecated payload fields remain accepted for existing definitions and are omitted from new-authoring catalogs.
Core 0.6.8 locks PHP and React SDK 0.6.4 plus the coordinated App releases to their immutable tags.

Process and decision authoring preserves the originating list on cancel and returns to a compatible company-common or Legal Entity scope after saving, including DMN-to-BPMN round trips.