Thanks to everyone for your assistance. We got it to work!

-----Original Message-----
From: Action Request System discussion list(ARSList) 
[mailto:[email protected]] On Behalf Of Rick Westbrock
Sent: Monday, April 22, 2013 14:49
To: [email protected]
Subject: Re: Allowing Status Change By Group Membership

** 

Hmm, the 7.6.04 docs show that the percentage sign when used in a LIKE 
operation "matches any string of 0 or more characters" which is why I didn't 
add a clause for nothing at the end. I did test it with group ID 1 (and the 
string Administrator) at the end of the Group List field and it matched the 
filter qualification.

 

-Rick

 

 

___________________________

Rick Westbrock

QMX Support Services

 

From: Action Request System discussion list(ARSList) 
[mailto:[email protected]] On Behalf Of Longwing, Lj
Sent: Monday, April 22, 2013 10:12 AM
To: [email protected]
Subject: Re: Allowing Status Change By Group Membership

 

** 

Rick,

Yes, $GROUPS$ is messy, which is why they added the $GROUPIDS$ keyword, and to 
avoid the exact issue you are discussing, the keyword for group ids always has 
a semicolon at the beginning and end of the string, so you don't need to do 
what you describe.

 

Oh...and you are forgetting the groups being at the END of the string...so when 
using it you need to not only do '1234;%', '%;1234;%', but also '%;1234'...very 
ugly :)

 

On Mon, Apr 22, 2013 at 10:44 AM, Rick Westbrock <[email protected]> wrote:

** 

Does the system just read the Group List field of the User record when 
resolving the operation? If so then wouldn't you also need to use LIKE "12345%" 
since the first group wouldn't have the leading semi-colon? I was using this 
extra clause when checking to see if group ID 1 was in the Group List (field ID 
104) of a supporting form (which is fed from the User form). In my case I'm 
using 'Group List' LIKE "1;%" OR 'Group List' LIKE "%;1;%" to check for the 
Admin group being the first or later in the field.

 

-Rick

 

___________________________

Rick Westbrock

QMX Support Services

 

From: Action Request System discussion list(ARSList) 
[mailto:[email protected]] On Behalf Of Longwing, Lj
Sent: Monday, April 22, 2013 9:30 AM
To: [email protected]
Subject: Re: Allowing Status Change By Group Membership

 

** 

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"

 

_ARSlist: "Where the Answers Are" and have been for 20 years_ 

_ARSlist: "Where the Answers Are" and have been for 20 years_

 

_ARSlist: "Where the Answers Are" and have been for 20 years_ 

_ARSlist: "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"

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to