After you register, publish, and enable an extension in a DataWorks workspace, DataWorks sends an event message to your extension whenever a supported operation is triggered. Your extension applies custom validation logic and calls the UpdateWorkbenchEventResult callback API to return the result, which controls whether the operation proceeds. You can then view the result returned by the extension.
Prerequisites
Before you begin, ensure that you have:
Message subscription enabled. See Enable message subscription.
An extension program developed and deployed. See Develop and deploy an extension program: Function Compute.
How it works
Operation Center enables your local service to receive messages for supported extension point events. You can also register a local program as a DataWorks extension to control workflows — the extension receives event messages, processes them using custom logic, and calls the UpdateWorkbenchEventResult callback API to return the result to the platform.
After your extension program is deployed, register it in the DataWorks Management Console and enable it in Management Center > Extension.
Only users with administrative permission for the workspace can enable extensions in Management Center > Extension.
When a supported operation is triggered, DataWorks sends an event message to your extension program. The program processes the message using custom logic and calls the UpdateWorkbenchEventResult callback API to return the result. Based on the result, DataWorks either allows or blocks the operation.
Supported extension points
Operation Center supports three extension points. Each extension point fires only when the operation is performed on a task in the production Auto Triggered Task list. Operations in the development environment and instance-level operations do not trigger extension validation.
| Extension point | Triggered operations | Scope |
|---|---|---|
| Operation Center - Freeze and restore nodes | Pre-freeze node event; prerequisite event for node restoration | Production Auto Triggered Task list only. Freezing or restoring from the instance interface does not trigger validation. |
| Operation Center - Unpublish node | Pre-unpublish node event | Production Auto Triggered Task list only. |
| Operation Center - Data backfill | Backfill data for the current node of an auto-triggered task; backfill data for the current node and its descendant nodes; backfill data in massive nodes mode; backfill data in advanced mode | Production Auto Triggered Task list only. Data backfill in the development environment does not trigger validation. |
Operation Center - Freeze and restore nodes
Operation Center - Unpublish node
Operation Center - Data backfill
Message format reference
Each extension point sends a specific message format to your program. Refer to the following resources before implementing your validation logic:
Data backfill event — message format for data backfill events.
Node change events (add, modify, delete, freeze, restore, and unpublish) — message format for node change events.
What's next
To enable an extension, see Apply an extension.
For all extension point events supported by Operation Center, see List of supported extension point events.