You can use these with the $P
Object Permission Constants
The following permission constants define the operations users who have that permission can perform on an object.
PERM_CHECKOUT // can modify an object's versions (and therefore check out the object)
PERM_CREATENODE // can add children to the object
PERM_DELETE // can delete the object
PERM_DELETEVERSIONS // can delete versions of an object
PERM_EDITATTS // can edit the object's category and attributes
PERM_EDITPERMS // can edit the object's permission set
PERM_MODIFY // can modify an object's characteristics (for example, rename
the object)
PERM_REMOVENODE // can delete child objects; this permission must be
included with all objects for Livelink to operate properly
PERM_SEE // can see the object
PERM_SEECONTENTS // can see the contents (child objects and/or data) of an object
PERM_FULL // all permission granted
Just sustitute for example $PSEE is PERM_SEE.In the builder inspector window if you do $PCREATENODE you will get bitmask 4
However the trick is a little hard to explain to a new programmer.The bitmasks are added/subtracted using oscript bit arithmetic you will see things like $PSee<$PSEECONTENTS etc in code which means that I have added those two bits togethrs.Also oscript allows /temms you which bits are 'SET' in a integer.
It is fun and I love bitmasking..
Well, if I called the wrong number, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937
Certified OT Developer,Livelink ECM Champion 2008