About setting application event action parameters

There are two basic ways you can set parameters for an application event action:

  • Use the event action parameter forms associated with each action type.

    To access these forms, select an Action Type and then click Edit Parameters on the Event Actions form.

  • Specify the parameters directly in the text edit field on the Event Actions form.

You can 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 adjusting the input using the event action parameter forms.

Note:  If you are familiar with the parameters, functions, and syntax for the action parameters, you can manually enter the parameter information in the text field. However, unless you are very confident in your ability to write this data from scratch or you are pasting in data from a reliable source, and to help ensure that you use only valid parameters, functions, and syntax, we recommend that you use the event action parameter forms, which have been designed specifically for this purpose.

Tips and guidelines for using the event action parameter forms effectively

While the event action parameter forms make it easier to set application 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 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 Condition button on many event action parameter forms opens 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.

When you click OK in the event action parameter form, the values you specified are returned to the parent form, formatted using the correct syntax.

To verify that the syntax is error-free, click the Check Syntax 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 would perform these steps:

  1. On the Event Handlers form, create an event handler that runs every time a customer's credit is changed.
  2. Click Event Actions.
  3. On the Event Actions form, specify the action sequence number and select the Branch action type.
  4. Click Edit Parameters.
  5. On the Event Action Branch form, click Condition.
  6. On the Event Action Parameter Condition form, click Expression 1.
  7. On the Event Action Expression Editor form, select the PROPERTY function and specify CreditLimit as the first argument.
  8. Click OK.
  9. Back on the Event Action Parameter Condition form, from the Operator drop-down list, select the > (greater than) symbol.
  10. In the Expression 2 field, specify 500000.
  11. Click OK.
  12. Back on the Event Action Branch form, in the Destination field, perform one of 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.
  13. Click OK.
  14. Back on the Event Actions form, click Check Syntax to verify that the parameter syntax is all correct.

    If there is an error, an error message displays. 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 Check Syntax again. Keep doing this until you have eliminated any errors.

    Caution: 
    If you do not correct any syntax errors before you click Edit Parameters again, you will lose all parameter text and need to start over.
  15. Click Save.
Related topics