Yolanda,
First I would suggest you utilize the group id keyword instead of the
groups keyword, only from the perspective that group names can
'overlap'...meaning you can have an 'Admin' and 'Contact Admin', and if you
do groups like admin...both would match....but not if you utilize the group
id keyword properly...and I assume you want to throw an error when someone
other than the groups try...so you would want to try something like this
('Status' = "Scheduled" OR 'Status' = "Cancelled" OR ('Status = "Denied"
AND 'Organization' = "EAST)) AND NOT ($GROUPIDS$ LIKE "%;12345;%
OR $GROUPIDS$ LIKE "%;23456;%"
please note the ; on both sides of the group ID. This helps ensure that
the group id is fully encased, and not part of another group number.
On Mon, Apr 22, 2013 at 10:12 AM, Yolanda Collier <
[email protected]> wrote:
> We have a custom application and the customer would like to limit the
> user's ability to change the status, unless that person is a member of a
> particular organization. You must be a member of certain groups in order to
> change the status to Scheduled, Cancelled, or Denied.
>
> We have attempted to used ($GROUPS$ LIKE "%ABC%") OR ($GROUPS$ LIKE
> "%XYZ%") OR (($GROUPS$ LIKE "%DFG%") AND ('Status' = "Scheduled")) OR
> ('Status' = "Cancelled") OR (('Status' = "Denied") AND ('Organization' =
> "EAST"))
>
> and we have attempted to use (NOT ($GROUPS$ LIKE "%ABC%") and it is still
> not working.
>
> Any suggestions on how to successfully implement would be greatly
> appreciated.
>
>
> _______________________________________________________________________________
> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
> "Where the Answers Are, and have been for 20 years"
>
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"