Setting Event Action Parameters
There are two basic ways you can set parameters for an event action:
- Use the event action parameter
forms associated with each action type.
To access these forms, select an Action Type and then click on the Event Actions form.
- Specify the parameters directly in the text edit field on the Event Actions form.
You can also begin with the event action parameter forms and then manually edit the output in the Event Actions form. You can also begin by directly entering starting parameters in the text edit field on the Event Actions form and then adjust the input using the event action parameter forms.
Tips and Guidelines for Using the Event Action Parameter Forms Effectively
While the event action parameter forms make it easier to set event action parameters than creating them manually, you must still be somewhat familiar with the parameters, functions, and syntax available for each action type. Probably, the best way to do this is to open the form associated with each action type and access the online Help for that form and its fields.
Each event action parameter form includes only those parameters and functions that will work for the selected action type. So, for example, if you are creating an action to notify recipients of something, only the parameters you might need to create that notification are available from the Event Action Notify form.
Most options on an event action parameter form include both a field and a button. The field might be any of these types:
- A text edit field into which you can directly enter the value for that option.
- A drop-down list from which you can select the value you want.
- A combo box that allows you to either select a value from a drop-down list or enter the value manually.
The associated button typically opens either of these forms:
- The Event Action Expression Editor, which is a generic form used to create desired values using expressions.
- Another auxiliary event
action parameter form specifically designed to help with the creation of an
appropriate value for that option.
For example, the Event Action Parameter Condition form, which is designed specifically to make it easier to create and format an appropriate condition statement for the application event system to use.
button on many event action parameter forms opens the
When you click
in the event action parameter form, the values you specified are returned to the parent form, formatted using the correct syntax.To verify the syntax is error-free, click the
button before you proceed.Example
As part of an application event that notifies a manager when a customer's credit limit has been changed, you want to prompt a Credit Manager for approval if the new credit limit is $500,000 or less. If the new credit limit is more than $500,000, then the Credit Supervisor must approve the change. You could use a Branch action type to determine who gets the prompt message.
To handle this situation, you must perform these steps:
- On the Event Handlers form, create an event handler that runs every time a customer's credit is changed.
- Click .
- On the Event Actions form, specify the action sequence number and select the Branch action type.
- Click .
- On the Event Action Branch form, click .
- On the Event Action Parameter Condition form, click .
- On the Event Action Expression Editor form, select the PROPERTY function and specify CreditLimit as the first argument.
- Click .
- In the > (greater than) symbol. field, select the
- In the 500000. field, specify
- Click .
- In the Event Action Branch > Destination field, perform these actions:
-
If the target action sequence step exists, select the number of the action sequence step you want the handler to go to.
-
If the target action sequence step does not exist, specify the number of the step that you plan to create for the target later.
-
- Click .
- On the Event Actions form, click to verify that
the parameter syntax is all correct.
If there is an error, an error message is displayed. You can use this error message to determine what and where the error appears and the preceding context. In many cases, such as this one, you must have the property name in quotation marks, or the system returns an error. In fact, missing quotation marks are the most common cause of syntax errors.
If this happens, try to correct the error manually and then click
again. Keep doing this until you have eliminated any errors.Caution:If you do not correct any syntax errors before you clickagain, you will lose all parameter text and need to start over. - Click .