Release Notes

Release Date

May 2026

New Features & Enhancements

Following is the list of new features and enhancements with this release:

• The platform now incorporates granular permissions for Support Login and Login As functionalities, enabling administrators to regulate these capabilities independently based on user roles. This approach enforces the principle of least privilege, enhances security and auditability, and guarantees that impersonation access is granted without extending broader support-level privileges.

• The following improvements enhance Hazelcast Global Cache stability, scalability, and deployment flexibility:

  • Storage statistics data moved out of the global cache layer, reducing load and lightening the global cluster.

  • Cache maps and related platform flows were validated to ensure reliable behavior, improve consistency, and lower cache-related error risks in distributed environments.

• Native Comments now support more granular permission settings, enabling independent control of Create, Edit, Delete, and View privileges according to role or policy. This enhancement facilitates customers in permitting users to add comments while restricting modifications or deletions, thereby enhancing governance and audit compliance. Existing permission configurations remain fully backward compatible for customers who do not modify their policy settings.

Fixed Issues

Following is the list of fixed issues with this release:

Known Issues

Following is the list of known issues with this release:

Release Date

April 2026

New Features & Enhancements

Following is the list of new features and enhancements with this release:

• The Hazelcast Global Cache stats has been refactored to use lazy loading in replicated and distributed maps. All System Console screens now use primary-cache for building out information and optionally enrich them with runtime stats when available. Absence of stats information like number of customers, running status etc. on list of components or servers does not result in UI facing exception and is re-built silently on next periodic refresh of stats. This improves cache consistency, reduces memory use, and boosts system performance and reliability.

• Marketplace application update reliability has improved, focusing on hosted file management. Issues causing hosted file content loss during deployment are fixed, ensuring consistent behavior after updates. Additional logging increases visibility into hosted file processing and speeds troubleshooting.

• A new client-side metadata API - rbf_getviewdef() was introduced to retrieve complete view definition details for custom UI rendering. This enhancement provides access to view columns, filters, sorting, grouping, totals, and display rules, enabling dynamic and configuration-driven list views. It helps ensure custom UI components stay aligned with platform-defined view behavior. See rbf_getviewdef() for more information.

• The platform provides better visibility into partially locked items that customers modified and that no longer follow the upgrade path. A tenant-level view helps administrators review these items, while a master-level report shows upgrade delta across selected tenants, highlighting changes that may be skipped during an application update. See Modified Components for more information.

• Support was added for reviewing and managing customer-modified entities and attributes with change-tracking details, helping teams assess upgrade impact and reduce maintenance. Tenant Admins can now edit more Partial Lock field properties, including Currency Format, Phone Number Input Mask, Lookup Default Value, and Picklist import exclusions. See Fields for more information.

• Support for legacy SOAP-based third-party libraries was removed during platform modernization. The update replaces outdated dependencies with supported alternatives, improving security, maintainability, and compliance with current standards.

• The REST API session cleanup now manages session lifecycles after expiry more effectively. API key requests no longer create user sessions, reducing unnecessary sessions and improving platform efficiency. See logout for more information.

Fixed Issues

Following is the list of fixed issues with this release:

Known Issues

Following is the list of known issues with this release:

Release Date

March 2026

Fixed Issues

Following is the list of fixed issues with this release:

Known Issues

Following is the list of known issues with this release:

