When I tried the following in the 'Run If' of my active link I was testing with, it did NOT work:
'Group List' = "1;" So, it didn't make any difference whether I was using a LIKE operation with wildcards or an equals operation with an explicit group ID value. I'm more inclined to believe that the inconsistencies you are observing are related to the special behavior of the 'Group List' field, and not indicative of a general issue with LIKE searches in other workflow. My server is ARS 7.0.01 Patch 001, my user tool is 7.0.01 Patch 007. Are you running your 7.0.1 client against a 7.0.1 server, or against the 5.1.2 server that you're planning to upgrade? Also, just out of curiosity, what is the underlying database you are using? This is probably trivial, but one other difference I noticed in your search syntax -- your 'Group List' field appears to contain an underscore character, which is not the format I have in my User form that was installed with ARS 7.0.1. Just to be sure, is this the same default 'Group List' field that you are searching in your active link? ----- Original Message ----- From: "McManus Michael A SSgt HQ 754 ELSG/DOMH" <[EMAIL PROTECTED]> Newsgroups: gmane.comp.crm.arsystem.general To: <[email protected]> Sent: Thursday, June 19, 2008 12:09 PM Subject: Re: LIKE qualifications in 7.0 Are you patched? I didn't see anything in the patch notes specifically relating to this, but maybe I just missed it. I just changed my qualification to the following: ('Group_List' LIKE "%" + "System" + "%") OR ('Group_List' LIKE "%" + "Admin" + "%") and it still fails the qualification. Here's the other thing that doesn't make sense to me. You mention that you think Run If qualifications are compared against the values in the client, and I'd be inclined to agree except when I change the qualification to the following: ( 'Group_List' = "275;" ) OR ( 'Group_List' = "1;" ) OR ( 'Group_List' = "285;" ) It passes the qualification. Those Group IDs are not what appears in the client. Does the LIKE operator compare against the values displayed in the client and the = operator compare against the DB? I guess that makes sense. Sorry to beat a dead horse, but this seems like decidedly inconsistent behavior and I'm really not looking forward to parsing 2200 active links when I'm unsure what the problem is. Michael A. McManus, SSgt, USAF Remedy Developer HQ 754 ELSG/DOMH -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Thomas Bean Sent: Thursday, June 19, 2008 10:56 AM To: [email protected] Subject: Re: LIKE qualifications in 7.0 ** Michael, I tested this in a 'Run If' qualification in active link on my system (ARS 7.0.1). Either of the following worked correctly: * 'Group List' LIKE "%" + "Administrator" + "%" * 'Group List' LIKE "%Administrator%" However, using the Group ID search method did NOT work. So, this seems to confirm my suspicion that the 'Run If' on an active link is just searching the displayed values on the screen, rather than the actual values stored in the database. As to why your original syntax (using the concatenation operator between the search value and the wildcard characters) didn't work in your 7.0.1 client, is still a mystery to me. ----- Original Message ----- From: "McManus Michael A SSgt HQ 754 ELSG/DOMH" <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > Newsgroups: gmane.comp.crm.arsystem.general To: <[email protected] <mailto:[email protected]> > Sent: Thursday, June 19, 2008 10:29 AM Subject: Re: LIKE qualifications in 7.0 Tell me about it. I tried the following as the Run If qualification in that active link: 'Group_List' LIKE "275;%" OR 'Group_List' LIKE "1;%" OR 'Group_List' LIKE "285;%" And it fails the qualification. However, if I run that in the Advanced Query Bar, I get everyone who belongs to one of those three groups. If I change the qualification to: ( 'Group_List' = "275;" ) OR ( 'Group_List' = "1;" ) OR ( 'Group_List' = "285;" ) It passes the qualification and that also works in the advanced query bar. Perhaps I'm just failing to understand the difference between advanced queries and Run If qualifications and how they're interpreted. I still can't wrap my head around why this: ( 'Group_List' LIKE (( "%" + "System" ) + "%" )) OR ( 'Group_List' LIKE (( "%" + "Admin" ) + "%" )) And this: ('Group_List' LIKE "%System%") OR ('Group_List' LIKE "%Admin%") Are different. I'm a layman, but it seems to me that those would evaluate to the exact same thing. Michael A. McManus, SSgt, USAF Remedy Developer HQ 754 ELSG/DOMH -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Thomas Bean Sent: Thursday, June 19, 2008 10:14 AM To: [email protected] <mailto:[email protected]> Subject: Re: LIKE qualifications in 7.0 Strange. The 'Run If' qualification in an active link would technically not be issuing a search to the database -- it is simply searching the values already displayed in the client. That may be why your qualification worked using group names instead of Group IDs. What happens if you change the 'Run If' qualification in the active link to search on the Group IDs instead of the group names? If it works using the Group IDs, I would recommend going that route. The qualification will be a lot lengthier, but I think this would be a more consistent solution between ARS versions. --Thomas ----- Original Message ----- From: "McManus Michael A SSgt HQ 754 ELSG/DOMH" <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > Newsgroups: gmane.comp.crm.arsystem.general To: <[email protected] <mailto:[email protected]> > Sent: Thursday, June 19, 2008 7:23 AM Subject: Re: LIKE qualifications in 7.0 Very bizarre. If I run the query in the advanced search bar in the WUT, I get no results. However, I changed the Run If qualification on one of our dev servers to the following: ('Group_List' LIKE "%System%") OR ('Group_List' LIKE "%Admin%") It's a 7.0.01 server and I'm using a 7.0.01 WUT. For some reason, it works. I logged it, and it passes the qualification. Just to make sure I'm not out of my mind, I changed it back to: ( 'Group_List' LIKE (( "%" + "System" ) + "%" )) OR ( 'Group_List' LIKE (( "%" + "Admin" ) + "%" )) And I received the error message again. It fails the qualification with the latter query, but it passes with the former query. And to boot, neither query will return a set of results in the advanced search bar. Michael A. McManus, SSgt, USAF Remedy Developer HQ 754 ELSG/DOMH -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Thomas Bean Sent: Wednesday, June 18, 2008 6:08 PM To: [email protected] <mailto:[email protected]> Subject: Re: LIKE qualifications in 7.0 ** Michael, I don't think this has anything to do with the way LIKE qualifications are handled between version 5.1.2 and 7.0.1. Even if you change "%" + "System" + "%" to "%System%", the issue is most likely related to the fact that the 'Group List' field does not actually store explicit group names -- it actually stores a semicolon-delimited list of Group IDs. I tried a similar search on my User form, using the Advanced Search bar with a LIKE qualification: 'Group List' LIKE "%Administrator%" This returned NO results. However, the following query will return all Users in the "Administrator" group (group ID 1). 'Group List' LIKE "1;%" OR 'Group List' LIKE "% 1;%" OR 'Group List' LIKE "%;1;" AFAIK, this has always been the proper method to search the 'Group List' field (see attached document titled "How To Query On The Group List Field", circa ARS 3.x). I'm pretty sure this is still valid. Now, I am curious why this seems to have worked differently in ARS 5.1... Perhaps this version allowed searches on the 'Group List' field with explicit group names, or maybe it was only possible in the "Run If" statement on an Active Link??? --Thomas ----- Original Message ----- From: Grooms, Frederick W <mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > Newsgroups: gmane.comp.crm.arsystem.general To: [email protected] <mailto:[email protected]> Sent: Wednesday, June 18, 2008 3:59 PM Subject: Re: LIKE qualifications in 7.0 ** What happens if you run your qualification in the Advanced Query bar on your v7 User tool. You should get a list of users. ________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of McManus Michael A SSgt HQ 754 ELSG/DOMH Sent: Wednesday, June 18, 2008 2:02 PM To: [email protected] <mailto:[email protected]> Subject: LIKE qualifications in 7.0 We're in the process of upgrading our AR System Server and Clients from version 5.1.2 to 7.0.01 and I've run into a bit of a problem. I was asked to upgrade my User and Admin tools to 7.0.01 on my PC for testing purposes, and to draft an implementation plan. Our server is still 5.1.2 but I was under the impression that the WUT is backwards compatible and I generally do very little day-to-day work in the WUT anyway. Anyhow, I upgraded with no problems and was able to login with no problems. I did a cursory examination of some workflow and everything seemed okay. This morning, I got a request to change the Group of a user. I went to the USER form, made the required changes, and clicked a button to Add them as a System POC and received an error: "Before attempting to add a System POC, their Group List must be set to System POC or System POC Manager. (ARERR 75001) The preceding message occurred during the execution of active link USER:Add A New POC -- action 1. (ARNOTE 1101)" The first line is the Message action in the Else action of the above Active Link. The problem is, I did in fact change the Group List of the user to System POC. I went to the Admin tool and checked the Run If qualification for that Active Link: ( 'Group_List' LIKE (( "%" + "System" ) + "%" )) OR ( 'Group_List' LIKE (( "%" + "Admin" ) + "%" )) Just to make sure I hadn't screwed up somewhere along the line, I had one of my coworkers attempt the change on his 5.1.2 WUT and it worked perfectly. To make sure it wasn't a backwards compatibility problem, I tested the workflow on our 7.0.01 dev server and received the same error. I looked through the Release Notes as well as the "What's new in 7.0.01" docs and didn't see any issues about LIKE qualifications being interpreted differently in 7.0.01 versus 5.1.2 and I checked the patch notes for 7.0.01 just to see if it was a possible bug. No luck. I asked an old coworker of mine who now works on a 7.1 server if he'd experienced anything like this, and he mentioned that I could change "%" + "System" + "%" to "%System%" That's all well and good, but this is only one active link in a fairly large beast of an application. Did something change in the way the WUT interprets LIKE qualifications? Thanks much, Michael A. McManus, SSgt, USAF Remedy Developer HQ 754 ELSG/DOMH __Platinum Sponsor: www.rmsportal.com <http://www.rmsportal.com> ARSlist: "Where the Answers Are" html___ __Platinum Sponsor: www.rmsportal.com <http://www.rmsportal.com> ARSlist: "Where the Answers Are" html___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org <http://www.arslist.org> Platinum Sponsor: www.rmsportal.com <http://www.rmsportal.com> ARSlist: "Where the Answers Are" __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
