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
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 matchbut not if you utilize the group
id
: Action Request System discussion list(ARSList)
[mailto:arslist@ARSLIST.ORG] On Behalf Of Longwing, Lj
Sent: Monday, April 22, 2013 9:30 AM
To: arslist@ARSLIST.ORG
Subject: Re: Allowing Status Change By Group Membership
**
Yolanda,
First I would suggest you utilize the group id keyword instead
Hi Yolanda,
Using $GROUPS$ or $GROUPID$ to query for membership is always a bit messy
and error prone. There is a run process purpose built for this type of
activity, you just need to do a 2 step process instead of trying to do it
all in your Run If qual.
You set a field with this run process
(ARSList) [mailto:
arslist@ARSLIST.ORG] *On Behalf Of *Longwing, Lj
*Sent:* Monday, April 22, 2013 9:30 AM
*To:* arslist@ARSLIST.ORG
*Subject:* Re: Allowing Status Change By Group Membership
** **
**
Yolanda,
First I would suggest you utilize the group id keyword instead
Curtis,
I don't like using that particular run-process, because in situations like
this you need to filters to do a single job, and a temp field for EACH
group you want to check...the run-if that I outlined before will work
reliably (as long as you use it properly) with a single piece of workflow,
@ARSLIST.ORG
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
Message-
From: Action Request System discussion list(ARSList)
[mailto:arslist@ARSLIST.ORG] On Behalf Of Collier, Yolanda S CTR MSC, N6
Sent: Monday, April 22, 2013 10:39 AM
To: arslist@ARSLIST.ORG
Subject: Re: Allowing Status Change By Group Membership
Thank you all for your input
) [mailto:
arslist@ARSLIST.ORG] On Behalf Of Longwing, Lj
Sent: Monday, April 22, 2013 12:30
To: arslist@ARSLIST.ORG
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
(ARSList)
[mailto:arslist@ARSLIST.ORG] On Behalf Of Longwing, Lj
Sent: Monday, April 22, 2013 9:30 AM
To: arslist@ARSLIST.ORG
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
@ARSLIST.ORG
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
** **
** **
___
Rick Westbrock
QMX Support Services
** **
*From:* Action Request System discussion list(ARSList) [mailto:
arslist@ARSLIST.ORG] *On Behalf Of *Longwing, Lj
*Sent:* Monday, April 22, 2013 10:12 AM
*To:* arslist@ARSLIST.ORG
*Subject:* Re: Allowing Status Change By Group Membership
12 matches
Mail list logo
