Offline Development Task Version Management

Last updated: 2026-06-03 18:11:03

Overview

Offline development tasks support draft and published versions. Save unfinished configurations as drafts, or publish confirmed configurations for scheduling. Historical versions help you trace changes, restore a stable configuration, and troubleshoot runs.

Version	Purpose	Restrictions
Draft	Preserves editing progress; can be edited and run manually.	Cannot be scheduled, triggered by URL, or migrated across environments.
Published	Preserves the confirmed configuration.	Can be scheduled, triggered by URL, or migrated across environments.

Business Value

This feature solves the problem where a later submission directly overwrites a previous change to the same task, making historical changes impossible to trace. By retaining draft versions and published versions, teams can track changes more clearly, quickly identify problematic versions, and restore a stable version when a new version becomes abnormal, thereby reducing recovery time and data contamination risk.

Applicable Scenarios

This feature is suitable for daily iteration of Offline Development Tasks, multi-user collaborative development, troubleshooting, historical change tracing, task migration, and post-release rollback scenarios. It is especially useful for tasks whose processing logic changes frequently and that require stable releases.

Prerequisites

Before using this feature, confirm that the following conditions are met:

1. The current account has permission to view and edit Offline Development Tasks.
2. When publishing a task, no node in the task has a configuration exception.
3. When referencing a Subprocess, only a Subprocess that already has a published version can be selected.

A configuration exception node refers to a node with missing required fields or a node whose current owner lacks permission for the related resources. When a task contains configuration exception nodes, the task can still be run, canceled, or saved as a draft, but it cannot be published.

Save and Publish Tasks

Open the Editor

On the Offline Development Task page, click Add workflow to create a new task, or click a target task in the task list to open the editing page.

Available Actions

The task editor provides the following version-related actions:

Button	Description
Run	Runs the current draft version or published version of the task.
Cancel	Exits the current editing page and returns to the task list.
Save as Draft	Saves the current task definition as a draft version.
Publish	Saves the current task definition as a published version and stays on the current page.
Publish and Exit	Saves the current task definition as a published version and returns to the task list.
Save, run and exit	Creates a published version, runs the task, and returns to the task list.
View Version History	Views task history and switches to a specified version.
Current Version	Displays the version state and version information of the current page.

Button Availability Rules

The available buttons differ depending on the editing state.

1. When there are no nodes on the canvas, only the Cancel button is available. All other buttons are disabled and display the message At least one node is required.
2. When nodes have been added to the canvas but some nodes still have configuration exceptions, the Run, Cancel, and Save as draft buttons are available. All publishing actions are disabled and display the message There are nodes with configuration exceptions.
3. When all nodes are fully configured, run, save, and publishing actions are all available.
4. When the task contains a Subprocess node, only Subprocess tasks that already have a published version can be selected. When the parent task is triggered by scheduling, the published version of the Subprocess is used.

Save as Draft

Save as draft is used to record the current editing progress without affecting the availability of the existing published version.

1. On the Offline Development Task Editing page, click the Save as draft button.

2. The system saves the current task definition and remains on the current page.

3. The latest draft version in version history is overwritten, and the draft save time is updated.

4. If the task has only a draft version and no published version yet, the task list displays the Only Draft Exists indicator.

   

5. If the task has only a draft version, scheduling cannot be configured. The Scheduling Switch and URL Trigger Switch are disabled and display the message Only published tasks support scheduling.

Tasks that only have draft versions can still be edited and run manually, but cannot be formally executed as scheduled tasks.

Publish

Publish is used to generate a formal version that can be scheduled, migrated, and reused reliably.

1. On the Offline Development Task Editing page, confirm that all nodes are fully configured.
2. Click the Publish button.
3. The system adds a published-version record and distinguishes different published versions by save time.
4. The page remains on the current editing page, and displays the newly generated version number.

Publish and Exit

Publish and Exit is used when you want to return to the task list immediately after finishing configuration.

1. On the Offline Development Task Editing page, click the Publish and Exit button.
2. The system adds a published-version record and distinguishes different published versions by save time.
3. The system returns to the Offline Development Task List page.

Publish, Run, and Exit

To run a task immediately after publishing, open the dropdown beside Publish and select Save, run and exit. This creates a published version, runs the task, and returns to the task list.

Run Tasks

This section explains how the system determines whether to use a draft version or a published version when an Offline Development Task is run manually, and how it prompts users to save changes if the task has been modified.

Entry Description

You can click the Run button on the Offline Development Task Editing page, or run a task directly from the Offline Development Task List page.

Run from the Editing Page

1. On the Offline Development Task Editing page, click the Run button.

2. If the task definition has not changed, the system runs it according to the current manual-run logic and indicates whether the latest version is a draft version or a published version.

   

3. If the task definition has changed, the system displays the prompt You need to save the task before running it. Do you want to save it?.

   

4. In the prompt dialog, select one of the following operations as needed:

Action	Description
Cancel	Closes the dialog and does not run the task.
Save as Draft and Run	Saves the current draft version and then runs it.
Publish and Run	Publishes the current version and then runs it.

5. If the task contains unconfigured items, the Publish and Run button is disabled and cannot be selected.