(Release Date

February 2026

New Features & Enhancements

Following is the list of new features and enhancements with this release:

• The Async Job Framework now supports asynchronous trigger execution with callback functions and structured response handling. It introduces a shared property controlling trigger execution delays. The EnableParallelEventProcessing property lets administrators choose if delayed triggers with the same definition run concurrently or sequentially. When enabled (the default), triggers run in parallel, limited by the DelayedTriggersExecutorThreadCount setting. When disabled, triggers run sequentially per definition.

• Enhanced rate-limiting capabilities for API endpoints have been introduced to provide greater control over API traffic and strengthen the platform. Administrators can now configure rate-limit profiles that specify the allowable number of requests per minute, hour, or day for each endpoint. The rate-limiting mechanism operates hierarchically. Initially, tenant-level profiles are evaluated (if enabled); otherwise, system-level profiles are applied. Requests are tracked within defined time intervals, and limits are enforced for each period to prevent excessive or malicious traffic. Administrative controls and backend validations ensure centralized and effective management of rate limits. For more information, Rate Limit.

• Transaction logging is enhanced to capture the originating server component and record event timestamps at the source, improving server attribution and time stamp precision for better traceability and correlation. Enabling transaction debug logging through the System Console outputs the transaction completion time in the customer's transaction log, aiding internal diagnostics.

• This release implements an update which optimizes job execution and connection management to reduce system load and improve platform stability. It also strengthens resource controls to prevent Too Many Connections errors common in high-traffic environments.

• The LCAP platform has been upgraded to support MySQL version 8.4.7, the latest Long Term Support release, thereby ensuring ongoing compatibility as MySQL 8.0 approaches its end of life. MySQL 8.4.7 offers extended support and enhanced long term stability, aligning with AWS deprecation schedules and securing the platform for future production deployments. Support for MySQL 8.0.44 will continue for existing environments.

Fixed Issues

Following is the list of fixed issues with this release:

Known Issues

Following is the list of known issues with this release:

Release Date

January 2026

New Features & Enhancements

Following is the list of new features and enhancements with this release:

• The following improvements were made to Hosted Files as part of the Partial Lock Framework MVP:

  • Introduced Partial Lock functionality to allow Super Admins to edit hosted files under Tenant Admin Permissions, even if they are marked as Not Allowed.

  • Tenant Admins remain restricted from editing components marked as Not Allowed.

  • Components disallowed by tenants are always upgraded from source to destination, regardless of modifications made by Super Admins.

• The following improvements were made to Fields as part of the Partial Lock Framework MVP:

  • Tenant Admins and Super Admins can edit Allowed fields (marked as Modified). Only Super Admins can edit Not Allowed fields. Tenant-allowed fields upgrade only when unmodified, while tenant-disallowed fields always upgrade. Parent/child field relationships remain unaffected by each other’s upgrade paths.

  • Both admin roles can view which fields are on or off the upgrade path and restore fields to the upgrade path as needed.

  • Phase 3 extends Partial Lock to additional field types, including Currency, Phone Number, URL, Password, Auto Number, Roll-Up Summary, Lookup/Related/Reference, and Picklist/Multi-Select/Dependent/Radio/Group-of-Checkboxes, as well as portal-specific fields like Captcha Image, Hidden Input, and IP Address.

• The following enhancements were made to strengthen platform security:

  • The System Console health check logic now validates node reachability and high-availability status, ensuring component health reflects real-time system conditions.

  • Component metadata and runtime information have been consolidated into a streamlined caching model, creating a single source of truth and enhancing consistency, maintainability, and scalability.

  • Logging behavior for recurring and delayed triggers has been refined to reduce excessive log entries, improving operational visibility and usability.

  • Internal processing for concurrent import jobs has been optimized to address CPU and memory spikes, resulting in improved system stability and resource utilization.

  • Additional security fixes and safeguards have been implemented to address vulnerabilities and strengthen overall platform resilience.

• The Lucene library has been upgraded to version 9.12.3 to improve indexing performance and search stability.

  Note: As part of this update, customers must perform a tenant-wide re-index to recreate all existing indexes for compatibility with the new version, ensuring optimized and reliable search operations across the platform. Below is a sample error message displayed if the tenant was not re-indexed after the Lucene upgrade.
  

Fixed Issues

Following is the list of fixed issues with this release:

Known Issues

Following is the list of known issues with this release:

Release Date

November 2025

New Features & Enhancements

Following is the list of new features and enhancements with this release:

• The following enhancements were introduced to extend the Partial Lock Framework consistently across Pages, Templates, and Fields, with component-specific behaviors noted where applicable:

  • Super Admins can edit both Allowed and Not Allowed components, with Allowed components flagged as Modified when changed.

  • Components or fields allowed by a tenant upgrade only when unmodified whereas Components or fields disallowed by a tenant always upgrade, regardless of Super Admin modifications.

  • For Pages specifically, changes to a component’s upgrade path do not affect its parent or child components. Additionally, adjustments were made to allow tab and section reordering within page containers while supporting Partial Lock behavior.

  • Partial Lock support now applies to a broad range of field types, including Text, Text Area, Checkbox, Numerical (Integer/Decimal), Percent, Date, Email, Integration Link, Version Number, File/Image Upload, Shared Image, and others as applicable. Likewise for Fields, field-level locking, consistent version control, and upgrade governance were introduced for all supported field types.

• The following updates were implemented as third-party library upgrades to enhance platform security, stability, and overall performance:

  • The core libraries supporting the SMTP Email Server and JSON communication framework were upgraded to the latest supported versions to ensure improved reliability and compliance with current standards.

  • The default Log4j2 configuration was updated to prevent Lucene Search from logging in DEBUG mode by default.

  • The runtime UI was enhanced to load the latest standalone jQuery version, resolving known security vulnerabilities and improving frontend resilience.

• The following enhancements were made to strengthen platform security:

  • Improved input validation and sanitization across key backend and frontend modules to prevent injection risks.

  • Resolved a few vulnerabilities in the search and filtering interfaces to enhance data protection.

  • Implemented additional safeguards and secure coding improvements to reinforce overall system resilience.

jQuery Library Upgrade
The jQuery library has been upgraded from version 1.12.0 to 3.7.0 to improve performance, security, and compatibility with modern web standards. Since some older methods are now deprecated, the jQuery Migrate plugin is temporarily included to maintain backward compatibility. Users are advised to update any deprecated methods in their custom scripts to supported ones, as the jQuery Migrate plugin will be removed in a future release and deprecated methods will no longer be supported.

Fixed Issues

Following is the list of fixed issues with this release:

Known Issues

Following is the list of known issues with this release:

Release Date

October 2025

New Features & Enhancements

Following is the list of new features and enhancements with this release:

• The following enhancements were made as part of the Partial Lock Framework across Pages, Tabs/Menus, Triggers, and Fields, providing improved control and consistency in component management.

  • Tenant Admins can edit components within their allowed permissions.

  • Super Admins retain full edit access, regardless of modification status.

  • Components allowed by tenants are upgraded only if unmodified.

  • Components disallowed by tenants are always upgraded, even if modified by Super Admins.

  • Upgrade path changes no longer affect parent or child components, ensuring stability and independence across upgrades.

  • The framework now supports reordering of tabs and sections within page containers, menus, and related components, aligning with the Partial Locking structure.

• This release includes updates to several third-party libraries primarily as security, stability, and compatibility improvements under these categories:

  • Password Strength

  • SFTP & FTP Batch Jobs

Fixed Issues

Following is the list of fixed issues with this release:

Known Issues

Following is the list of known issues with this release:

(This is the Drop-down text)Release Date

August 2025

New Features & Enhancements

Following is the list of new features and enhancements with this release:

• The following improvements were made as part of the Partial Lock Framework:

  • Tenant Admins are allowed to edit components under Tenant Admin Permissions if they are modified. Likewise, Super Admins can edit the components, even if they are modified.

  • Components allowed by the tenant are upgraded only if the components are not modified. However, components disallowed by the tenants are always upgraded, even if modified by the Super Admin.

  • Any changes to the component’s upgrade path do not impact its parent or child components.

  • Reordering of tabs and sections within page containers was adjusted to support the Partial Locking framework.

    For more information, refer Partial Locking.

Fixed Issues

Following is the list of fixed issues with this release:

Known Issues

Following is the list of known issues with this release:

Release Date

July 2025

New Features & Enhancements

Following is the list of new features and enhancements with this release:

1. The following fixes were implemented to improve CEM and Platform integration:

   • Resolved iFrame loading issues when accessing the Platform from CEM in multi-instance production environments.

   • Fixed compatibility issues with the navDisabled=true parameter for non-iFrame pages introduced in platform version 6.11.2.

2. The platform now supports PGP encryption by generating a public-private key pair at the instance level.

   • Tenant admins can download and share the public key, which end users must use to encrypt files before uploading them via SFTP.

   • During import, the platform detects encrypted files, retrieves the corresponding private key, and decrypts the content before processing, ensuring secure file transfer and data confidentiality.

     For more information, refer PGP Encryption.

3. The following enhancements were made as part of third-party library and integration updates:

   • Upgraded Google Integration library to the latest version.

   • Updated Hazelcast (caching layer) to version 5.3.x where the private cloud customers can use updated cluster-config-*.xml for better security.

4. This enhancement provides developers with more granular control over navigation by enabling specific page routing at the action level (New, Quick Create, Edit, and View) directly from list view settings. The following changes streamline user workflows and improve application adoption by giving developers precise control over user navigation paths.

   • List views now support configuration of target pages for New, Quick Create, Edit, and View actions using new dropdown picklists. These settings override object- or role-level defaults.

   • If navigation originates from a list view, the associated action uses the list view’s defined target page.

     For more information, refer List View Targets.

Fixed Issues

Following is the list of fixed issues with this release:

Known Issues

Following is the list of known issues with this release:

Release Date

June 2025

New Features & Enhancements

Following is the list of new features and enhancements with this release:

1. The following security enhancements were implemented as part of platform hardening during the maintenance release:

   • Removed deprecated MS Access import libraries to eliminate outdated components.

   • Removed unsupported test and sample applications identified as security risks.

   • Enabled the Secure flag for session cookies to ensure HTTPS-only transmission.

   • Set the HttpOnly flag on platform cookies to prevent client-side access and reduce XSS exposure.

2. Quick Create modals now support grid controls, offering functionality consistent with standard new/edit pages. These popups are now correctly aligned with their respective object types to ensure a seamless user experience. For more information, see Grid Control on a Quick Create Page.

3. Quick Create modals also support implicit relationship linking, ensuring related records are automatically associated without manual input, similar to the new/edit pages. For more information, see Implicit Relationship Linking on New and Quick Create Pages.

4. Users now have dedicated access to the BCIC Online Help, which differentiates between the Enterprise Application help and Infinite Blue Platform help. For more information, see Introduction to BC in the Cloud.

5. The upgrade process has been optimized to reduce time and manual intervention.

   • Administrators can now perform system backups for multiple customers at once through a new bulk action. Only authorized roles can initiate the backup, and the process runs asynchronously, adhering to existing processing limits. For more information, see Bulk System Backup for Multiple Customers.

   • A new bulk unload feature allows administrators to unload multiple customers from the master zone for support escalations or post-upgrade clearing. This process also runs asynchronously, ignores already unloaded tenants, and sends a completion email to the initiator. For more information, see Bulk Unloading of Multiple Customers.

6. The cloning functionality has been enhanced to allow the cloning of related records with unique text values. Administrators can now control the cloned values, making it easier and more efficient to create additional records while ensuring uniqueness where necessary. For more information, see rbv_api.getcloneRecord().

7. This release allows CEM users to view a pop-up of the related BCIC Location record directly from a CEM asset via an external ID without needing direct access to BCIC. This allows quick visibility into planning-related business impact.

8. Relationship cloning now supports records with unique fields by allowing users to control the cloned value for supported input types, preventing errors and improving efficiency when duplicating records. Supported unique fields include EmailInput, PhoneInput, IntInput, TextInput, and URLInput. For more information, see Cloning with Unique Fields.

Note: Customers using PostgreSQL should not upgrade to this version, as it is currently incompatible with PostgreSQL databases. Proceeding with the upgrade will result in database failures. It is strongly recommended to postpone the upgrade until a compatible version is released.

Fixed Issues

Following is the list of fixed issues with this release:

Known Issues

Following is the list of known issues with this release:

Release Date

March 2025

New Features & Enhancements

Following is the list of new features and enhancements with this release:

1. Admins can now perform nightly upgrades without being restricted by the MaxBackupsPerMonth limit. The platform will manage backups based on the MaxSystemBackups property, which controls the number of stored backups per customer. As part of this update, the MaxBackupsPerMonth shared property has been deprecated and removed from Shared Properties and the Customer object in master zone.

2. The third-party library is updated for JDBC to the latest version:

   • postgresql-42.7.5.jar

3. Introducing the navDisabled URL parameter, which enables a minimal view in Kendo UI by hiding navigation elements while preserving role-based permissions. Links open in a new tab with standard navigation, while platform buttons redirect within the same window. This applies only to Kendo UI. See Custom Blueprint for more information.

4. Updated System Info (OSHI) libraries to the latest version for improved performance and reliability.

5. Updated Smart Images libraries to optimize image minimization for improved UI performance.

6. The following libraries are removed due to the deprecation of Git Integration for XML Upload/Download:

   • jgit-5.11.0.202103091610r.jar

   • jgit.ssh.jsch-5.11.0.202103091610r.jar

   • jsch-0.1.55.jar

7. The third-party library is updated for Apache CSV Import/Export support to the following versions:

   • commons-csv: 1.13.0

   • commons-codec: 1.17.2

   • commons-io: 2.18.0

Fixed Issues

Following is the list of fixed issues with this release:

Known Issues

Following is the list of known issues with this release:

1. [Search Results] [Filter]: The keyword filter does not populate search results in the list view.

2. [Partial Locking]: The Unlocked option is not disabled in the Generate XML page for Partially Locked applications, as customers can currently generate an Unlocked application from a Partially Locked application.

3. [View] [Filter]: When applying a View Filter using the Formula dropdown, the Clear View Filter option is not visible in the Remove Filter button.

4. [View] [Page Designer]: When accessing a List View or Record View page from an iframe, selecting Design This Page incorrectly opens pageEdit.jsp within the same iframe instead of a new tab.

5. [Blueprint] [List View]: When navDisabled=true is set, users cannot detach records from a Related List View within the iframe.

Release Date

December 2024

Fixed Issues

Following is the list of fixed issues with this release:

Known Issues

Following is the list of known issues with this release:

1. [UI] [Jquery]: The codebase includes an outdated commented-out reference to the SP:NewUIMobileUsesJqueryMobileUI.

2. [List View] [Filters]: The record count in the list view does not update correctly when using any filter or Quick Filter Template.

   Work Around: Reload the page manually after applying filter

3. [ISV] [Help Menu]: The Help Menu items fail to populate for tenants with an ISV Partner user configured if the ISV Home Page and ISV Support URL are not set.

4. [Password] [Authentication]: The minimum length for a password field is incorrectly set to a hardcoded value of 6, ignoring both the user-defined value and the security level's minPasswordLength setting.

   Work Around: Keep portal password authentication profile's security level and customer security level in sync.

5. [Security] [Update]: Custom security levels are deleted after upgrading to any development build.

   Work Around: System admins should manually add new security level with distinct id and name for usability

6. [List View] [Filters]: When exporting the list view records asynchronously with quick filter enabled, the export includes all records instead of just the filtered records.

7. [Object Definition] [Reports]: During the application installation flow, retrieving the object definition ID from the Reports webpage returns a null value, causing interruptions.

   Work Around: Do not include report type page in the Partially Locked application before exporting

8. [XML] [Reports]: XML reports do not render correctly in preview mode on Chrome and Edge browsers.

   Work Around: Use firefox browser.

9. [Input] [Application]: The application does not securely handle all input, allowing unintended behaviours such as triggering a Print screen popup when malicious input is provided

10. [Email Templates] [Super Admin]: Unable to create email templates as the mailTemplEdit.jsp page is locked.

Release Date

November 2024

Fixed Issues

Following is the list of fixed issues with this release:

Known Issues

Following is the known issue with this release:

• [Relationships] [Portals]: No related line records are visible on the Portal, despite having View permission for the relationship..

Release Date

October 2024

Fixed Issues

Following is the list of fixed issues with this release:

Known Issues

Following is the known issue with this release:

• [Relationships] [Portals]: No related line records are visible on the Portal, despite having View permission for the relationship..

Release Date

August 2024

Fixed Issues

Following is the list of fixed issues with this release:

Known Issues

Following is the list of known issues with this release:

1. [Partial Locking] [Preferences]: The unlocked Object Type tab appears as non-editable (displayed as "PL" in appView.jsp) on the Partial Locking Preferences page.

   Work Around: On the subsequent application push, even if no changes were made to this tab, it automatically updates to an editable "UL" status. This brings it in line with the expected behavior in appView.jsp.

2. [Tabs/Sections] [Emojis]: Emojis are not retained in the Tab/Section help descriptions if the content consists solely of emojis or if an emoji is the final character.

   Work Around: Ensure that the help content does not contain an emoji as the only or last character.

3. [Buttons] [Integration Name]: Users can create multiple buttons with the same integration name, which conflicts with the requirement for unique names to retrieve button details through the API.

   Work Around: Ensure that each button is assigned a unique integration name to avoid issues with API data retrieval.

4. [REST 2.0] [Tomcat]: The REST 2.0 API fails to function if the Tomcat installation path contains spaces.

5. [Tabs] [Code]: Once a value has been assigned to a Tab code, it cannot be reset to null.

Release Date

May 2024

Fixed Issues

Following is the list of fixed issues with this release:

Known Issues

Following is the list of known issues with this release:

1. [Partial Lock] [Page Sections]: Partially locked page sections lose their property changes after any application upgrade.

2. [Partial Lock] [Super Admin]: In Fully Locked pages, the Super Admins are unable to add new sections or create any tabs.

Release Date

April 2024

Fixed Issues

Following is the list of fixed issues with this release:

Known Issues

Following is the list of known issues with this release:

1. [Partial Lock] [Picklist Field] - Customer's configured changes are lost for the Shared Picklist field values when the field is Partially Locked.

   Work Around: Reload the Destination Tenant cache before pushing the Partially Locked Application.

2. [Relationships] [System Objects] - Attaching records for M:1 cardinality via Server-Side API (rbv_api.attachRecord) sometimes still shows them unattached from UI.

   Work Around: The data set on UI would be fixed on page refresh.

3. [Partial Lock] [Settings/User Objects]: In the preference page, regardless of the application's overall lock status, settings and user objects which are marked as Unlocked, Fully Locked, or Partially Locked are treated as Unlocked.

Release Date

March 2024

Fixed Issues

Following is the list of fixed issues with this release:

Known Issues

Following is the known issue with this release:

1. [Partial Lock] [UI] - In the destination tenant, the attributes of the object coming from the source application may have their descriptions displayed in red.

Release Date

January 2024

Fixed Issues

Following is the list of fixed issues with this release:

Known Issues

Following is the list of known issues with this release:

1. [Partial Lock] [Picklist Field] - Customer customized changes are lost for the Shared Picklist field values when the field is partially locked in the second iteration (If the destination tenant follows this path: Unlocked -> Partially Locked -> Partially Locked).

   Work Around: Reload the destination tenant cache before pushing the Partially Locked Application.

2. [Partial Lock] [System Objects] - As settings and user objects do not support fully and partial locked states, these options fall back to unlocked in behavior.

Release Date

October 2023

Enhancement

Following is the enhancement with this release:

Partial Lock

Partial lock preferences is now introduced as a beta feature, where the users can now configure components using partial lock preferences. This feature provides options for Unlocked, Partially Locked, or Locked status for supported components, allowing for better security and confidentiality of sensitive code. However, please note that these enhancements are in the developmental stage and are not recommended for production use.

To access these settings, navigate to the More Actions menu on the Application Setup page and select Partial Lock Preferences. Remember to test these features in a controlled environment before implementing them.

For more information, see Partial Lock Preferences.

Fixed Issues

Following is the list of fixed issues with this release:

Known Issues

Following is the list of known issue with this release:

• [Partial Lock] - As of now settings and user objects do not completely support a fully locked status, thus this option should be disabled as this could be misleading. However, as per the functionality, it falls back to unlocked status. In fully locked application, these objects go with an unlocked status while in a partially locked application with object set to unlocked or fully locked, the objects are unlocked.

Release Date

September 2023

Fixed Issues

Following is the list of fixed issues with this release:

Known Issues

Following is the list of known issue with this release:

1. [Portal Fields] [IP Address] - If the IP Address field is read-only, it displays null or no value after saving the record.

   Work Around: To utilize the IP address field data, make sure the field is not set to read-only.

Release Date

August 2023

Fixed Issues

Following is the list of fixed issues with this release:

Known Issues

Following is the list of known issues with this release:

1. [Version Number] - The system information version number on the subscription page is displayed as 6.7.1.1 instead of 6.7.1.2.

Release Date

July 2023

Fixed Issues

Following is the list of fixed issues with this release:

Known Issues

Following is the list of known issues with this release:

1. [Picklists] - Any new customer/tenant space created between Platform version 6.7.0.0 to 6.7.1.1 may have a default system picklist created as part of customer creation like country, state, and country codes for phone number fields un-deployed by default. This would lead end-users of the application to see no options in the above picklist dropdown fields only while attempting to create or edit records.

   Workaround - The application administrator may edit the country or state picklist fields and enable deployed option on pick-items manually and save the field.

Release Date

July 2023

Fixed Issues

Following is the list of fixed issues with this release:

Enhancements

Following is the enhancement with this release:

Third-Party Library Updates

This release is also bundled with a significant enhancement to our third-party library which includes several upgraded libraries, including PostgreSQL, hsqldb, commons-net, commons-fileupload, REST v2.0, jQuery, and Bootstrap. These updates bring numerous benefits in terms of reliability, scalability, and performance. Furthermore, we have addressed any known issues by incorporating bug fixes and security patches for these third-party libraries. This upgrade is designed to provide our users with a more secure and stable environment, ultimately enhancing their overall experience.

The following table details each library updated version incorporated in this release.

Release Date

May 2023

Fixed Issues

Following is the list of fixed issues with this release:

Known Issues

Following is the list of known issues with this release:

1. [List View] [Relationships] - 'Use list view' lookup option in configureGrid3 jsp lists only default view when relationship is with default type of object.

Release Date

March 2023

Fixed Issues

Following is the list of fixed issues with this release:

Known Issues

Following is the list of known issues with this release:

1. [Object Types] [Record Creation] - Installing update to existing application with Allow record creation option disabled on Default Object Type will not clear existing data records on default object type. App developers may delete these records manually after application update.

2. [Notifications] [Templates] - There is no additional pop-up confirmation prompting the user on proceeding with save deletes duplicate templates when choose to clean up duplicate system templates from template actions.