< All Bots

Configurable Event Handler

The Event Handler Bot provides an Enterprise-standard framework for definition of process events, & stakeholder notification.

Top Benefits

  • Event notification is configurable to avoid un-necessary hardcoding.
  • Helps enforce standardization of logging, event tracking, and notification.
  • Helps enforce comprehensive definition of Exceptions/Errors/Event for any Use Case.
  • Enables powerful insight by analyzing Errors, Exceptions, Events logged across processes/use cases

Tasks

  • Read event log populated by any automated process.
  • Read XML configuration and issue appropriate stakeholder notifications for the event.

A common property of all automations is that key ‘events’ may occur, that require specific action. This action is often logging the information for subsequent analysis, and notification. The Event Handler Bot supports Automation Anywhere’s Best Practices for Bot Development, by enabling this functionality in a way that is configurable – minimizing any need for ‘hard-coding’ the definition.
As we build Bots, there are a few problems that can arise, in particular as an organization scales in the volume of Use Cases, and people developing automations:

1. Lack of standards for notification – each person developing the Bot may adopt their own approach to tracking/sending notification
2. Hard-coding – actions and targeted recipients for communications may be hard-coded, requiring changes to code when these requirements change. Changes to a solution once deployed to Production introduce un-necessary risk, as changes could negatively impact the functionality.
3. Lack of Exception Definition/Handling – as the process for a Use Case is defined, there is often insufficient attention on the entire scope of potential process / system exceptions.

This EventHandler helps to address each of these challenges, as follows:

1. With the EventHandler, definition of notifications and required actions are defined using a standard approach across all processes/Use Cases
2. Rather than hard-coding, definition of ‘events’ and required actions are configurable via XML
3. Definition of ‘exceptions’ is embedded in an XML file, which could be defined early in the bot development lifecycle, and change to those definitions managed throughout the Bot’s lifecycle.

Get Bot

Free

Applications
Business Process
Category
Security
Passed third-party anti-virus scan conducted by Automation Anywhere.
Downloads
37
Vendor
Automation Type
Bot
Last Updated
December 2, 2019
First Published
November 21, 2019
Enterprise Version
10.5
Community Version
Not Supported
ReadMe
ReadMe
Support

See the Bot in Action

Event Log (CSV) Sample
Event Handling Sample #1
Event Handling Sample #2
Event Notification Sample
PREV NEXT
Event Log (CSV) Sample
Event Handling Sample #1
Event Handling Sample #2
Event Notification Sample

Setup Process

Install

Download the Bot and follow the instructions to install it in your AAE Control Room.

Configure

Open the Bot to configure your username and other settings the Bot will need (see the Installation Guide or ReadMe for details.)

Run

That's it - now the Bot is ready to get going!

Requirements and Inputs

  • EventHandling.XML (sample included)
  • EventLog CSV (sample included)