I think you are correct in your description of the situation. If it helps
anyone, one of the tricks I use is that if you are ever in a situation
where some of the records have a leading delimiter and some don't, then
just add them as part of the qualification. For example, if some of your
Group_List fields (user form) had "480;490;", but some had "480;490" or
";480;490;", etc... you could just add a semi-colon at the beginning and
end of your field name, and then you know one is there. For example,
(NOT($Group_List$ LIKE "%;480;%") AND NOT($Group_List$ LIKE "480;%"))
becomes
NOT(";" + $Group_List$ + ";" LIKE "%;480;%")
Hopefully that helps someone.
Thad Esser
Remedy Developer
"Argue for your limitations, and sure enough, they're yours."-- Richard
Bach
"LJ Longwing" <[EMAIL PROTECTED]>
Sent by: "Action Request System discussion list(ARSList)"
<[email protected]>
03/13/2008 03:55 PM
Please respond to
[email protected]
To
[email protected]
cc
Subject
Re: Using "Not Like"
**
I know that when you used to search on the Group field in user, the first
record didn't have a ; in front of it, so you had to do this weird is it
the first, is it in the middle, is it at the end, type of search, but I
think since the inception of the $GROUPIDS$ keyword, they have put a ; at
the beginning and end of each value so you didn't hafta do that funky
search
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Wheeler, Dylan
Sent: Thursday, March 13, 2008 4:06 PM
To: [email protected]
Subject: Re: Using "Not Like"
**
Yeah, I got an email from Doug M and checked it. I was wrong on the
leading ;
There is one, I could of swore the first ID didn't have one. Maybe I had a
specific instance that had one of those "undocumented features" out there
and assumed it was always like that.
It is GROUPIDS though
So depending on if your an optimist or pessimist, we're both right/wrong
:)
My qual works but it has extra unneeded workflow in it, which I'll have to
correct on the workflow I already have out there hehe.
So Christopher,
Either will work but the best one to use would be
NOT($GROUPIDS$ LIKE ?%;1;%?)
-------------
Dylan Wheeler
Production Control Analyst Principal
IT Operations
Downey Savings & Loan Association, F.A.
Email: [EMAIL PROTECTED]
-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of LJ Longwing
Sent: Thursday, March 13, 2008 2:34 PM
To: [email protected]
Subject: Re: Using "Not Like"
**
I think if you look at your $GROUPID$ (is there an s in there) you will
find that there is a ; before the first group, specifically so you can do
this type of search...but it's been a LONG time since I have used that
Qual, so I can't be entirely sure.
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Wheeler, Dylan
Sent: Thursday, March 13, 2008 3:01 PM
To: [email protected]
Subject: Re: Using "Not Like"
**
Your qual would fail if Administrator was the first group because of the
leading ; though
Personally I use GROUPIDS instead of GROUPS unless I have to. But if you
remove the leading ; then any group that has 1 in the id would come up.
I guess the best way would be something like
(NOT($GROUPIDS$ LIKE ?%;1;%?) AND NOT($GROUPIDS$ LIKE ?1;%?))
The ; is the way Remedy knows how to seperate the groups. So if you have
two groups in your Group List, like Adminstrator(1) and APP-Support(12345)
then the database value of that field would be
1; 12345;
-------------
Dylan Wheeler
Production Control Analyst Principal
IT Operations
Downey Savings & Loan Association, F.A.
Direct: 949.509.4565
Fax: 949.509.7841
Email: [EMAIL PROTECTED]
-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of LJ Longwing
Sent: Thursday, March 13, 2008 1:47 PM
To: [email protected]
Subject: Re: Using "Not Like"
**
Wouldn't you want
NOT($GROUPID$ LIKE ?%;1;%?)
to avoid the problem of Administrator being part of another groups string?
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Moore, Christopher Allen
Sent: Thursday, March 13, 2008 2:39 PM
To: [email protected]
Subject: Re: Using "Not Like"
**
J
I?ll give it a shot.
Thanks!
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Dylan
Sent: Thursday, March 13, 2008 3:37 PM
To: [email protected]
Subject: Re: Using "Not Like"
NOT($GROUPS$ LIKE ?%Administrator%?)
That should work.
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Moore, Christopher Allen
Sent: Thursday, March 13, 2008 12:31 PM
To: [email protected]
Subject: Using "Not Like"
Hey Everyone-
We have an OOTB active link we want to make not run for administrators. It
sets fields on TSK to read-only when a task is closed, but we would like
administrators to be able to re-open closed tasks. While we could make an
active link that runs after the one that makes the field read only reverse
that, I would like to add to the run if condition of the original active
link if possible.
However, to do this all I can think is to add something along the lines of
$GROUPS$ NOT LIKE ?Administrator?. However, I don?t think you can do
that.
$GROUPS$ != ?Administrator? doesn?t work, we tried that. It did work when
we did $USER$ != my user name.
Is there a way to do a ?not like?? Or should I resign myself to letting
Remedy do what it wants and then un-doing it in a separate action?
Thanks!
Chris
__Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
html___ __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers
Are" html___ __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the
Answers Are" html___ __Platinum Sponsor: www.rmsportal.com ARSlist: "Where
the Answers Are" html___
This message and any attachments are for the intended recipient(s) only
and may contain privileged, confidential and/or proprietary information
about Downey Savings or its customers, which Downey Savings does not
intend to disclose to the public. If you received this message by
mistake, please notify the sender by reply e-mail and delete the message
and attachments.
__Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
html___ __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers
Are" html___
__Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
html___
__Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
html___
***IMPORTANT NOTICE: This communication, including any attachment, contains
information that may be confidential or privileged, and is intended solely for
the entity or individual to whom it is addressed. If you are not the intended
recipient, you should delete this message and are hereby notified that any
disclosure, copying, or distribution of this message is strictly prohibited.
Nothing in this email, including any attachment, is intended to be a legally
binding signature.***
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
