Manage Offline Integration Tasks in Dataphin - Dataphin

The offline integration tasks list shows all the offline integration tasks that you created in Dataphin. This list displays basic information and management options for each task. You can use the list to view and manage your offline integration tasks. This topic describes the management features available in the offline integration tasks list.

Access the Offline Integration Tasks List

In the top menu bar on the Dataphin homepage, choose Develop > Data Integration.
On the Integration page, select Project in the top menu bar.
In the navigation pane on the left, choose Integration > Batch Pipeline. At the bottom of the Batch Pipeline list, click Offline Integration Tasks List to open the list tab.

About the Offline Integration Tasks List

The offline integration tasks list page has four main areas: the toolbar, the filter section, the offline integration tasks list, and the batch operations section. You can use this page to view and manage your offline integration tasks.

Area	Description
① Function Area	Search: Enter an integration task ID, name, or code in the text box to find a specific offline integration task. Use this when you know the task ID, name, or code. Filter: Select I Developed to filter tasks. Click Filter, then click More in the filter section to show all filter options. View Batch Operation Records: Click View Batch Operation Records to see records for batch operations such as Submit or Other Operations. Other operations include batch lock acquisition, batch unpublish, batch unpublish and delete, batch shift, batch change owner, batch scheduling configuration, batch dependency configuration, batch parameter configuration, batch run configuration, batch channel configuration, and batch modify ownership directory. Create Offline Integration Task: Click Create Offline Integration Task to create a new offline pipeline task or offline script task. Offline Pipeline: An offline pipeline is a script that processes one or more offline integration tasks. It synchronizes data from one or more source data sources (single tables or multiple tables) to one or more target data sources. For details, see Create an Integration Task Using a Single Pipeline. Script Task: Write a JSON script to develop data synchronization. This gives you more flexibility and fine-grained control over configuration. For details, see Create an Integration Task Using Script Mode. Configure Displayed Columns: Choose which columns appear in the offline integration tasks list. Available columns include the following: Basic Information: Task name/ID, task mode, source information, target information, task status, latest submission status, current locker, development owner, and O&M owner. Configuration Information: Scheduling type, scheduling cycle, dependencies, and parameters. Other Information: Creation time, latest modifier, and actions. Note You cannot hide Task Name/ID or Actions. Refresh: Click to refresh the offline integration tasks list.
② Filter Section	Click Filter to expand the filter section. Click More to show all filter options. Available filters include the following: Task Mode: Filter by task mode. Options are Offline Pipeline and Offline Script. Task Status: Filter by development status. Options are Draft, Developing, Submitted, and Submitting. Schedule Type: Filter by scheduling type. Options are Normal, Dry-Run, Paused, and One-Time Task. For more information, see Scheduling Types. Recurrence: Filter by scheduling cycle. Options are Minute, Hour, Day, Week, and Month. Development Owner: Filter by development owner. Operation Owner: Filter by O&M owner. You can select I Manage or choose a specific O&M owner. Latest Submission Status: Filter by the status of the most recent submission. Options are Submitting, Submission Failed, Submission Alert, and Submission Successful. Published: Filter by whether the task is published. Source Data Source/Project/Data Domain: Filter by source data source, project, or data domain. The source data sources include all those listed in the integration tasks list. Source Table/Topic/Index: Filter by source table name, topic, or index. Note Select a source data source, project, or data domain before using this filter. Target Data Source/Project/Data Domain: Filter by target data source, project, or data domain. The target data sources include all those listed in the integration tasks list. Target Table/Topic/Index: Filter by target table name, topic, or index. Note Select a target data source, project, or data domain before using this filter. Created At: Filter by creation time. Options are Last 3 Days, Last 7 Days, Last 30 Days, or a custom time range. Last Modified At: Filter by last modification time. Options are Last 3 Days, Last 7 Days, Last 30 Days, or a custom time range. Conditional Scheduling: Filter by whether conditional scheduling is enabled or disabled. Tag: Filter by one or more task tag values. To clear all filters and restore defaults, click Reset.
③ Offline Integration Tasks List	This list shows information about your offline integration tasks and the actions you can take. The columns shown depend on your display settings. For supported actions, see Actions Supported in the Offline Integration Tasks List.
④ Batch Operations Section	Use the batch operations section to process multiple offline integration tasks at once. This saves time and improves efficiency. For supported batch operations, see Batch Operations Supported for Offline Integration Tasks.

Actions Supported in the Offline Integration Tasks List

The following actions are available in the action bar:

