Hi Mark,
You have to specify the trigger as a type trigger, and then put an
inclusion list on it.
Depending on how you have written the script you will need to process the
branch type to see
if it is valid for removal or not.
Eg:
ct mktrtype -type -brtype -all -preop rmtype -exec .....
This will fire as a preop on rmtype, on all branch types.
If you want to extend it to all meta-data types then the command extends to:
ct mktrtype -type -brtype -all -lbtype -all -attype -all -hltype
-all -eltype -all -preop rmtype -exec ...
Your script, however, has to do more testing to see what is actually being
removed and take appropraite action.
You then have to work out who the user is, some may be allowed to do this.
The -nuser switch could be used here or
your script extends further to do user processing against which type etc.
Some users may be allowed to remove attribute types,
but not branches for example. Then of course you have which VOB are they in.
Support for all the above is provided by our tool Access*Rite and provides
an easy to use GUI so you don't have to worry about trigger type
creation.
Just one of its many features.
Hope this helps.
Steve.
At 11:47 AM 2/29/00 +0000, you wrote:
>Hi,
>How do I put a trigger to stop any users removing a branch type (or any
>other type). I have the script but I want to do it the same way as
>putting a "ct mktrtype -element -all -pre ....." trigger in place
>
>Regards
>
>Mark
>
> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
>
Steve Toop
Patriate Limited
Highview House, Charles Square
Bracknell, Berkshire RG12 1DF
DDI: 01344 646041 Mobile: 07860 364311
Fax: 01344 304728
Main Tel: 01344 397228
steve@patriate.com WWW: Patriate.com
CLEARly making the difference..
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
This archive was generated by hypermail 2b29 : Sun May 06 2001 - 00:23:31 EDT