Salesforce

WorldServer - how are target assets/tasks getting locked and unlocked?

« Go Back

Information

 
TitleWorldServer - how are target assets/tasks getting locked and unlocked?
URL Name000020117
SummaryThis article provides the details.
Scope/EnvironmentWorldServer
Question
We are having issues with tasks/target assets that are locked in our system, leading to issues like the one described in this article

WorldServer - Error when importing a Return package - 'Current user does not have privilege to unlock asset'

Can you tell us how these assets get locked and unlocked?
Answer
1- When a user works in Worldserver on the project's Tasks page:
  • A target asset becomes locked when the user opens the corresponding Task in Browser Workbench and clicks on Save is done.
  • When a user opens a Task in Browser Workbench, he/she will also automatically claim the task, or the user will be prompted to claim the task before being able to open the Task in Browser Workbench.
  • Just claiming the task and/or opening an asset/task in Browser Workbench without saving will NOT lock the target asset in Explorer.
  • The Save operation is what locks the asset. Unclaiming the Task corresponding to the locked asset will also unlock the asset (even if the task is still open in Browser Workbench).
  • Another Save in Browser Workbench will lock the task again (it will also claim it again).
  • Also completing a Task's step assigned to the user who has locked the asset will automatically unlock the asset because the completion of a human step unclaims the step from the user.
2- When working in WorldServer Explorer, both in "new" Explorer (from version 11.5) and old Explorer (before version 11.5):
  • An asset gets locked by a user if the user opens that asset in Browser Workbench and does a Save. No Save= no lock.
  • Note: closing Browser Workbench in Explorer will *NOT* unlock the asset automatically! So the user should unlock it in Explorer by selecting the locked asset and going to File/Unlock
Reference
Attachment 1 
Attachment 2 
Attachment 3 
Attachment 4 
Attachment 5 

Powered by