FileGPS 6.3.3.1 Release Notes
This release introduces IANN FileGPS version 6.3.3.1, delivering a more standardized, stable, secure, and feature-rich experience. Building on the core capabilities of earlier versions, this update includes key enhancements in alerting, performance, security, and integration flexibility.
Upgrading to version 6.3.3.1 introduces several functional changes. While most features are backward compatible, certain enhancements may require configuration validation and testing to ensure a smooth transition and full utilization of new capabilities.
| Area | Impact |
|---|---|
| Tomcat Upgrade (9.0.82 → 10.1.36) | May require revalidation of connectors and TLS configurations. Ensure compatibility with OS-level dependencies and service wrappers. |
| Datasource Password Resolution | New flexible resolution order: Command line → Env variable → YML file. Update your deployment scripts or environment variables accordingly. |
| Feature | Impact & Required Action |
|---|---|
| Favicon Configuration | New optional property favicon: true/false. The default is true. No change needed unless customization is required. |
Summary:
A new configuration property has been introduced to control favicon (browser tab icon) behavior. This enhancement allows teams to customize the favicon or disable it entirely based on deployment needs.
Configuration Details:
Application.yml
filegps:
favicon: true # default is true
When favicon: true (default):
The application will load a favicon from an external path (outside the JAR) if present.
You can override the default icon by placing a custom favicon in a designated directory name icon with the following specs:
📏 Resolution: 32×32 pixels
🧾 MIME Type: image/x-icon
📁 File Extension: .ico
📦 Recommended Size: ≤ 5.55 KB
🎨 Bit Depth: 32-bit
When favicon: false:
The application will not load any favicon, resulting in no icon being shown in the browser tab.
Use Case:
Enables branding flexibility by allowing deployments to use custom favicons without modifying the application JAR.
Suitable for white-labeled environments or minimal UI setups.
Impact:
Backward compatible.
Default behavior remains unchanged (true).
The Maintenance Window for Alerts feature allows administrators to define specific time periods during which alerts are temporarily suppressed across various modules, including:
This ensures that planned maintenance activities such as system updates, batch process reruns, or network-level changes do not trigger false or unnecessary alerts, thereby avoiding alert fatigue and maintaining clarity for operational teams.
The Retention Policy with Purge Option introduces advanced data lifecycle management capabilities, enabling organizations to control how long operational and transactional data is retained within the IANN FileGPS system. In addition to scheduled purging of outdated data, the system now supports archiving purged records into a secondary storage table (either within the same or a different database), helping meet regulatory, compliance, and audit requirements.
Benefits Summary
✅ Reduces database size and improves system efficiency.
✅ Ensures compliance with enterprise data retention and deletion policies.
✅ Provides a secure fallback mechanism for recovering purged records.
✅ Enhances audit and traceability controls without retaining stale data in operational workflows.
The File Not Received (FNR) Alert is a critical monitoring mechanism in IANN FileGPS that detects and notifies when expected files are not received within a configured time window or frequency. This ensures early identification of data transfer issues, system integration failures, or upstream processing delays.
The Improved Alert Traceability feature enhances the visibility, auditability, and diagnostics of alerts triggered within the FileGPS platform. In this release, alert records are enriched with comprehensive metadata, making it easier for users, administrators, and support teams to:
What’s Included in the Enhanced Alert Details
When an alert (such as FNR, TNR, SLA breach, Agent Down, etc.) is triggered, the system now captures and displays the following details on the UI and in alert logs:
| Field | Description |
|---|---|
| Email Subject | The actual subject line sent in alert email notifications. |
| Email Body | The complete body content of the email sent, including dynamic parameters like file name, alert time, etc. |
| API URL / Endpoint | The URL of the external system endpoint (e.g., SNOW API, webhook) where the alert was posted. |
| Incident Service Used | The integration service responsible for triggering incidents (e.g., SNOW, Webhook, PagerDuty). |
| Response Code | The HTTP status code received from the API call (e.g., 200 OK, 500 Internal Server Error). |
| Response Message | The message returned by the external system (e.g., Incident Created, Authentication Failed). |
| Request Payload | The exact JSON or XML payload sent to the external system, including parameters like incident title, description, timestamp, priority, etc. |
Summary: The application now supports reading the encrypted datasource password (spring.datasource.fgks) from multiple sources, improving flexibility in deployment and environment configuration.
Key Enhancements & Fixes
Most changes are non-breaking and backward compatible. Default behaviors are preserved unless explicitly overridden in configuration. However, validation and reconfiguration are recommended to fully leverage new features and avoid misconfigurations.
📩 Support & Contact Information
For any questions, clarifications, or further discussions related to this release, please reach out to the Pragma Support Team:
📧 Email: techsupport@pragmaedge.com
🌐 Website: www.pragmaedge.com