The CA Process Automation Remedy connector uses the Remedy* variable to send data to BMC Remedy for creating a ticket. When defining custom fields, you use the Remedy* variable, which is a copy of the BMC Remedy parameters. The CreateRemedyTicket process creates its own copy of the Remedy* variable when the process is triggered to pass information to BMC Remedy. The asterisk in the variable corresponds to HelpDesk or ITSM, depending on the version of BMC Remedy that you are using.
Note: The Remedy* variable is only accessible when using the CreateRemedyTicket process. For more information, including source code examples, see Add Custom JavaScript (Add Custom JavaScript, Add Custom JavaScript).
The Remedy* variable is a ValueMap data type variable that consists of a group of variables, each describing a BMC Remedy ticket attribute. You access each element in the ValueMap using the dot (.) operator. When used in source code, the elements of a Remedy* variable are accessible using the format Remedy*.variableName. For example, to reference the (non-ITIL) BMC Remedy HelpDesk site, you would use RemedyHelpDesk.Site.
Note: The fully qualified reference is Process.RemedyHelpDesk.variableName, but RemedyHelpDesk.variableName is acceptable.
The following BMC Remedy ticket attributes are available. Each item represents variableName in Remedy*.variableName:
CA Process Automation also provides a listing of these values. For more information about displaying these values, see View BMC Remedy Parameters (View BMC Remedy Parameters, View HP Service Manager Parameters) and How to Display a CA SOI Alert Instance (Display a CA SOI Alert Instance, Display a CA SOI Alert Instance).
For more information about using the Remedy* variable in custom source code, see Add Custom JavaScript (Add Custom JavaScript, Add Custom JavaScript). For more information about CA Process Automation development practices, see the CA Process Automation User Guide.
|
Copyright © 2013 CA.
All rights reserved.
|
|