INTRODUCTION

The alert configuration contains step to configure alerts for any event in the system. Alerts are configured against the pre configured activity event .Any alert is identified by 3 properties as follows:

• Activity Id: An identifier for the activity being performed .It is the combination of the fully qualified name for the class and the method name. For example: Request fund activity in the Wallet. The activity id would be “com.ofss.digx.app.wallet.service.core. Wallet.requestFunds”.
• Event Id: An identifier for the event occurred while performing the activity. An activity can have multiple events. It should start from the module name followed by the logical name for the event. For example: Request fund success is an event in the wallet module. The Event Id can be “WA_REQUEST_FUNDS_SUCCESS”.
• Action Id: An identifier for the action to be executed during event processing .The action can be of 3 types.
• Alerts: Raise a message alert for the specified destination type like EMAIL, SMS etc. This is the default action performed while alerts processing.
• Notifications: The notifications to be generated for the dashboard etc.
• Business Logic: Any business Logic to be performed while alerts processing.

The alert configuration contains following:

• Database Configuration
• API for Raising an Event
• Custom Fields for Push Notification
• Multi-Entity Specific Templates

Back