DataWorks provides a unified process with end-to-end capabilities for data development and data governance. You can also implement process controls at key nodes in the default DataWorks process to meet your business needs. This topic describes the process control features that DataWorks supports during data development.
Version limitations
This feature is available only in DataWorks Enterprise Edition and later editions.
Features
DataWorks workspaces are available in standard mode and basic mode. The development flow for tasks differs depending on the mode. The following diagrams illustrate the data development flow for each mode.
Development flow in a standard mode workspace
Development flow in a basic mode workspace
As shown in the preceding diagrams, you can implement process controls at key nodes in the general process, such as before a task is run, debugged, committed, or published.
Example of pre-run check | Example of pre-commit check | Example of pre-publish check |
|
|
|
You can use DataWorks features such as Open Platform and data governance to implement control checks at key nodes of the data development process.
Feature module | Pre-run check | Pre-commit check | Pre-publish check | Introduction to process control features |
Data governance center |
|
|
| The DataWorks data governance center has multiple built-in check items. You can enable check items as needed. After you enable a check item, the built-in check logic of DataWorks is triggered for the relevant operation to perform a control check. The subsequent process continues only after the control check is complete. |
Open Platform |
|
|
| If the built-in check items in DataWorks do not meet your process control requirements, you can use Open Platform. Open Platform lets you develop custom check programs for events that require control and embed the control process into the data development flow. |
The following sections use a standard mode workspace as an example to describe the process control features at these key nodes.
Enable built-in check items: Data governance center
The DataWorks Data Governance Center provides multiple built-in check items that you can enable as needed. When you enable a check item, DataWorks triggers its built-in check logic for the relevant operation. The process can continue only after this control check is complete.
Breakdown | Description |
Related DataWorks features | DataWorks data governance center The DataWorks data governance center has many built-in check items. After you enable them, you can perform control checks for the corresponding operations.
|
Configuration entry point and guidance | Enable check items in the data governance center and specify the workspace where they take effect. For general instructions, see Configure administration items. |
Customize check logic: Open Platform
If the built-in check items in DataWorks do not meet your process control requirements, you can use Open Platform. Open Platform lets you develop custom check programs for events that require control and embed the control process into the data development flow. The following information describes the control check capabilities of custom check logic before you debug and run a task.
Breakdown | Description |
Involved DataWorks feature module | DataWorks Open Platform DataWorks Open Platform provides OpenEvent, Extensions, and OpenAPI. You can use OpenEvent to subscribe to messages about user operations in Data Studio. After an event message is received, you can use Extensions to customize a check and approval program. Then, you can use an OpenAPI to send the approval result of the program back to the DataWorks system as a callback. For more information about OpenEvent and Extensions, see OpenEvent overview and Extensions overview. |
Check process | If you use Open Platform to configure event subscriptions and event checks for key operations in Data Studio, a check process is triggered when a user performs a corresponding operation. The following diagram shows the control check process for pre-run control. |
Configuration entry point and guidance | In Open Platform, configure subscriptions to Data Studio events. Then, develop an extension for event processing, publish the extension to DataWorks, and specify the workspace in which to enable it.
For more information about the event types that Open Platform supports for subscription-based control, see Extensions overview.
|
