View Issue Details

IDProjectCategoryView StatusLast Update
0000118Oberon PlatformPlatform functionalitiespublic2014-08-03 13:21
Reporteradministrator Assigned Toadministrator  
PrioritynormalSeverityfeatureReproducibilityalways
Status resolvedResolutionfixed 
Product Version4.1 - DB build 0071 
Target Version4.2 - DB build 0072Fixed in Version4.2 - DB build 0072 
Summary0000118: Distinguish object lock and file lock
DescriptionCurrently 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.
TagsNo tags attached.

Activities

administrator

2014-08-03 13:21

administrator   ~0000183

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