runmacro.exe
) that can
be used to externally create a trouble ticket or operate on an
existing trouble ticket. This program can be called by a trouble
ticket submission script such as the examples shown below:
Example 1:
ExecPath="runmacro.exe -eSubmit AR -hg:\ProgramFiles\remedy" &_ " -p Node=' " & ' " -p MsgId=" &" -p Text=' &Text
Example 2:
WscriptEchoExecPath Set WshShell=WScriptCreateObject("WScript.Shell") RunError=Wsh.ShellRun(ExecPath,1, TRUE)Additionally, an ARS macro is required. In this example, it is
SubmitAR
, located in the macro default directory
c:\Program Files\remedy\arcmds
, that actually does the
job (runmacro only triggers the macro). We pass the message
attributes as macro parameters (marked by the -p options).
The macro itself may look like the example shown below (but this depends on the ARS form structure and how the trouble ticket entries are structured).
SubmitAR Set-schema:DemoHelpDesk localhost Submit: DemoHelp Desk_carrot|8=$MsgId$_100000000=$Text$_100000001=Demo_100000005_10000001 4=Software_100000038=Demo_100000039=Other_2=$-1$_7=0_100000006=0_100000013=0_ end
The AR will be submitted into the form DemoHelpDesk, and the parameters Text and MsgId will be used as initial values for the Short Description and Details fields.
<InstallDir>/examples/OvOW/MessageForwarding
.See the Remedy documentation for more details on how to use runmacro and how to create ARS macros.
Related Topics: