You must configure a target project for the current project in the following cases.
Data development and data production are carried out respectively in different projects to achieve data isolation.
The data processing procedure developed in one project is synchronized to another project on schedule.
When a project is configured with a target project, the Release button appears on the development page. Click the button to enter the Release Management page.
On the Release Management page, you can select the tasks, resources, and functions that have been successfully submitted in the current project and release them to the specified target project.
The Release Management page appears only when a project is configured with a target project.
Only Task, Resource, and Function can be released from the development project to the production project.
The connection information such as table and data source configuration cannot be released. If tables or data sources are used in the task, the production project administrator is responsible for maintaining them in the target project.
Navigate to Project Management > Project Configuration. Select another project name as the Release Target.
Only the Project Administrator has a permission to configure the target project on the Project Configuration page. If you are not the project administrator, ask the holder of the main account to configure it.
After the target project is configured, the Release button appears in the toolbar of the Data Development page.
On the Data Development page, click Release to go to the Release Management page.
Click Create Release Package and then a list of submitted workflow tasks, node tasks, resources, and functions appears.
Only the tasks, resources, and functions that are successfully submitted but not in the release package can appear in the list to be released.
On the Create Release Package page, you can filter the objects according to the latest modifier, object type, modified date, and object name, and view object details such as the changes of internal nodes in the workflow.
Click Release or Package and Release as needed.
Two methods are provided to release the objects: release objects one by one directly and build a package of multiple objects and release.
Release objects one by one directly
After screening out the objects to be released based on the filter conditions, select an object and click Release to trigger the release process. Subsequent operations vary with user roles. For more information, see the following descriptions.
Build a package of multiple objects and release
After screening out the objects to be released based on the filter conditions, click Add after each object to add them to the release package.
Click Package and Release to build a release package and trigger the release process. Subsequent operations vary with user roles. For more information, see the following descriptions.
Release operations for different user roles
If you are a Project Administrator or maintainer, the release package is released directly after you click Package and Release.
If you are a deployer, then you have no permission to create a release package. You can only approve the release package created by the developer and click Release to release it.
If you are only a developer, the release package is added into the release package list with the status of For Release after you click Package and Release. Ask the project administrator, maintainer, or deployer to click Release on the Release Package List page.
Since two projects are involved in the release operation, if you are a developer in project A, and a maintainer in project B, you can release the projects simultaneously by selecting both of the projects and clicking Package and Release.
The Release Package List page displays the packages in four statuses: for release, in release, released successfully, and release failed.
You can filter the release packages by publisher, applicant, release date, application date, and release package status. You can also view, delete, and continue releasing the release package.
The objects of successfully released packages (such as contents and configurations) are copied from the current project to the target project. You can view the release results in the target project.