Services

Release 4.5.3

Progress® Rollbase® Version 4.5.3 Release Notes

The following section describes issues fixed and enhancements done with this release.

  • For information on new features and changes in behavior, see here.
  • For information on supported platforms, see here.
  • For Third party acknowledgments see here.

Fixed Issues

Defect ID Case ID Description
72238 00401828 Some users were unable to open .pdf files from within Rollbase as the path separators were not properly handled.
72134 00401497 Pagination is disappearing when changing report filter criteria and reverting the changes
71621 00400378 Picklist search functionality for records with link lookup does not work.
71622 00400374 Clear All button in link lookup does not clear the displayed records and also shows some unrelated records.
71720 00399099 Nested delayed email trigger not getting queued when invoked from field update trigger.
70713 00398897 Users are encountering a 404 error on SOAP UI - Tool when trying to access SOAP end point.
71635 00397886 Conversion map for LDF enabled record with workflow action, the location field mapping is different in Old & New UI.
70951 00397644 Document Template stops rendering data for subsequent inner loops after fourth level.
70944 00393536 If objects in relationships are not part of core and dependent, an error is returned while generating an application.
70946 00386265 Revised Grid Control with Lookup having records in thousand slows down the rendering of edit page.
71092 Records viewed in applications with LDF permissions and related objects and view records in portal, do not adhere to LDF settings.

Enhancement

Enhanced Get Paged Data APIs: Rollbase 4.5.3 release offers an enhancement to getViewPage to improve the performance of API, JSON Format & Parameter Validation, better code readability and provides better information of fields & objects used as filters. The call structure is enhanced where each related object & filter parameter list is within a composite block, instead of comma separated object list in one argument.



Rollbase 4.4.4

Enhanced Hashing and Encryption Algorithms for Rollbase Private Cloud

SHA‐512 as Hashing Algorithm

Rollbase has upgraded its password hashing mechanism to SHA‐512. Each hashing process combines plain‐text password with random salt generated using cryptographically secure pseudo‐random number generator (CSPRNG). Existing passwords will be re‐hashed using SHA‐512 after user login.

Encryption Algorithm Private Key

Rollbase supports encryption for text, phone, and email fields, and contents of file upload fields. All these data are by default encrypted using AES (Advanced Encryption Standard) with 128‐bit key size.

When the system restarts after upgrading to 4.4.4, a private.key file that contains the secret key unique to your Rollbase instance is generated and saved in your Rollbase config folder on your master machine at <ROLLBASE_HOME>/config/security.

NOTE: Store a copy of the generated key in a secure place so that it is available for situations such as disaster recovery, or machine changes. This file is created and managed by Rollbase and should not be edited locally.

All fields currently encrypted using default encryption algorithm (AES‐128) will continue to function correctly. They will be decrypted and then re‐encrypted using your preferred algorithm and generated secret key the next time they are edited and saved.

AES‐256 Encryption Algorithm Support

Rollbase now also supports encrypting data using AES with 256‐bit key size. This is a system wide choice and managed through the shared property ‐ ‘EncryptionType’.

To make use of AES‐256 on a Rollbase Private Cloud:
  1. Set value of shared property ‘EncryptionType’ from 0 to 1. This is a one‐time setting. Once set to 1, reverting to 0 is not recommended. If no value is specified, ‘EncryptionType’ uses its default value, 0. No additional changes are required if you want to continue using AES‐128.
  2. Install Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files 8 to enable the 256‐bit Key Size used by AES‐256. For download and usage instructions, see here.

Note: If these JCE files are not installed and the property ‘EncryptionType’ is set to 1, encryption attempts will fail with the exception: Illegal Key Size.

Important: Support for unique constraint validation on encrypted fields has been deprecated. Thus, unique checks on encrypted fields will not work. Encrypted fields cannot be audited, marked unique or indexed as part of the search engine. Once set, this option cannot be removed.