Filters

In BMC Remedy, Filters are server-side workflow objects that automate actions based on specific conditions. They are integral to BMC Remedy's ability to process and manage data dynamically. Filters are triggered by database operations and can execute actions like updating fields, sending notifications, or performing escalations.

Key Features of Filters:

1. Execution Context:

   • Filters are triggered during Create, Modify, or Delete operations on forms.
   • They operate server-side, ensuring actions are performed regardless of the client interface.

2. Workflow Logic:

   • Filters consist of three parts:
     1. Qualification: A condition that determines whether the filter should run.
     2. Actions: Tasks executed when the qualification evaluates to true. For example:
        • Field updates
        • Push field actions
        • Notifications
        • Calling a guide or process
     3. Error Handling: Controls what happens if the filter encounters errors.

3. Execution Order:

   • Filters are assigned execution order numbers (0–1000).
   • Filters with lower numbers execute first, enabling precise workflow control.

4. Phases of Execution:

   • Filters execute in three distinct phases:
     1. Phase 1: Perform basic operations, such as validation.
     2. Phase 2: Perform more complex actions, like data manipulation and push field actions.
     3. Phase 3: Handle notifications and other post-transaction operations.

5. Performance:

   • Filters are efficient and do not rely on user interfaces, making them ideal for back-end processing.

6. Global and Form-Specific:

   • Filters can apply to specific forms or globally across the system, depending on their design.

Use Cases:

• Data Validation: Automatically validate data before saving.
• Field Updates: Update fields in the same form or in related forms.
• Notifications: Send alerts or emails to users or groups based on conditions.
• Process Automation: Push data between forms or invoke external processes.
• Error Handling: Reject invalid entries with meaningful error messages.

Filters are powerful tools in BMC Remedy, enabling developers to implement robust, automated workflows tailored to specific business needs.

Filter Phasing in BMC Remedy refers to the sequence in which filters are executed during database transactions. Filters are processed in three distinct phases, each serving a specific purpose in the workflow. This mechanism ensures that operations are executed in a structured and predictable order.

The Three Phases of Filter Execution:
1. Phase 1: Before the Database Operation

• Purpose: Pre-validation and preparation.
• Actions Allowed:
  • Validating user inputs and system conditions.
  • Performing checks to ensure the operation can proceed (e.g., field value validation).
• Impact:
  • Filters in this phase can halt the operation if their qualifications fail or trigger error messages.
  • Data changes made here are not yet committed to the database.
• Example Use Case: Ensure a mandatory field has a valid value before saving a record.

2. Phase 2: After the Database Operation

• Purpose: Post-commit data manipulation and further processing.
• Actions Allowed:
  • Updating additional fields in the current form.
  • Triggering workflows that depend on committed data.
  • Performing actions like Push Fields or Set Fields.
• Impact:
  • Filters in this phase act on data that has already been saved to the database.
  • They allow for subsequent operations that depend on the successful database transaction.
• Example Use Case: Automatically calculate and update a derived field after saving a record.

3. Phase 3: After Commit Actions

• Purpose: Non-critical operations that don't impact the database transaction.
• Actions Allowed:
  • Sending email notifications or alerts.
  • Logging events or updates.
  • Triggering external processes or integrations.
• Impact:
  • Actions in this phase do not affect the transaction's success or failure.
  • They are typically asynchronous to avoid delaying the transaction.
• Example Use Case: Send a notification email to a support team after a ticket is created.

Key Points to Remember:

1. Execution Order:

   • Filters are executed in ascending order of their Execution Order Number (0–1000) within each phase.
   • Filters with the same execution order number are executed in the order they were created.

2. Rollback Mechanism:

   • If an error occurs during Phase 1 or Phase 2, the entire transaction, including actions from earlier phases, is rolled back.
   • Actions in Phase 3 are not rolled back as they occur post-commit.

3. Dependencies:

   • Filters can use data updated in previous phases but cannot access data updated in subsequent phases.

Example Scenario:

• A user submits a form to create a service request.
  • Phase 1: Validate required fields and ensure the requester has the appropriate permissions.
  • Phase 2: Save the service request to the database, then calculate and update a priority field based on the urgency and impact values.
  • Phase 3: Send a notification email to the assigned support group about the new service request.

This structured approach ensures reliable and efficient workflow execution in BMC Remedy.