Release 5.3 Private Cloud

Progress® Rollbase® Version 5.3 Release Notes

Release Date 

October 1st, 2018

  • For information on new features and changes in behavior, see here.
  • For information on supported platforms, see here.
  • For Third party acknowledgments, refer product documentation or the installation directory.

Fixed Issues

Following is the list of issues fixed with this release.

Case ID Defect ID Description
00338188 RB-1187 Lookup selector does not return records when typing only 3 letters
00409420 RB-1999 Field flagged as unique is allowing non-unique values
00416462 RB-1814 When updating a record WITHOUT USING THE UI; expression fields are not getting updated.
00416997 RB-2061 Filter criteria cleared on save of Filter condition if List View is edited from the Edit action in the View Selector.
00417827 RB-2059 Detailed search with Expression field is not working as expected.
00419354 RB-2075 Resetting the size of textfields to default by clearing the value on Page Designer New/Edit page not working.
00432212 RB-2159 Unique field combination issue when running batchjobs
00434965 RB-2213 Shared values set as part of triggers are not available to triggers downs the line.
00435197 RB-2204 Page does not show after clicking the edit page
00437989 RB-8203 Column Header misaligned when resizing columns
00438078 RB-7217 Hide Label Field Attribute on Portal page is not working
00441032 RB-7771 Mainlookup/ Linklookup are not work in grid control
00441550 RB-7515 Tabular section custom field header is not shown on the exported report.
00441556 RB-7516 Decimal points specification on a formula field is not being honored in the exported report
00445174 RB-7784 Submitting the page on Portal after session timeout throws an exception instead of proper error message.
00445566 RB-7797 Percent field in Grid doesn't show zero as a value after save.
00447214 RB-7970 Duplicated relationship records getting created in RB_Relationship table.
00448333 RB-8027 While performing user search getting the maxClauseCount error.
00448955 RB-8288 Type-ahead causes LDF filter to not be honored when creating record on LDF-enabled object.
00449424 RB-8093 Rollbase system console have "InactiveSessionExpireMins" and "LoginSessionExpireMins" deprecated shared properties in UI
00452442 RB-8305 Data maintenance utility performance slow down working with huge number of relationship records (~49 million)
00455779 RB-8477 Generic Tab with layout of Charts on the side by side and list view below these charts cause list view controls misalignment.
00458527 RB-7404 Permission Issue querying $LOGIN object
RB-1109 Expression fields in Filters and Grid row coloring do not work correctly
RB-1926 List view filters doesn't provide filter option for TextArea field
RB-7531 Custom login page does not redirect to RT field
RB-8238 Clicking on "Clear Filter" not clearing the filters fields
RB-8363 Duplicated records created in RB_Translation table when a record is updated after the customer is reloaded

Known Issues

  1. On an existing Rollbase setups, in case if any user encounters "Error: no column assigned to Expression field Installation Expression" while updating records from Published Application, the workaround is to convert the expression field to 'formula' and then back to 'expression'. (This error should never occur in a fresh setup)
  2. MySQL Connector/J 8.0 is now recommended for MySQL 8.0. A notable change is that the driver’s class name has been changed from com.mysql.jdbc.Driver to com.mysql.cj.jdbc.Driver. With MySQL Connector/J 8.0, although the older class name is supported, it is advised to update the class name for existing databases.
  3. MySQL JDBC driver (8.0) drivers may affect Date/Time field values.  If any errors are encountered during Tomcat startup, please refer to this article. A date/time field may retain the current/correct date, but the time component might show a future time (such as 1:42 PM instead of the current time of 8:42 AM). The driver now expects an additional parameter ‘serverTimezone’ in the connection URL.
  4. Primary keys are now added to RB_RELATIONSHIP and RB_TRANSLATION tables. While executing the update_5.3.0.sql script if either or both of these tables contain any duplicate records, Duplicate entry / Primary Key Constraint Violation errors will be seen. To resolve such errors, please follow the approach detailed in article.
  5. For OpenEdge and Oracle databases, login names are now case insensitive. If more than one user with the same login name exists, regardless of case, the user may fail to login. In this event, the login name entries need to be fixed manually in the database. For other databases, the login name is already case insensitive.
  6. In REST APIs, newly introduced shared properties UseISODateFormatInRESTJSON and UseISODateFormatInRESTXMLQuery are enabled by default. As a result, Date, Date/Time fields (including Expression and Formula fields whose return type is Date or Date/Time) return the values in ISO format. To fallback to earlier behavior, these properties need to be disabled explicitly.

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.