Filter Phases for on Submit,Merge,Modify

Version 1
    Share This:

    An Overview

     

    ·         Remedy-AR System Work Flow Objects -Introduction

    ·         Filter Phases for on Submit and On Merge Actions

    ·         Filter Phases for on Modify Action

    ·         Filter Phases for on Get Entry Action

    ·         Filter Phases for on Delete Action

     

     

    Remedy-AR System Work Flow Objects -Introduction

     

    In AR System, form is an AR System object which is used to capture and display the information. The information captured in the forms will be processed by Remedy workflow objects before storing it in the database.

     

    AR System has following three types of work flow objects to implement the Business Logic:

     

    1. Active Links
    2. Filters
    3. Escalations

    Active Links:

     

    An active link is an action or a series of actions that are being triggered when a user performs an operation, based on the set of permissions assigned to that user. The action(s) is triggered on the AR System client (either web or Windows) in the current form window.

     

    Filters:

     

    Filters are meant to implement and enforce business rules because they test every request transaction to see if certain conditions

    are met, and then respond to the conditions by taking specific actions. These filters are executed for all the transactions occur in the Database. Filters will run from the Server. So Administrator permission is defined for the Filters.

     

    Escalations:

     

    An escalation enables a condition to be checked on a regular basis or time bound basis and, depending on if and how it is met, performs one or more actions. Escalations differ from filters in that escalations occur at a specific point on a time interval rather than in response to a specific operation. Escalations will run from the Server. So Administrator permission is defined for the Filters.

     

     


    Here we are going to discuss about the processing of Filter in the AR Server.

     

    As we already discussed, Filter Object executes on the Server with Administrator permission. So whenever the following actions are made, the filter objects are executed:

    • Submit
    • Modify
    • Delete
    • Get entry
    • Merge

     

     

    If any one of the action is triggered for a Request, then all the filter for the corresponding execute on condition will be executed. While executing these filters, they will be executed based on the execution order. But the actions present may not be executed sequentially as Active link or in escalation actions.

     

    The actions present in the Filters are classified under the following three categories:

    • Phase 1
    • Phase 2
    • Phase 3

     

    The following table shows actions that are processed under each phase:

     

     

    Phase 1

    Phase 2

    Phase 3

    Call Guide

    Exit Guide

    GoTo

    Go To Guide Label

    Log to File

    Message

    Set Fields

    Push Fields

    Direct SQL

     

    Notify

    Run Process

    Distributed Server Option

     



     

    This implementation is meant for ensuring that notifications are sent and that processes are run only after the database operations are successful. If any database operation fails, all subsequent actions are suppressed, and database changes are rolled back. So, the system defers to a final phase the operations that should not run until database transactions have been committed and there is no chance that a rollback will occur.

    The subsequent section will detail the order in which the filter actions are executed in more detail.

     

    Filter Phases for on Submit and On Merge Action

     

    When the On submit or On merge execute action is triggered, the filter actions are executed in the following procedure:

     

    • First all the phase 1 actions in all the filters executed.
    • A new entry in created in the Database with created record committed into the data base.
    • All the Phase 2 Actions are executed.
    • Then at last Phase 3 actions are executed.

     

    Here if there are any errors in any one of the phase 2 actions, then all the phase 2 actions will be rolled back. Then the created record will be deleted from the data base.

     

    If any phase 2 action triggers any more transactions such as CREATE or MODIFY subsequently, the phase 2 action will not be committed until all the phase 1 and phase 2 actions are completed. If there are any errors in these, the transaction is rolled back and created entry is deleted from the data base.

     

    The same principle applies to On Merge Option also.

     

    Filter Phases for on Modify Action

     

    When the On Modify execute action is triggered, the filter actions are executed in the following procedure:

     

    • First all the phase 1 actions in all the filters executed.
    • All the Phase 2 Actions are executed.
    • Entries are modified into the database(committed)
    • Phase 3 actions are executed at last.

     

    Here if there are any errors in any one of the phase 2 actions, then all the phase 2 actions will be rolled back.

     

    If any phase 2 action triggers any CREATE transactions subsequently, the phase 2 action will not be committed until all the phase 1 and phase 2 actions are completed. If there are any errors in these, the transaction is rolled back and created entries are deleted from the data base.

     

    Filter Phases for on Get Entry Action

     

    When the On Get Entry execute action is triggered, the filter actions are executed in the following procedure:

     

    • Data is Retrieved from the database
    • All the Phase 1 and phase 3 Actions are executed.
    • Phase 2 actions are executed at last.

     

    Here if there are any errors in any one of the phase 2 actions, then all the phase 2 actions will be rolled back. But by the time the Notification would have been sent. So be careful in using this option.

     

    For getEntry operations, there is generally no database change, so the actions are not be phased.

     

    Filter Phases for on Delete Action

     

    When the On Delete execute action is triggered, the filter actions are executed in the following procedure:

     

    • All the Phase 1 and phase 3 Actions are executed.
    • Phase 2 actions are executed at last.
    • Request is deleted from the Database.

     

    Here if there are any errors in any one of the phase 2 actions, then all the phase 2 actions will be rolled back. But by the time the Notification would have been sent. So be careful in using this option.

     

    Rakesh Jajper

    Vyomlabs Pvt. Ltd.