Lock out other worksets?

[patricks]

Is there a way to make either non-editable worksets or those checked out by others completely non-editable, i.e. you can't even click on or select those objects/views/standards, etc?

[beegee]

Well, its not really a security tool, but you can create a "dummy" log-in, called say "Lock-out", and then create a new workset, transfer objects to that workset and save without relinquishing that workset. Log-out, and it will appear to other users that that cannot get at that workset.

All false of course, they would only have to log-in under that user name to do so.


Is there a way to make either non-editable worksets or those checked out by others completely non-editable, i.e. you can't even click on or select those objects/views/standards, etc?

[paul.licameli]

patricks, aren't you simply asking for the effects of the Editable Only checkbox?

However you may also consider the alternative of not using worksets at all for the control of editability in version 8.1 and later.

[ajayholland]

The “Editable Only” checkbox might work for those in a highly conscious mode, but it is not fool proof. Users who inadvertently delete or modify objects will probably not remember to check the box! Furthermore, the box is automatically cleared after STC.

Another solution for this problem (suggested by a colleague) is to use Design Options. Objects placed in a “locked objects” option set are less likely to be selected because the “exclude options” checkbox is checked by default.

On the downside, hosted objects and their hosts must both be assigned to the option.

~AJH