Good idea. I tried this, but it returned O as the client type, which is
really the client type returned whenever there is no client type.
Referencing the ar.h file:
/* client Id for an API program */
#define AR_CLIENT_TYPE_UNKNOWN 0
#define AR_CLIENT_TYPE_PRE_50 1 /* Pre 5.0 ar client
tools */
#define AR_CLIENT_TYPE_WAT 2 /* Windows admin tool
*/
#define AR_CLIENT_TYPE_WUT 3 /* Windows user tool
*/
#define AR_CLIENT_TYPE_WIP 4 /* Windows import tool
*/
#define AR_CLIENT_TYPE_DSO 5 /* Distributed server
*/
#define AR_CLIENT_TYPE_ODBC 6 /* ARODBC */
#define AR_CLIENT_TYPE_APPROVAL 7 /* Approval server */
#define AR_CLIENT_TYPE_WEB_SERVER 8 /* AR web server,
waserver */
#define AR_CLIENT_TYPE_MID_TIER 9 /* Mid-tier 5.0 and
later */
#define AR_CLIENT_TYPE_PALM_PILOT 10 /* Palm pilot */
#define AR_CLIENT_TYPE_FLASHBOARDS 11 /* Flashboards */
#define AR_CLIENT_TYPE_FLASHBOARDS_MID_TIER 12 /* Flashboards
mid-tier */
#define AR_CLIENT_TYPE_EIE 13 /* Enterprise
Integration */
/* Engine
*/
#define AR_CLIENT_TYPE_RELOAD 14 /* arreload */
#define AR_CLIENT_TYPE_CACHE 15 /* arcache */
#define AR_CLIENT_TYPE_DIST 16 /* ardist */
#define AR_CLIENT_TYPE_RUN_MACRO 17 /* runmacro */
.
.
.
.
.
So, it looks like that remedy cannot see the client-type of runmacro
when you are referencing it in a filter. I would try an active link, but
you cannot fire active links via run-macro, so I would not be able to
test to see if it could see it or not.
Thanks,
Gary Opela, Jr
Sr. Remedy Developer
Leader Communications, Inc.
405 736 3211
-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Garrison, Sean (Norcross)
Sent: Wednesday, January 23, 2008 2:52 PM
To: [email protected]
Subject: Re: Client-Type
Have you tried adding a note or error to see what the actual value of
client type is when the Run Macro is run? Worse case you will see it in
the arerror.log
Sean
-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Opela, Gary L Contr
OC-ALC/ITMA
Sent: Wednesday, January 23, 2008 2:32 PM
To: [email protected]
Subject: Re: Client-Type
Fixed:
I changed $CLIENT-TYPE$ = 17 to $CLIENT-TYPE$ != 3
I'm guessing that when you bypass the user tool to modify tickets, then
$Client-Type$ is not set, or at least runmacro doesn't know the
client-type, thereby it is $NULL$, which will evaluate to true in this
situation.
>From the User tool, it works fine. The filter does not fire because it
knows the Client Type is indeed 3.
Thanks,
Gary Opela, Jr
Sr. Remedy Developer
Leader Communications, Inc.
405 736 3211
-----Original Message-----
From: Opela, Gary L Contr OC-ALC/ITMA
Sent: Wednesday, January 23, 2008 1:27 PM
To: '[email protected]'
Subject: Client-Type
>From the Beginners Guide page 673:
"The client type of the API program. When used in workflow, this keyword
resolves to a number that corresponds to Remedy User, Remedy
Administrator, DSO, and so on.
The number representations of the different client types are in the ar.h
file,
which is located in <install_directory>\api\include. For example, if you
use
$CLIENT-TYPE$ in a Run If qualification for an active link, you can
cause the
active link to execute only for a mid-tier client (for example,
$CLIENT-TYPE$ = 9)."
I have found that, according to my ar.h file, the Client-Type for
runmacro.exe is 17. I have created a filter that runs only when
$CLIENT-TYPE$ = 17 to send a message.
Unfortunately, it is not running whenever runmacro.exe modifies the
ticket. The guide only mentions Active Links. Active Links are not fired
whenever runmacro.exe submits the ticket.
I need this workflow to only fire whenever runmacro modifies the ticket.
Can I still reference CLIENT-TYPE, or will I have to reference a
different keyword? According to everything I can see, the way I'm doing
it now should be working fine.
Thanks,
Gary Opela, Jr
Sr. Remedy Developer
Leader Communications, Inc.
405 736 3211
________________________________________________________________________
_______
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
________________________________________________________________________
_______
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
