After you register, publish, and enable an extension in a DataWorks workspace, DataWorks sends an event message to your extension when a corresponding extension point event is triggered. You can then view the result returned by the extension. This topic describes the extension point events that Operation Center supports and explains how to use them to trigger extension validation.
Prerequisites
Message subscription is enabled. For more information, see Enable message subscription.
The extension program is developed and deployed. For more information, see Develop and deploy an extension program: Function Compute.
Background information
DataWorks can notify you of extension point events by sending messages. You can also use extensions to control workflows. To do this, enable an extension for a specific extension point event. The extension then processes the event using your custom logic. To use these features, you must first register your extension in the DataWorks Management Console and then enable it in .
Only users with administrative permission for the workspace can enable extensions in .
For more information about extensions, see Extensions overview.
The figure shows a workspace-level extension. For more information, see List of supported extension point events.
Capabilities
The Operation Center module enables your local service to receive messages for the following extension point events. You can also register a local program as a DataWorks extension. The extension receives event messages and processes them using custom logic. It then uses the UpdateWorkbenchEventResult callback API to return the result to the platform. This lets you control workflows in DataWorks. Operation Center supports the following extension points:
Event name | Event details |
Node change event |
Note In this context, a node refers to a task in the Auto-triggered Task list in the Production Operation Center. |
Data backfill event |
|
In this context, a node refers to a task in the production Operation Center Auto Triggered Task list. Extension validation is triggered when you perform the listed operations on a task in the Auto Triggered Task interface of the production Operation Center. These operations do not trigger validation if they are performed on an auto triggered task in the Operation Center for the development environment. Similarly, freezing or restoring an instance from the instance interface does not trigger validation.
Supported extension points
Operation Center - Freeze and restore nodes
The following figure shows an example of the node freeze extension point.
Operation Center - Unpublish node
Operation Center - Data backfill
References
For more information about how to enable an extension, see Apply an extension.
For more information about other extension point events in Operation Center, see List of supported extension point events.
For information about the message entity format for data backfill events, see Data backfill event.
For information about the message entity format for node change events, see Node change events (add, modify, delete, freeze, restore, and unpublish).