Did You Know?

FileGPS 6.3.3.1 Release Notes 

Contents -
Features and Enhancements:
1. The Tomcat version has been upgraded
2. Maintenance Window for Alerts
3. Retention Policy with Purge Option
4. File Not Received (FNR) Alert with Count Conditions
5. Multi-File Pattern Support for FNR Alerts
6. Transaction Not Received (TNR) Alert with Count Conditions
7. Rest Consumer changes
8. Alert Name Text Limit Changes
9. FNR and TNR Window Configuration
10. SNOW Integration with FileGPS
11. FileGPS Alerts Traceability
12. Improvement in Performance – Resolved Timeout Errors

This document outlines the release notes for FileGPS Product version 6.3.3.1. In addition to the default FileGPS features introduced in previous versions, this release includes the following features and enhancements to ensure a more standardized, stable, bug-free, and improved version. 

Features and Enhancements:

1. The Tomcat version has been upgraded

from 9.0.82 to 10.1.36 to address all vulnerabilities and align with security standards.

2. Maintenance Window for Alerts

  • Allows users to pause active alerts (FNR, TNR, SLA, Subscription, etc.) during scheduled maintenance. 
  • Prevents unnecessary notifications by temporarily disabling alert checks. 
  • It ensures smooth operations during planned downtime. 

3. Retention Policy with Purge Option

  • Users can configure Retention Policies to define how long data should be retained in the database. 
  • New Purge Option: When enabled, data deleted by the retention policy is stored in another table (same DB or another DB) for future reference. 
  • Provides better control over data lifecycle and compliance. 

4. File Not Received (FNR) Alert with Count Conditions

  • The FNR alert notifies users when expected files are not received. 
  • New Count Conditions allow more precise alert configurations: 
    • Less Than – Alert if file count ≥ expected count. 
    • Less Than or Equal To – Alert if file count > expected count. 
    • Equal To – Alert if file count ≠ expected count. 
    • Greater Than – Alert if file count ≤ expected count. 
    • Greater Than or Equal To – Alert if file count < expected count. 
  • Enhances flexibility in monitoring file transfers.

5. Multi-File Pattern Support for FNR Alerts

  • Previously, users could configure only one file pattern per FNR alert. 
  • Now, users can configure multiple file patterns within a single alert. 

6. Transaction Not Received (TNR) Alert with Count Conditions

  • The TNR alert notifies users when expected transaction count is not met as per configured count. 
  • New Count Conditions allow more precise alert configurations: 
    • Less Than – Alert if file count ≥ expected count. 
    • Less Than or Equal To – Alert if file count > expected count. 
    • Equal To – Alert if file count ≠ expected count. 
    • Greater Than – Alert if file count ≤ expected count. 
    • Greater Than or Equal To – Alert if file count < expected count.

7. Rest Consumer changes

  • Rest Consumer is a component designed to interact with RESTful web services, enabling efficient communication and data exchange between systems. It acts as a client that sends requests to REST APIs and processes the responses, facilitating integration with various web services. 
  • Features of Rest Consumer: 
    • Basic Authentication: Supports basic authentication to ensure secure access to REST APIs, protecting sensitive data during communication. 
    • SSL Integration: Implements SSL (Secure Sockets Layer) to encrypt data transmitted between the client and server, enhancing security and preventing unauthorized access. 
    • Flexible Configuration: Allows customization of request headers, parameters, and payloads to meet specific integration requirements. 
    • Error Handling: Provides robust error handling mechanisms to manage and respond to various HTTP status codes and exceptions. 

8. Alert Name Text Limit Changes

  • Extended Text Limit: The alert name text limit has been increased from 100 characters to 200 characters. 
  • Enhanced Flexibility: This change allows for more descriptive and detailed alert names, improving clarity and usability. 

9. FNR and TNR Window Configuration

  • Extended Time Window: The configurable time window for FNR (File Not Received) and TNR (Transaction Not Received) alerts has been extended from 15 minutes to 30 minutes. 
  • Flexible Configuration: Users can now set the alert window to either 15 minutes or 30 minutes, providing greater flexibility in monitoring and alerting. 

10. SNOW Integration with FileGPS

  • Enhanced Integration: SNOW integration with FileGPS has been improved to support seamless API integration. 
  • Customizable Alert Parameters: Users can now add SNOW-supported API details directly in the FileGPS alert creation body using the $ symbol followed by key=value. 
  • Simplified Configuration: This enhancement allows for easier customization of alert parameters, streamlining the integration process. 

11. FileGPS Alerts Traceability

We have updated the alerts screen to provide full traceability of API and email alerts. The update includes the addition of the email subject and body, API URL, incident service used, API response code, API response status message, and API payload. 

12. Improvement in Performance – Resolved Timeout Errors

We’ve enhanced the application’s performance by addressing timeout and latency issues in the File Search and Reports modules, particularly when handling large data volumes. Additionally, we’ve introduced a Retention with Purge feature that can now be managed through a straightforward configuration, as outlined in this document.