Release 5.3 Private Cloud

Infinite Blue® Platform Version 5.3 Release Notes

Release Date

October 1st, 2018

Fixed Issues


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

Known Issues


  1. On an existing Platform 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.