View Issue Details

IDProjectCategoryView StatusLast Update
0000054Oberon PlatformContext Designpublic2014-08-02 17:13
Reporterg_prajeesh Assigned Toadministrator  
PriorityhighSeverityfeatureReproducibilityalways
Status closedResolutionfixed 
Summary0000054: When a user has edit permission, he should have lock/unlock permission by default
DescriptionWhen a user has edit permission in a Stage, he should have lock / unlock permission implicitly.
TagsNo tags attached.

Activities

administrator

2011-05-12 01:18

administrator   ~0000066

A user can LOCK an object if:
- the object is not already locked
and he has the lock access in the object's current stage

A user can UNLOCK an object if:
- he is the locker
or he has the unlock access in the object's current stage

If an object is locked and you are not the locker, you can perfom any action on the object.

g_prajeesh

2011-05-12 08:59

manager   ~0000068

In Context Designer UI, I have to explicitly select the lock. Most of the cases when a user edit business Object, he has to lock the object so that no one else can update the object at the same time.

"If an object is locked and you are not the locker, you can perfom any action on the object."

The above line is confusing me. If an object is locked and I am not the locker, I should not be allowed to modify it. Only locked person can modify it. I hope current implements hold this.

administrator

2014-08-02 17:13

administrator   ~0000177

Sorry, there is a mistake in the sentence; obviously the correct one is:

"If an object is locked and you are not the locker, you CAN'T perfom any action on the object."

Issue History

Date Modified Username Field Change
2011-05-11 13:15 g_prajeesh New Issue
2011-05-12 01:18 administrator Note Added: 0000066
2011-05-12 01:18 administrator Status new => closed
2011-05-12 01:18 administrator Resolution open => fixed
2011-05-12 01:20 administrator Status closed => assigned
2011-05-12 01:20 administrator Assigned To => administrator
2011-05-12 01:20 administrator Status assigned => resolved
2011-05-12 08:59 g_prajeesh Note Added: 0000068
2014-08-02 15:39 g_prajeesh Status resolved => closed
2014-08-02 17:13 administrator Note Added: 0000177