Filter Guides

In BMC Remedy, Filter Guides are objects that allow you to execute a series of filters in a specific order, similar to how Active Link Guides work for active links. However, Filter Guides operate on the server side and are used to process workflows related to server-side events, such as data manipulation, during different phases of a filter's execution.

Key Characteristics of Filter Guides:

1. Execution Scope:

   • Filter Guides operate on server-side events such as Submit, Modify, or Delete operations.

2. Triggering Context:

   • They are triggered during filter execution in response to specific events.

3. Reusability:

   • A single Filter Guide can be reused across multiple forms, making it efficient for managing repetitive workflows.

4. Sequential Execution:

   • Filters included in a Filter Guide are executed sequentially, maintaining the order defined in the guide.

5. Condition Checking:

   • Each filter in the guide evaluates its own conditions. Only those filters with satisfied conditions are executed.

6. Phases:

   • Filter Guides execute within the standard filter execution phases (Phase 1: Execute, Phase 2: If Actions, Phase 3: Else Actions).

7. Loops:

   • Unlike Active Link Guides, Filter Guides do not support loops or branching.

Use Cases for Filter Guides:

• Implementing server-side workflows involving multiple filters.
• Performing a sequence of data validations or transformations.
• Ensuring consistent and reusable processing logic across multiple forms.

Example Workflow:

1. A user submits a ticket through a form.
2. The Filter Guide is triggered during the Submit event.
3. The guide processes a series of filters to:
   • Validate the input data.
   • Auto-populate certain fields based on predefined logic.
   • Notify relevant stakeholders.
4. The ticket is then saved into the database with the processed data.

Benefits of Filter Guides:

• Simplified Maintenance: Reduces duplication of logic by centralizing workflows.
• Consistency: Ensures the same logic is applied across forms.
• Efficiency: Optimized for server-side execution, which is faster and less prone to user-side interruptions.

Would you like a specific example or more details about how to create and use filter Guides?