DataWorks introduces an upgraded data development mode with a three-level structure (workspace > solution > workflow) that replaces traditional directory-based organization.
Background
DataWorks has upgraded its data development mode. This upgrade helps you organize nodes by business category, improve development based on business units, and connect multiple workflows.
DataWorks redefines the development process with a three-level structure of to enhance your development experience:
-
Workspace: A workspace is the basic unit for organizing permissions. It controls your access to development and O&M features. Workspace members can collaboratively develop and manage all code within the workspace.
-
Solution: You can combine one or more workflows into a custom solution. Solutions offer the following benefits:
-
They contain multiple workflows.
-
The same workflow can be reused across different solutions.
-
They provide a focused, immersive development environment.
-
-
Workflow: A workflow is an abstract representation of a business process. Workflows allow you to organize data development from a business perspective. A workflow can be reused by multiple solutions.
Workflows offer the following benefits:
-
They help you organize code from a business perspective for better clarity and structure it by task type. You can create multi-level subfolders under each node type. To do this, right-click a node type and select Create Folder. We recommend using no more than four levels of subfolders.
-
They allow you to view and optimize the entire business process from a business perspective.
-
Each workflow has a dedicated board to make development more efficient.
-
They allow you to deploy and perform O&M on nodes for an entire workflow.
-
A workflow can be reused across multiple solutions. You can focus on developing your own solution. This enables collaborative development, as other users can edit a referenced workflow directly from their own solutions.
The node state machine model defines the six states of a data node throughout its lifecycle. The following figure shows the state transition logic.
Enable the solution feature
-
Go to the DataStudio page.
Log on to the DataWorks console. In the target region, click in the left-side navigation pane. Select a workspace from the drop-down list and click Go to Data Development.
-
Enable the solution feature.
-
At the bottom of the left-side navigation pane, click the
icon. -
On the Personal Settings tab of the Configure page, select Show Solution.
-
Create a solution
-
Go to the DataStudio page.
Log on to the DataWorks console. In the target region, click in the left-side navigation pane. Select a workspace from the drop-down list and click Go to Data Development.
-
Click and configure the parameters in the dialog box that opens.
Parameter
Description
Solution Name
The name of the solution. The name cannot exceed 128 characters.
Description
The description of the solution. The description cannot exceed 256 characters.
Workflows
You can select multiple workflows to include in the solution.
-
After creating the solution, click Solution to expand the list and perform the following operations:
-
Double-click a solution to view all its workflows. Click a workflow name to view and edit it. For more information, see Create a workflow.
-
Right-click the solution name and select Solution Board to view the nodes of the selected workflows and modify the solution.
-
-
Deploy and manage the solution.
Hover over the solution name to display the
and 
icons:-
Click the
icon to open the Create Deploy Task page. You can view the nodes in the Nodes to Deploy status under the current solution.For more information about deploying nodes, see Deploy nodes.
Note-
Deploying a solution bundles multiple workflows for a single deployment operation.
-
A reused workflow will not be redeployed if it has no nodes pending deployment in the current solution.
-
You cannot specify the execution order of workflows within a solution. You must configure scheduling rules in the nodes. The scheduled time of each instance determines its execution order.
-
-
Click the
icon to go to the page. By default, this page displays the cycle instances for all nodes in the current solution.
-