1. Resource reuse scenario:
Standardized scenario tasks are packaged as resources and provided to IT personnel, who can import them for immediate use without reconfiguring dependent resources.
2. Test-to-production deployment scenario:
When users deploy two projects, they need to batch import developed tasks from the test environment project to the production environment project.
After you enter the FineDataLink project, click the dropdown button next to your user account to select either Resource Export or Resource Import, as shown in the following figure.
1. This function is not supported in cluster environments.
2. Resource Import and Resource Export are visible and configurable by all data developers. All resources for which a user has management permissions within the current project can be viewed.
3. Importing a large number of scheduled tasks may cause performance issues (for example, importing 400+ scheduled tasks may take approximately 8 minutes).
4. Cross-version import and export are supported.
1. Log in to FineDataLink, click the dropdown button next to your user account to choose Resource Export, and then click Select Resource, as shown in the following figure.
For details about the “Export Dependent Configuration” button, refer to the table in Step 2 of this section (it is recommended to select it; otherwise, using the resource may cause issues).
2. Select the scheduled tasks/scheduling plans to export and proceed with the export, as shown in the following figure.
Steps and page for exporting scheduled tasks:
Steps and page for exporting scheduling plans:
The following table describes each setting item.
1. When selected, subtask B called by scheduled task A will also be exported; if subtask B calls subtask C, C will also be exported, and so on.
2. If you do not have management permissions for a subtask, that subtask will not be exported.
3. Before exporting, the associated resources of scheduled tasks will be validated. For example, scheduled task A calls scheduled task aa, and scheduled task B calls scheduled task bb. Data development user Alice has management permissions for tasks A, B, and aa. When exporting resources A and B, a prompt will indicate whether the associated resources are complete or missing.
You can delete the scheduled tasks that are prompted as missing. If you still proceed with the export, a warning will indicate that it may cause abnormal usage of the exported resources, and the exported resource package will not include subtasks for which you lack permissions.
1. When selected, all scheduled tasks under the scheduling plan will be exported. If a scheduled task has subtasks, they will also be exported. If subtasks have their own subtasks, those will be exported as well, and so on.
3. Before exporting, the associated resources of the scheduling plan will be validated. If the user lacks management permissions for a scheduled task, that task will not appear in the left-side list, as shown in the following figure.
A prompt will appear in the O&M Center tab page, as shown in the following figure.
You can delete the schedules indicated as missing or obtain management permissions for the scheduled tasks. If you still proceed with the export, a warning will be displayed indicating that there are missing associated resources, which may cause abnormal usage when using the exported resources.
1. When selected, the scheduling calendar of the schedule plan will be exported. Scheduling calendars associated with subtasks will not be exported.
2. If the scheduling plan is enabled or disabled before export, its status will remain unchanged after export.
1. The resource directory path is exported by default, including all parent directories from the root down to the entity resources. Example: (Root directory) Folder A/Folder B/Task A
2. The exported content of scheduled tasks will be the latest version from the production environment. If there is no production environment, the development environment configuration will be used.
3. Only scheduled tasks for which the current user has management permissions in the current project can be exported. Empty folders will be filtered out.
When exporting scheduling plans:
For versions prior to 4.2.5.1, you can choose to export Timed Scheduling or Event Scheduling.
For version 4.2.5.1 and later, Event Scheduling export is not supported; only Timed Scheduling can be exported.
3. After the resources are exported, a ZIP package is downloaded automatically, as shown in the following figure.
1. Log in to FineDataLink, click the dropdown button next to your user account to choose Resource Import, as shown in the following figure.
2. Select the compressed package to be imported (only one compressed package can be selected for import at a time).
The following page is for importing Scheduled Task and Scheduling Plan.
1. During the import process, if conflicting objects are detected, you can choose an import method: Add Import or Overwrite Import.
Overwrite Import: If the user has permission to manage the entity resource, the current entity resource will be overwritten. If any scheduled task being overwritten contains a subtask for which the user lacks management permission, overwrite import is not allowed.
After clicking the One-Click Processing button, the import method can be configured uniformly. For Add Import, you can customize the imported scheduled task name. The task name cannot be empty or duplicated.
2. If the version gap is too large and the resource structures are incompatible, an error will occur indicating that the imported resource version is not supported. If the imported resources use features that do not exist in the target environment, an error will occur, indicating that unsupported features exist in the current environment.
3. If no conflicts are detected, the process proceeds directly to the next step.
1. The matching method can be Match Path or Specify Path:
Match Path: Match the folder path in this environment first. A folder will be created if there is no such path. This method is available only when the user has permission to create directories at the root level. If the target folder does not exist, it will be created automatically. If a folder with the same name already exists, it will be overwritten by default.
Specify Path: A folder will be created in the specified path. The selectable directory must be at a folder level that supports creating new tasks. During import, new folders and files will be created under the specified location.
If a sibling folder with the same name already exists, the imported folder name will be suffixed with "-Copy".
2. Dependent resources and associated resources validation:
If you still choose to import, the scheduling plan will indicate missing tasks after import.
A function exists in both the old and new environments, but the configurable values differ.
Example:
1. Scheduled Task - File Input: The file path in the original project does not exist in the new project.
2. Scheduled Task: The scheduled task does not include a dependent data connection, and no data connection with the same name can be matched in the new project.
The frontend retains the original configuration values after importing tasks:
1. If you manually reselect, the frontend will display a validation error.
2. If you make no manual changes, the backend will report an error when running the task.
A function exists in the old environment but does not exist in the new environment.
1. The original project's scheduled task includes a plugin node, but the plugin is not installed in the new project.
2. The original project's scheduled task uses an advanced operator, but the function is not registered in the new project.
A resource package contains resources without a corresponding functional entry point.
Example: User A imports a resource package containing scheduled task resources, but User A lacks the data development functional entry point in the new project.
Resources that are not compatible with the FineDataLink environment or lack the functional points specified in the LIC file.
Example: Scheduling Plan - Advanced Functional Points.
滑鼠選中內容，快速回饋問題
滑鼠選中存在疑惑的內容，即可快速回饋問題，我們將會跟進處理。
不再提示
10s後關閉
Submitted successfully
Network busy