Run from the List Page

1. On the Offline Development Task List page, locate the target task and run it.
2. The system runs the latest version of the task.
3. During execution, the system indicates whether the current version being run is a draft version or a published version.

Scheduled tasks and URL-triggered tasks always use the latest published version. Manual runs from the list page always use the latest version of the task.

View and Restore Historical Versions

This section explains how to view the history of an Offline Development Task and how to switch to a specific historical version for continued editing.

Entry Description

On the Offline Development Task Editing page, click the Historical versions button.

View Version History

1. On the Offline Development Task Editing page, click the Historical versions button.
2. The system displays the task canvas of the latest version by default.
3. Select the historical version to view. This view shows only the node layout; node configurations cannot be edited here.

Switch to a Historical Version

1. In the version history list, select the target version.
2. After switching, return to the task canvas page.
3. The node configuration on the canvas is updated to the configuration of the selected historical version.
4. After confirming the configuration, continue editing or publish it again.

After switching to a historical version, the system loads that version into the current editing context, making it easy to continue modifying or republishing it.

Restore a Stable Version

If the latest modification causes a task to fail, produce abnormal results, or require quick restoration of stable logic, you can roll back by switching to a historical version and publishing it again.

1. On the Offline Development Task Editing page, click Historical versions.
2. Select the most recent stable and usable historical version.
3. Return to the canvas and confirm that the node structure matches expectations.
4. Click Publish or Publish and Exit to make that stable version the latest published version again.

Version Rules for Other Features

This section summarizes how the task list page and related features behave after version management is introduced, making it easier to understand which version state each operation uses by default.

Task List Page Operation Rules

The relationship between each capability and version state on the task list page is as follows:

Feature	Version Rule
Edit	After entering the editing page, version-management rules apply.
Run	Runs the latest version and indicates whether it is a draft version or a published version.
Rename	Does not modify any version.
View Resource Lineage	Uses the published version.
View Instances	Not affected by version management.
Transfer Ownership	Not affected by version management.
Save As	Uses the published version. The copied task is created as a draft version.
Move To	Not affected by version management.
Delete	Not affected by version management.
Cross-Environment Migration	Uses the published version. Tasks that only have a draft version cannot be migrated.
Admin Permission Transfer	Not affected by version management.
User Access to Task	Uses the latest version. Users can see version history, but cannot switch to a historical version.

Restrictions for Draft-Only Tasks

When a newly created task only has a draft version, the following capabilities are hidden:

1. Save As
2. Resource Lineage
3. User Authorization
4. Collaborator Authorization

Cross-Environment Migration Rules

This section explains how the system decides whether an Offline Development Task can be migrated across environments based on its version state, and what the migration result looks like after import.

Migration Rules

1. Offline Development Tasks that only have a draft version cannot be migrated.
2. Offline Development Tasks that have a published version can be migrated, and the migrated content is the latest published version.
3. If no Offline Development Task with the same ID exists in the target environment, the system creates a new task and saves the migrated content as a draft version.
4. If an Offline Development Task with the same ID already exists in the target environment:

Scenario	Result
The target task already has a draft version	Overwrites the draft version of the target task.
The target task does not have a draft version	Adds a new draft version.

The result of cross-environment migration always lands as a draft version in the target environment, making it easy to review and adjust the migrated task before publishing it there.

Management and Monitoring

This section describes newly added version-management-related capabilities in the Management Center and Task Monitor, helping administrators and operations personnel track version usage.

Management Center Configuration

The Management Center adds a historical version limit setting to control the maximum number of historical versions retained for a single Offline Development Task.

1. In the Management Center, open the configuration page related to Offline Development Tasks.
2. Find the Offline Development Historical Version Limit setting.
3. Set the retention count as needed. The valid range is 1 to 100.

Task Monitor

Task Monitor adds version information to the instance details page so that you can identify which task version is associated with the current instance.

1. On the Task Monitor page, open the details page of the target instance.
2. Check the newly added version information field to confirm the version state and version content used for that run.

Limitations and FAQ

Limitations

• A task must contain at least one node before it can be run, saved, or published.
• Configuration exceptions prevent publishing, publishing and exiting, and publishing and running.
• Only subprocess tasks with a published version can be selected.
• Scheduling and URL triggers use the latest published version.
• Tasks labeled Only Draft Exists cannot enable scheduling or URL triggers.
• Historical versions show node layouts only. They do not support viewing detailed node settings, editing node configurations, or entering a dataflow directly.
• Users with view access can view historical versions but cannot switch to one.

FAQ

• Why can I not publish a task after adding nodes? Check for missing required settings or resources the owner cannot access. Resolve the configuration exceptions before publishing; save a draft in the meantime.
• Why is publishing and running unavailable? Complete the missing node settings, then publish and run again.
• Why can I run a task manually but not enable scheduling? It has only a draft version. Publish it before enabling scheduling or URL triggers.
• Why are some tasks absent from cross-environment migration? Draft-only tasks cannot be migrated. Create a published version first.
• Why can I not edit a historical version directly? The history view supports viewing node layouts and switching versions, not editing node settings in that view.