Michiel, Its not a string but a integer.. If you try to evaluate $CLIENT-TYPE$ = "13" you will get a data type mismatch error.. you have to evaluate it as $CLIENT-TYPE$ = 13
I got a mail from Remedy support which (although they didn't claim it to be a bug) said that that the value should have been 13 but the feature hadn't been enabled for AIE upto Patch 2 but will be available on Patch 3.. I guess we could interpret that in not so many words as yes it is a bug in its current state, but will be fixed in Patch 3.. thought some of you might be interested in knowing this... Gary, you might want to raise a ticket about runamacro, and I'm sure you will get a similar response.. In my case I want my workflow to identify AIE as setting a transaction or creating an entry and only then for workflow to fire, so my choice is limited to using the $CLIENT-TYPE$ keyword, unless there is another system identifier that could recognize the AIE engine... I have used the user that will run the AIE as well but there is no stopping an admin user from logging in as the AIE user and making changes.. I'm running tests using AIE, by creating or updating a subset of entries - what I did is qualified the data that will be created or updated that returns a reasonable subset of data so testing is not one of my biggest concerns.. Thank you however for your inputs.. Cheers Joe -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] Behalf Of Michiel Beijen Sent: Wednesday, March 26, 2008 4:48 PM To: [email protected] Subject: Re: AIE Client Type - Another #$%# bug??? ** The Client Type is a string that the 'client' -- such as AIE, Remedy User, Runmacro etc -- sends to the server when communicating. I guess when they compiled AIE against the 7.1 libs they failed to set the Client Type? This will probably not be a bug in the 7.1 server but in the 7.1 version of runmacro or in the AIE 2.1 version.... You can test it by connecting AIE 2.1 to an old 6.3 server if you still have one somewhere. One concern on using the $CLIENT-TYPE $ keyword - I would discourage it because it can make troubleshooting really nasty. I like the fact that you can 'talk' to Remedy using user tool - API integration - EIE - whatever and that it will behave the same (not counting active links here). If you'd use the $CLIENT-TYPE $ keyword you can not ever test an interface form directly by opening it in the user tool and submitting a record because you can not 'fake' this keyword with the WUT. -- Met vriendelijke groet / Kind regards Michiel Beijen ______________________________________________________ MANSOLUTIONS Energieweg 60-62 3771 NA Barneveld The Netherlands Tel. +31-(0)612968592 Mail [EMAIL PROTECTED] Internet http://bsm.mansolutions.nl On Wed, Mar 26, 2008 at 6:17 PM, Joe D'Souza <[EMAIL PROTECTED]> wrote: ** I wonder if this is a bug in 7.1 then? What version of the ARS are you running? Has anyone else encountered this where the ARS would assign an unknown client type for even known ones? Joe -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] Behalf Of Opela, Gary L CTR USAF AFMC OC-ALC/ITMA Sent: Wednesday, March 26, 2008 8:35 AM To: [email protected] Subject: Re: AIE Client Type - Another #$%# bug??? Runmacro.exe seems to be doing this for me, even though it isn't supposed to. From what I can tell, runmacro should be 17, however, it's showing up as unknown to my system. Oh well.... Thanks, Gary Opela, Jr Sr. Remedy Developer RSP Certified Leader Communications, Inc. 405 736 3211 -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Joe D'Souza Sent: Wednesday, March 26, 2008 1:59 AM To: [email protected] Subject: AIE Client Type - Another #$%# bug??? ** It looks like the AIE client type is 0!!!!??? The ar.h file has the EIE Client Type as 13, so I assumed this and developed the initial part of the code I wanted to for an AIE exchange I was working on only later to learn that the qualification seemed to be failing only to learn that the reason was I was equating $CLIENT-TYPE$ for AIE to be 13 as it was 13 for EIE.. It apparently looks like the CLIENT-TYPE for AIE is 0 (Unknown).. Has anyone else encountered this?? Cheers Joe D'Souza No virus found in this outgoing message. Checked by AVG. Version: 7.5.519 / Virus Database: 269.21.8/1340 - Release Date: 3/23/2008 6:50 PM _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
