This documentation supports the 20.02 version of Remedy Action Request (AR) System.

To view an earlier version, select the version from the Product version menu.


Creating filters

Filter execution options cause the filter to execute based on actions that occur on the BMC Remedy AR System server for requests in the reference form.

If a filter is part of a guide, you do not need to select an execution option. If an action generates an error during the processing of a filter, no further actions occur.

To define the execution options for filters

  1. Open an existing filter or create a new one.
  2. Make sure there is an associated form selected, or select one in the Associated Forms panel if necessary. See Associating workflow objects with forms.
  3. Expand the Execution Options panel.
  4. Set the State field to Enabled or Disabled.
    When the state is Enabled, the filter becomes active as soon as it is saved. You might want to set the state to Disabled during development or when troubleshooting.
  5. If necessary, enter a number in the Execution Order field.
    The value that you enter in the Execution Order field determines the order in which this filter is executed relative to other filters with the same triggering conditions. Numbers between 0 and 1000 are valid execution order values; lower numbers are processed first. The default value for filters is 500.

    Note

    Although filters are processed in execution order, some filter actions are queued up to be performed at a later time. For information about filter phases, see Filter processing in BMC Remedy AR System server.

  6. Select the filter execution options, if any.
    Filter execution options are described in the following table. You can select any combination of these execution conditions, or none of them, as appropriate. If you select multiple options, the active link or filter executes when any one of the selected operations occurs.

    Filter execution options

    Execution optionDescription
    ModifyExecutes when a request is modified.
    SubmitExecutes when a request is submitted to the server.
    DeleteExecutes when a request is deleted.
    Get EntryExecutes when a request is retrieved.
    Merge

    Executes when a request is merged into the database by using BMC Remedy Data Import, a DSO independent copy transfer, or the data import command line interface. For more information, see:

    Service

    Executes when a Service active link, filter, or escalation action is performed. 

    The filter accesses a request with the field values passed by the active link, the filter, or the escalation action and those retrieved from the database, if any, and returns output values to the calling request. No other database operation is performed. If the filter runs a Push Fields action, the output field value list is 
    not affected. If the filter runs a Set Fields action, the output field value list uses any modified values. 

    For more information, see Service action.

  7. Expand a Run If Qualification panel, and enter a qualification, if needed.
    For more information, see Building qualifications and expressions.
  8. Expand the Error Handler panel, and complete the fields as needed.
    For more information, see Error processing.
  9. Enter If and Else actions as needed.
    For more information, see If Actions and Else Actions .
  10. Save the filter.
Was this page helpful? Yes No Submitting... Thank you

Comments

  1. Mykola Slutskyi

    If necessary, enter a number in the Execution Order field. The value that you enter in the Execution Order field determines the order in which this filter is executed relative to other filters with the same triggering conditions. Numbers between 0 and 1000 are valid execution order values; lower numbers are processed first. The default value for filters is 500.

    What if several filters have the same value of 'Execution Order' field? Will their sequence of execution be determined by other rule, or they executed in random sequence then?

    Jun 15, 2021 08:54