{"id":475,"date":"2013-12-09T12:38:52","date_gmt":"2013-12-09T12:38:52","guid":{"rendered":"https:\/\/www.kovair.com\/blog\/?p=475"},"modified":"2013-12-09T12:38:52","modified_gmt":"2013-12-09T12:38:52","slug":"enforcing-business-rules-of-a-project-through-kovair-event-driven-policies","status":"publish","type":"post","link":"https:\/\/www.kovair.com\/blogs\/enforcing-business-rules-of-a-project-through-kovair-event-driven-policies\/","title":{"rendered":"Enforcing Business Rules of a Project Through Kovair Event-Driven Policies"},"content":{"rendered":"

The basic prerequisites to drive a project towards success are optimized usage of time, and resources and reduction of human errors in the process. Kovair\u2019s Event Driven Policy<\/b> helps organizations to accomplish this by reducing manual intervention at various levels, thus minimizing the scope of human errors. This saves time by reducing the number of repetitive tasks done manually at various levels. Kovair\u2019s Event Driven Policy is an automated approach that ensures that based on certain events, actions will be performed by the application. We will take a look at how this is accomplished.<\/p>\n

Let us consider some business scenarios and see how we can use Kovair Event Driven Policy<\/b> in solving them.<\/p>\n

\u00a0<\/b>Scenario 1<\/b><\/p>\n

Create a Defect automatically and then link it to the specific Test Run which has failed in execution and has given rise to this Defect.<\/p>\n

\u00a0<\/b>Scenario 2<\/b><\/p>\n

Create a task for the Developer when a Bug is assigned to him for fixing and then notify him or her accordingly..<\/p>\n

To accomplish Scenario 1,<\/b> we specify the Event and the Action. The Event and the Test Run, while being modified, are specified along with the condition that the value of the Status field changes to \u201cFailed\u201d.<\/p>\n

We then go on to specify the corresponding Action, which is to create a new Defect, and then link it to the Test Run that is getting modified.<\/p>\n

For Scenario 2<\/b> we create two policies.<\/p>\n

    \n
  1. We specify the event that a bug is being modified and assigned to a developer. In addition, we also specify that the same developer will create a new task.<\/li>\n
  2. Once the event in which the task is created and assigned to the developer, we specify a corresponding action to notify the developer that the bug is being assigned. Such notifications can be sent to the developer via Email or SMS.<\/li>\n<\/ol>\n

    Thus, the power of the Kovair policy framework increases manifold with the use of relationship establishment between two records of two entities as explained in the above scenarios. Specifying the Event and Action in a Kovair policy is quite simple. The simple and interactive user interface allows the user to create a policy and specify Events and Actions to be performed in a few clicks.<\/p>\n

    Once the policy is created our desired rule is ready to execute. Thus even a complex business rule gets implemented in just a few clicks. Complex conditions can also be set up quite easily while defining a policy. Kovair addresses this by using another feature called the expression builder, in which complex expressions involving numbers and characters can be specified, accompanied by a vast range of inbuilt logical, arithmetic and string manipulation functions and operators.<\/p>\n

    \"The<\/b><\/p>\n

    Figure <\/span>3<\/span><\/strong>: The expression builder interface.<\/span><\/p>\n

    Besides the internal management of entities and records, Kovair policy can be made to invoke service calls which can be used to establish communication with external tools or web services. An example might be to trigger a build in Hudson, once a code file is checked into SVN from the Eclipse client.<\/p>\n

    Currently, Kovair Event Driven Policy supports 21 types of events and 15 types of actions. Each event may be used to execute one or more actions. Thus Kovair policy continues to be a highly popular feature among its users. It not only helps in the automation of business rules but also facilitates an integrated development environment by interacting with other tools and processes.<\/p>\n

    \n
    \n
    \n

    Request for Free Live Product Demo from our Engineers!<\/p>\n<\/div>\n

    Request FREE Demo<\/a><\/div>\n<\/div>\n<\/div>\n
    \r\n
    Related Posts<\/div>\r\n
    \r\n\r\n
    \r\n
    \r\n \r\n\r\n \"Data\r\n\r\n <\/a>\r\n <\/div>\r\n\r\n \r\n Data Validation Techniques for High-Stakes Financial Transfers <\/a>\r\n\r\n <\/div>\r\n
    \r\n
    \r\n \r\n\r\n \"Human-Centered\r\n\r\n <\/a>\r\n <\/div>\r\n\r\n \r\n Human-Centered Design vs AI-Generated Design: What Users Actually Prefer <\/a>\r\n\r\n <\/div>\r\n
    \r\n
    \r\n \r\n\r\n \"Security\r\n\r\n <\/a>\r\n <\/div>\r\n\r\n \r\n Security Considerations in Fintech Product Development <\/a>\r\n\r\n <\/div>\r\n \r\n <\/div>\r\n\r\n