Main | My View | View Issues | Change Log | Roadmap | Docs
  

Viewing Issue Simple Details [ Jump to Notes ] [ View Advanced ] [ Issue History ] [ Print ]
ID Category Severity Reproducibility Date Submitted Last Update
0000118 [Oberon Platform] Platform functionalities feature always 2014-08-03 13:12 2014-08-03 13:21
Reporter administrator View Status public  
Assigned To administrator
Priority normal Resolution fixed  
Status resolved   Product Version 4.1 - DB build 0071
Summary 0000118: Distinguish object lock and file lock
Description Currently if a user lock an object other users are not able to perform any actions on it except the read / fileget operations when allowed by user privileges. If a user1 locks an object and another user2 gets the file with lock option checked the file is locked by user2 while object is locked by user1.
We need a mechanism to distinguish between the object lock and file lock.
Additional Information
Tags No tags attached.
Attached Files

- Relationships

-  Notes
(0000183)
administrator (administrator)
2014-08-03 13:21

 The new platform version introduces 2 levels for locks: object lock and file lock are separated. These are the new rules:

1. if object is locked by another user you cannot lock it or perform other operations ( edit, fileput, progress..... )
2. if you have the unlock privilege, you may unlock a locked object, but now there is a flag to choice if extend or not the unlock to all attached files. So you can unlock the object but leave the locks on the files.
3. if a file is locked by another user you can't update (fileput) the same file (overwrite the file in the filespace)
4. if you download a locked file, you can unlock it only if you are the locker
5. you can upload and lock files even if there are other files locked by other users

There are two new commands : object filelock and object fileunlock to let the user to lock an unlocked file or unlock a previous locked file without the need to download it. Obviously a user can unlock only files locked by himself.

- Issue History
Date Modified Username Field Change
2014-08-03 13:12 administrator New Issue
2014-08-03 13:12 administrator Fixed in Version => 4.2 - DB build 0072
2014-08-03 13:12 administrator Target Version => 4.2 - DB build 0072
2014-08-03 13:21 administrator Note Added: 0000183
2014-08-03 13:21 administrator Status new => resolved
2014-08-03 13:21 administrator Resolution open => fixed
2014-08-03 13:21 administrator Assigned To => administrator
© 2008-2013 Mirko Solazzi | Website Templates by IceTemplates.com
Please Read: Privacy Policy and Terms of Use
Powered by Mantis Bugtracker
Copyright © 2000 - 2008 Mantis Group