1. Home
  2. Getting Started
  3. Alert Management

Alert Management

In Alert Management, the user can configure the alerts based on his requirement. 

Path: 

Login   >   Dashboard    >  Alert Management 

User can create and manage alerts to track the transmissions of the files to a particular hub. Alerts are categorized into multiple subcategories 

  • SLA Alert 
  • File-Not-Receive Alert 
  • Subscription Alert 
  • Manage Alert 

 SLA Alert:

Service Level Agreement Alert can be configured by the user based on the requirement of the time ranges and percentages. 

Path: 

Login   >   Dashboard   >    Alert Management  >    SLA Alert 

In SLA Alert, user can create SLA’s/KPI’s for required Clients or files by committing conditions against the time ranges and percentages. 

The prerequisite in order to configure the Alert is, corresponding SLA should be created 

 

For example, In the below scenario Fig 1, the user has set an alert ‘ACME-Below Yellow-SLA Alert’ condition based on a percentage to the SLA named ‘Client Based ACME Percentage SLA’. 

 

Figure 1: Create SLA Alert 

Property  Description  Format 
SLA/ KPI Name  Agreement Name   
Description  of agreement   
Client Name  Name of Created/existing Client   
Client ID  ID of Created/existing Client   
Type of SLA  Whether it is FNR, SLA, etc.,   
Is Correlation SLA  Based on the direction of file   
Start value  Value at the beginning of the process   
End Value  Value at the end of the process   
Color Picker value  #value of the color (yellow, red, Green)   
ADD SLA  Creates SLA   
Cancel  Clears the values in input fields   

 

Figure 2: On Successful creation of SLA Alert 

 

For example, In the above ACME-BelowYellowSLAAlert’ where the ‘ClientBased-ACME-Percentage-SLA’ matches the below yellow condition value then an alert notification is raised as shown below in filegps dashboard. 

Figure 3:  SLA Alert view  

 

File Not received (FNR) Alert :

 In the File Transfer process, if a file is not yet started, in other words, if the event state start was not found then ‘FNR’ alert will be raised. This alert let the business team know that the file has not received for the client.

Path: 

Login   >   Dashboard  >     Alert Management    >  File not received 

In the below figure 4 user has configured the FNR Alert ‘ACME Client Not received Files FNR Alert’  

 

                                Figure 4: Create an FNR Alert

 

Property  Description 
Alert Name  Created/Existing Alert Name 
Description  FNR Alert Description Info 
Client Name  Created/Existing Client Name 
Client ID  Created/Existing Client ID 
File Name  Name of the file in the process 
File Pattern  File expression pattern  
File Count  Number of files passed the process 
Frequency of Occurrence  Time interval when occurred 
Start Date  Start Date of the file Processed 
End Date  End Date of the file Processed 
Notification Frequency  Notification occurrence at regular intervals 
Alert Content  Description of the alert and its content 
Priority   Level of importance given to alert 
Subject   Regarding the alert  
Body  miscellaneous 
Notification  To inform  
Recipient  Receive  
Email  Email of the client 
Create   Creates alerts 
Cancel  Clears values in input values 

 

After successful creation of FNR Alert, all the pages will be redirected to manage alerts screen with a success message. 

Figure 5On Successful creation of FNR Alert

 Subscription Alert :

Subscription Alert will be raised when a user subscribes to a particular event in the file transfer process and a file matches to a particular subscription. 

Path: 

Login   >   Dashboard   >    Alert Management    >  Subscription Alert  

In the below, figure 6 user has configured the Subscription Alert ACME Client received Start Subscription Alert to receive notifications on a particular file match. 

  

                                 Figure 6: Create Subscription Alert

 

Property  Description 
Alert Name  Subscription alert name 
Description  Subscription alert information 
Client Name  Created/existing Client name 
Client ID  Created/existing Client ID 
File Name  File name of subscription alert 
File Type  File extension 
File Count  Number of files created 
Timing  Yearly, monthly & daily, etc., 
Expected Time  Time at which the alert is expected to be  

notified 

Frequency of Occurrence  The occurrence of notification at regular intervals 
Start Date  Alert start date 
End Date  Alert End Date 
Alert Content  Description 

 

Figure 7 refers to the successful creation of a subscription alert 

Figure 7: Successful Creation of Subscription Alert

 

Property  Description 
Client Name   Created/Existing Client Name 
Client ID  Created/Existing Client ID 
Alert Type  Type of the alert either FNR/SLA etc. 
Alert Name  Name of the alert created 
Priority  To assign as per the importance 
Search  Shows Result set with a list of records 
Reset Search  Clear the values of input fields 

 

For example, In the above created ACME Client received Start Subscription Alert where the ACME Client receives the start files then the alert notification is raised as shown below in filegps dashboard 

 

                                         Figure 8: Subscription Alert view

 

 File Load Alert:

File load alert is raised whenever a file is processed from one node to other file load alert will raise with success status if the file is transmitted in the prescribed time. Else File load alert is raised with a failure status. In either of the cases, file load alert notifies the user on the file transmission. 

Path: 

Login  >    Dashboard   >    Alert Management   >   File Load Alert   

File load alert can be configured either on the client base and file base 

Creation of Client-based FLA: 

In the below figure 9, the user has configured the File Load Alert ACME Client File Load Success Alert’ for the ACME Client. 

                                     

                              Figure 9: Create Client based File Load Alert  

 

Alert Name  File Load alert name 
Description  File Load alert information 
Client Name  Created/existing Client name 
Client ID  Created/existing Client ID 
File Name  File name of subscription alert 
Configuration  File based/Client based 
Condition  Success/failure condition 
Alert Content  Description 
Subject/Body  Subject and body description 
Email  Email of the user 

 

Figure 10 refers to the successful creation of a File Load Alert 

 

Figure 10: On Successful Creation of File Load Alert 

 

Creation of File-based FLA: 

In the below figure 11, the user has configured the File Load Alert ‘%ACME% File-Based File Load Failure Alert’ for the ACME Client. 

 

Figure 11: Create File-based File Load Alert 

Figure 12 refers to the successful creation of a File Load Alert 

 

Figure 12: On Successful Creation of File Load Alert 

 

Manage Alert: 

In Manage Alert, User can search for the Alerts based on the filters that were provided at the time of Alerts creation. 

 

Path: 

Login   >   Dashboard   >    Alert Management   >   Manage Alert   

User have edit/delete/View Activity options to perform on alerts. 

All the actions such as edit/delete/View Activity could be performed when the user clicks on the particular record as shown in figure  

 

Figure 13: Manage Alert  

 

‘EDIT’ option is used to edit the Alert details. For example consider FNR Alert created previously, By clicking on the edit option, the page will be navigated to create page module where we can change details as per requirement. 

‘Update’ button, after making the required changes, the application will update the Alert details as shown in figure 14 

 

Figure 14: On Successful updation of FNR Alert  

View Activity’ will have the record of all the actions performed by the users as shown in figure  15. 

 

Figure 15: On Clicking Activity of FNR Alert 

 

Alert record could be permanently deleted with ‘DELETE’ option as shown in below figure 16. 

 

Figure 16: On Successful deletion of FNR Alert  

 

Updated on March 4, 2020

Was this article helpful?

Related Articles

Leave a Comment