Why not indeed? It would help if I looked properly at the options
available!! I never saw the "user does not belong..." condition.
Yours is a much simpler solution. Thanks.
Nigel.
available!! I never saw the "user does not belong..." condition.
Yours is a much simpler solution. Thanks.
Nigel.
--- In vantage@yahoogroups.com, "Ross Hughes" <ross.hughes@...> wrote:
>
> Why not just throw an exception error for the action with the
"raise an
> exception based on the designed template' approach instead of the
4GL code.
> This will stop the BO update and give you a message box (design
template)
> option.
>
> You can also add an AND to the conditions and insert a 'user DOES
NOT belong
> to group' condition as well.
>
> So:
>
> Condition 1: the ttOrderHed.TermsCode field has been changed from
any to
> any.
> AND
> Condition 2: 'user DOES NOT belong to SG002'
>
> Action: raise an exception based on the designed template. (insert
message
> box text in designed template).
>
> Another possibility.
>
> Ross
>
> -----Original Message-----
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On
Behalf Of
> Nigel Kerley
> Sent: Wednesday, January 07, 2009 9:19 AM
> To: vantage@yahoogroups.com
> Subject: [Vantage] Re: Make a field Read Only to all but certain
Security
> Groups
>
> This has been asked before but I don't think there was a
satisfactory
> solution. I reckon the best way is by BPM. I have a need for this
as
> well, so I though I'd have a look at it now. Here's what I've come
up
> with:
>
> A pre-processing directive against the SalesOrder.Update BO.
>
> One condition: the ttOrderHed.TermsCode field has been changed from
> any to any.
>
> One action: execute the following 4GL code
> Code:
> Find first ttOrderHed where ttOrderHed.RowMod = 'A' or
> ttOrderHed.RowMod = 'U' NO-LOCK NO-ERROR.
> If available ttOrderHed then do:
> find UserFile where UserFile.DcdUserID = DCD-UserID no-lock.
> if INDEX(UserFile.GroupList, 'SG002') = 0 then do:
> {lib/PublishEx.i &ExMsg = "'You do not have permission to
> change this field.'" }
> {&THROW_PRIVATE}.
> end.
> end.
>
> "SG002" is the code for the security group of those allowed to
amend
> the field.
>
> It seems to work, but I haven't finished testing it yet.
>
> Nigel.
>
>
>
> --- In vantage@yahoogroups.com, "Calvin Krusen" <ckrusen@> wrote:
> >
> > What's the 'Best' way to make a field default to R/O, but be R/W
to
> a
> > certain Security Group?
> >
> > I need to make the Terms field on the Order Entry program be R/O
> for
> > all but a specific Security Group. I still need the terms field
to
> be
> > auto-populated by when a custeomer ID is entered, but don't want
OE
> > folks to be able to change it.
> >
> > Should I go for a...
> > A) Customization (I've already did some in the OE program)
> > B) A BPM
> > C) Field Security
> > D) something entirely differant
> >
> > Thanks
> >
> > Calvin
> >
>
>
>
> ------------------------------------
>
> Useful links for the Yahoo!Groups Vantage Board are: ( Note: You
must have
> already linked your email address to a yahoo id to enable access. )
> (1) To access the Files Section of our Yahoo!Group for Report
Builder and
> Crystal Reports and other 'goodies', please goto:
> http://groups.yahoo.com/group/vantage/files/.
> (2) To search through old msg's goto:
> http://groups.yahoo.com/group/vantage/messages
> (3) To view links to Vendors that provide Vantage services goto:
> http://groups.yahoo.com/group/vantage/linksYahoo! Groups Links
>