You specify the several parameters for a custom action when you add or edit the action. The following parameters are not self-explanatory:
Note: After you create, save, and close a custom action, you can edit its parameters, except that you cannot change the Type field. To specify a different type for the action, copy and rename it. If you do so, update the related rule to trigger the renamed action.
Specifies the type of action to use. To disable a rule action, select DISABLED. Depending on the type you select, additional fields are exposed. The add icon can be used to add an event parameter to the field used for each action type.
Specifies a command to run.
Specifies the URL to post.
Specifies the Java Class and parameters to pass.
Note: For more information about available Java classes, see the Reference Guide.
Notifies users (typically administrators) about system activities not related to requests. Examples include the addition of new users or a new business unit, or a data mediation load.
Notifies stakeholders about a request and optionally includes request details.
The following parameters require explanation:
Include Request Details - Specifies whether to add the details of the request to the text of the message body in the request email.
Specify Yes to add these details or No to omit them.
Type – Applies only when you use the $pending_action_users_or_groups$ variable.
Specifies the Type: Request, Service, or Service Option.
This parameter retrieves the list of pending action users or groups applicable to the selected Type. This parameter also assigns the retrieved list to the $pending_action_users_or_groups$ variable.
Request ID – Specifies the ID (not the name) of the request, which must be a numeric value or variable.
Request Item ID – Applies only when the selected Type is Service or Service Option.
Specifies the ID of the subscription detail object, which must be a non-numeric value or variable. This value is used to retrieve the list of pending action users or groups applicable to the selected Type (Service or Service Option).
From Email – Specifies the email address from which to send request emails.
From Name – Specifies the name of the email address from which to send request emails.
Note: If you do not specify a value for From Email or From Name, the Catalog system assigns the following value: the value specified in the Catalog, Request Management configuration options of the business unit of the request.
To – Specifies one or more primary recipients for the email.
You can use specific email addresses, user IDs, and requested for user-related variables.
To send an email to specific users or groups automatically, specify the matching variables, as follows:
To specify more than one value, separate the entries with a semi-colon (;).
You can select these variables and other variables from the list that appears when you click the list icon next to the field.
CC – Specifies one or more CC recipients for the email.
Use the same syntax as the To field.
BCC – Specifies one or more BCC recipients for the email.
Use the same syntax as the To field.
Subject – Specifies the text for the subject of the email.
Message Body – Specifies the text for the message body of the email.
Note: A commonly used variable is $server_url$. You can optionally use it to direct the recipient to the request detail page.
Specifies the start request form (SRF) (for CA Process Automation) or process definition (for CA Workflow) to invoke.
Use the Find Start Request Form icon (for CA Process Automation) or Find Process Definitions icon (for CA Workflow).
Specify the parameter values for the SRF or process definition, if applicable.
Specifies a parameter to pass to Reservation Manager.
For details about this integration, see the Integration Guide.
Specifies whether the action runs asynchronously or synchronously.
Note: Administrators cannot set the order in which actions run.
Specifies the number of seconds the action must run before a user can cancel it.
A value of 0 means no timeout applies.
Multiple Values
For some events, some parameters can have multiple values. For these parameters, use a delimiter to separate multiple values. For each parameter that can have multiple values, you can specify the separator that is used when that event occurs. If the Multiple Values check box is selected, the rule action is executed for each value for the parameter indicated in the Parameter field.
Note: The only standard event with multiple values parameters is the Catalog Subscription Change event. This event provides multiple values for the $new_offerings$, $new_subscriptions$, $old_offerings$ and $old_subscriptions$ parameters. You can use multiple value parameters with custom events; However, the event posting logic must provide the multiple parameter values.
| Copyright © 2013 CA. All rights reserved. |
|