4.1.6.3
Added task edit locks to prohibit concurrent editing of scheduled tasks, pipeline tasks, API tasks, and data service apps by multiple users.
When a task is opened and edited by multiple users simultaneously, the content saved later will overwrite the earlier saved version, resulting in the accidental deletion of the previously developed work.
FineDataLink employs task edit locks to prohibit concurrent editing of scheduled tasks, pipeline tasks, API tasks, and data service apps by multiple users.
A task currently being edited by one user is locked against editing by others. Other users opening it can only view the task and will receive a prompt "The current task/service/application is being edited by Username.", as shown in the following figure.
Applicable objects: scheduled tasks, pipeline tasks, API tasks, and data service apps
Scenarios where edit locks occur:
Multiple users open the same scheduled task/pipeline task/API task/data service app.
A user opens multiple tab pages in the same browser/multiple pages in different browsers.
1. If User B and User C open the same scheduled task that User A is editing, B and C will receive a prompt "The current task is being edited by A.", indicating that B and C cannot edit the task and can only view it, as shown in the following figure.
2. When User A exits the task editing page without clicking Save, User B and User C will receive a prompt on their editing page "A has exited editing." The FineDataLink project will automatically assign editing permission to the user (B/C) who clicks Refresh first. If User B obtains editing permission, User C will receive a prompt "The current task is being edited by B."
3. When a user clicks Save and exits the editing page, the other users will receive a prompt on their editing page "XX has exited editing. The configuration of the current task has been updated. Refresh it promptly.", as shown in the following figure.
Whoever clicks Refresh first will gain editing permission.
If a scheduled task is being edited by a user, Save and Run on the toolbar will be disabled for other users, as shown in the following figure.
When an edit lock occurs, the toolbar is described as follows.
1. Task Information, Scheduling Plan, and Task Control are not affected by the edit lock and follow the "later operation overwrites earlier one" logic.
2. When the task editing page is in the edit-locked state, Parameter List only allows viewing.
If a scheduled task is being edited by a user, the other users can still rename or move the task, as shown in the following figure.
The details are as follows.
1. Name and Description and Move to are not affected by the edit lock and follow the "later operation overwrites earlier one" logic. The Export function remains available.
2. If a scheduled task is being edited by a user, the other users cannot delete the task.
1. If Users B and C open the same pipeline task that User A is editing, B and C will receive a prompt "The current task is being edited by A." Users B and C can only view it, and all configuration items are grayed out, as shown in the following figure.
2. When User A clicks Save and exits the editing page, Refresh will be available on the editing page of Users B and C. Click Refresh to refresh the page and view the latest saved configuration, as shown in the following figure.
3. When User A exits the editing page without clicking Save, Users B and C will receive a prompt on their editing page "A has exited editing." The FineDataLink project will automatically assign editing permission to the user (B/C) who clicks Refresh first. If User B obtains editing permission, User C will receive a prompt "The current task is being edited by B."
1. If Users B and C open the same API task that User A is editing, B and C will receive a prompt "The current service is being edited by A." Users B and C can only view it, and all configuration items are grayed out, as shown in the following figure.
3. When User A exits the editing page without clicking Save, Users B and C will receive a prompt on their editing page "A has exited editing." The FineDataLink project will automatically assign editing permission to the user (B/C) who clicks Refresh first. If User B obtains editing permission, User C will receive a prompt "The current service is being edited by B."
4. When User A is editing an API task, other users cannot activate or deactivate the API task, as shown in the following figure.
5. If a user opens multiple tab pages in the same browser/multiple pages in different browsers and creates an API task in the same directory, the subsequently created task will be locked, as shown in the following figure.
1. If Users B and C open the same app that User A is editing, B and C will receive a prompt "The current application is being edited by A." Users B and C can only view it, and all configuration items are grayed out, as shown in the following figure.
User A opens a scheduled task. At this point, User A loses network connection, and User B also opens the same scheduled task.
When User A reconnects after network disconnection:
If User B has exited the editing page, User A can continue editing the scheduled task.
If User B has not exited the editing page, User A will encounter an edit lock and receive the prompt "The current task is being edited by B."
When User A is editing a scheduled task, User B enters the task viewing page. Then, User A exits the editing page, but the edit lock is still displayed on User B's page.
The admin can open the task and release the lock:
When User A is editing Task 1, User B is modifying/deleting the configuration such as the tasks/data connections/server datasets referenced by Task 1.
There is no lock. During the saving of Task 1, a configuration loss validation will be triggered.
User A renames Task 1 Task 2 on the Task 1 editing page but has not clicked Save yet. User B renames Task 1 Task 3 in the task list. Finally, User A clicks Save.
User A is the last to click Save, so Task 1 is ultimately renamed to Task 2.
滑鼠選中內容，快速回饋問題
滑鼠選中存在疑惑的內容，即可快速回饋問題，我們將會跟進處理。
不再提示
10s後關閉
Submitted successfully
Network busy