Action	Description
Open Task	Open the current offline integration task in the editor.
Acquire Lock	Acquire and lock the edit lock for the current offline integration task. Note You cannot release locks from this list. Release locks in the editor instead.
Locate in Directory	Find the current offline integration task in the directory tree on the left.
Change Development Owner	Change the development owner of the current offline integration task.
Publish	Go to the Publish Center to publish the current offline integration task. For details, see Manage Published Tasks.
O&M	Go to the Operation Center to manage the current offline integration task. For details, see Operation Center. Note This action is only available for published offline integration tasks.
Unpublish	You can unpublish an offline integration task. Note This action is not available if the task has downstream tasks in another tenant. This action does not work if the task has downstream dependent nodes. After successful unpublish, go to the Pending Publish list to publish the object to the production environment.
Delete	Delete an unpublished offline integration task. Note If your tenant does not have Development Platform Settings > Unpublish and Delete > Allow Deletion of Published Objects in Development Environment enabled, then in Dev-Prod projects, you cannot delete draft objects if matching production objects exist.
Unpublish and Delete	You can unpublish or delete published offline integration tasks. Note This action does not work if the task has downstream dependent nodes. For tasks published to production, only unpublish runs—not delete. After successful unpublish and delete, go to the Pending Publish list to publish the object to the production environment. If your tenant does not have Development Platform Settings > Unpublish and Delete > Allow Deletion of Published Objects in Development Environment enabled, then in Dev-Prod projects, you cannot unpublish and delete online development objects.
Change Project Ownership	Change the project that owns the current offline integration task. In the Directory Tree on the left, click the icon next to the target offline integration task. Then choose Change Project Ownership. After clicking Change Ownership Directory, select a Target Project, a Directory, and enter a Task Name. Target Project: Choose a project where you have development permissions, and that matches the current project’s mode (both Basic or both Dev-Prod) and engine type. Search by project name keyword. Directory: Choose a directory in the offline integration tasks directory tree of the target project. Default is `/` (root directory). Task Name: The task name after migration. Default is the current task name. If a task with the same name exists in the target project, change the name. After changing project ownership: The task ID, code, and upstream/downstream dependencies stay the same. The output table (if any) moves to the new project. Downstream tasks that reference this table also update. You must submit and publish the task in the target project. Historical versions remain in the original project. You cannot roll back to versions from before the migration. If batch project ownership changes fail, check the failure logs in the batch operation records.

Batch Operations Supported for Offline Integration Tasks

Action	Description
Lock	Acquire edit locks for multiple offline integration tasks at once.
Submit	Submit multiple offline integration tasks at once.
Unpublish	Unpublish multiple offline integration tasks at once. Note This action is not available if any task has downstream tasks in another tenant. This action does not work if any task has downstream dependent nodes. After successful unpublish, go to the Pending Publish list to publish the object to the production environment.
Batch Modify Tags	Add or replace tags for multiple offline integration tasks. Select multiple tasks in the offline integration tasks list. Or select the checkbox before Select All at the bottom of the page. Click the icon at the bottom of the page. Then choose Batch Modify Tags. In the Batch Modify Tags dialog box, choose a Modification Type and a Tag. If you choose Replace, the system clears existing tags and applies only the selected ones. If you choose Append, the system keeps existing tags and adds the selected ones. Click OK to complete the change.
Unpublish and Delete	Unpublish and delete multiple offline integration tasks at once. Note This action does not work if any task has downstream dependent nodes. For tasks published to production, only unpublish runs—not delete. After successful unpublish and delete, go to the Pending Publish list to publish the object to the production environment. If your tenant does not have Development Platform Settings > Unpublish and Delete > Allow Deletion of Published Objects in Development Environment enabled, then in Dev-Prod projects, you cannot unpublish and delete online development objects.
Shift	Move multiple offline integration tasks to another code directory at once.
Change Development Owner	You can change the owners of multiple offline integration tasks to other developers in bulk.
Scheduling Configuration	Important Batch scheduling configuration only applies to auto triggered tasks. After batch configuration, the original scheduling attributes of selected tasks are overwritten. Use with caution. If selected auto triggered tasks have conditional scheduling enabled, setting them to dry-run or paused will disable conditional scheduling. Modify scheduling configurations for multiple offline integration tasks at once. You can configure basic scheduling or conditional scheduling separately. Batch Modify Basic Scheduling: After enabling batch basic scheduling, you can update the Configuration Method, Scheduling Type, and Scheduling Cycle for selected tasks. For details, see Configure Scheduling for Offline Pipelines. Batch Modify Conditional Scheduling: Disabled by default. After enabling, you can update the Configuration Method and Scheduling Condition for selected tasks. For details, see Conditional Scheduling. Note Conditional scheduling only works for tasks with Normal scheduling. When you choose Custom as the configuration method, you cannot use cross-node parameters as conditions. The Start Time parameter only works for tasks with daily, weekly, or monthly scheduling cycles.
Dependency Configuration	Configure dependencies for multiple offline integration tasks at once. To add multiple upstream dependencies, click + Add Dependency. The list shows only manually added upstream dependencies that are common to all selected tasks (same dependency object and same dependency settings). Adding, deleting, or editing dependencies applies to all selected tasks.
Parameter Configuration	Configure parameters for multiple offline integration tasks at once. To add multiple parameters, click + Add Parameter. The available parameters are the union of local variables across all selected tasks. The system overwrites the value of each parameter for all selected tasks. For example, if you set `paramA=valueA`, and taskA does not have paramA, the system skips taskA. If taskA has paramA, the system sets paramA to valueA in taskA. You cannot batch set space name variables or global variables.
Run Configuration	Configure run settings for multiple offline integration tasks at once. Important After batch configuration, the original run settings of selected tasks are overwritten. Use with caution.
Channel Configuration	Configure channels for multiple offline integration tasks at once.
Change Project Ownership	Change the project ownership for multiple offline integration tasks at once. Select multiple tasks in the offline integration tasks list. Or select the checkbox before Select All at the bottom of the page. Click the icon at the bottom of the page. Then choose Change Project Ownership. In the Change Project Ownership dialog box, select a Target Project and a Directory. Target Project: Choose a project where you have development permissions, and that matches the current project’s mode (both Basic or both Dev-Prod) and engine type. Search by project name keyword. Directory: Choose a directory in the offline integration tasks directory tree of the target project. Default is `/` (root directory). Click OK to complete the change. After changing project ownership: The task ID, code, and upstream/downstream dependencies stay the same. The output table (if any) moves to the new project. Downstream tasks that reference this table also update. You must submit and publish the task in the target project. Historical versions remain in the original project. You cannot roll back to versions from before the migration. If batch project ownership changes fail, check the failure logs in the batch operation records.