vConnect & IT Ops
Log Auditing Control for Scheduled Jobs to optimize logs storage
A new “Audit Enabled” flag has been introduced in the scheduled job configuration, defaulting to enabled. When enabled, all service logs executed within the job are audited; when disabled, only error logs are audited, which can help with optimizing log storage. The job-level “Audit Enabled” flag takes precedence over the similar service-level flag for services executed as part of the job, but does not affect service execution outside of a scheduled job.
More information can be found here.
Fig 1: “Audit Enabled” flag in Scheduled Job configuration
Record Identifier for ESB Runtime Logs for easier filtering in logs
Record Identifier will now also be logged for direct requests to the ESB Runtime (e.g., requests from Scheduler or Custom Java), in addition to API Gateway requests. This change enables easier filtering in Developer Logs by parameters usually used as Record Identifiers such as Lead ID or Opportunity ID.
Fig 2: Record Identifier captured for Scheduler run services
Thumbnail Support for Images in DMS for a better user experience
DMS can now generate dynamic thumbnails for uploaded images. Supported formats are JPG, JPEG, PNG, WEBP. It supports configurable thumbnail dimensions for images, allowing customization of length and width through VRT-level DMS settings. These thumbnails will be returned when fetching images from the DMS, improving the user experience.
Tech Debt
- Enable Vahana API Gateway to Call Java 17 and HTTPS Microservices – Vahana API Gateway now supports calling microservices which are upgraded to Java 17 and using HTTPS protocol.
- Removal of Vahana-app-server-gateway – Vahana-app-server-gateway microservice has been removed due to it being no longer required.
- ESB Code Optimization for Vahana 2.0 Apps – Reduced unnecessary overhead and improved system performance.
- Vulnerabilities addressed in VRT – Vulnerabilities were scanned for and addressed in VRT Java code.
Bug Fixes
- API/Service Name Duplication Support – Users can now duplicate an API or Service using the same name previously used for a deleted API or Service, resolving the issue where name duplication was not allowed.
- Monthly Report Data Availability in User & Device Analytics – Resolved an issue where no data was displayed in the ‘Monthly Report’ section in User & Device Analytics after successfully logging into the app.
- Corrected AM/PM Format for Event Logs – The AM/PM format for event logs has been corrected to ensure proper time display.
- New “fileExtensionType” Parameter in DMS – A new parameter, “fileExtensionType,” has been introduced for specifying the file extension type in DMS to address issues faced due to previously changed parameter mappings in DMS.
- Preserve Existing Parameter Value after changes in Database API Configuration – The issue where the existing parameter value was being reset after making changes in Database API configuration has been resolved. The parameter value is now preserved as expected.
- Update Button Visibility in Database API Edit – The issue where the update button was visible without any changes while editing a Database API has been fixed. The button will now only appear when changes are made.
- Event Manager Lag Fix – Lag in recording event data in case of large amounts of data, has been resolved to improve performance and responsiveness in the Event Manager.
- Logs Generated for API Gateway in case of Read Timeout from ESB – Logs will now be generated when the API Gateway encounters a read timeout from the ESB. The current read timeout is set to 60 seconds.
- Primary Key Value Fetching Update in vConnect – The primary key value, previously fetched from the transformed request object when an event is raised via a REST/SOAP API, will now be prioritized as follows: First, it will be retrieved from the original request object if the mapped parameter exists; if not, the system will fall back to fetching it from the transformed request object.
- DMS Fetch Issue for PDF files – Resolved issue where PDF file extension was not coming in pdf files fetched from DMS resulting in “Invalid File Extension” error message.