Release 5.11.0 Private Cloud
Infinite Blue®Platform Version 5.11.0 Release Notes
Release Date
October 2020
Fixed Issues
Following is the list of fixed issues with this release:
Support ID |
Bug ID |
Public Description |
---|---|---|
PTSP-1755, PTSP-1354 |
IB-10780 |
Administrative and user permissions are not getting updated while application updates. |
PTSP-1271, PTSP-1873 |
IB-10634 |
Administrative and user permissions at the role level are not getting updated while pushing application updates through the marketplace. |
PTSP-2063 |
IB-12464 |
Batch job invoking a delayed trigger is causing a lock wait timeout. |
PTSP-748, PTSP-16, PTSP-2079 |
IB-12213 |
Batch jobs are running intermittently for inactive tenants when the customer is loaded. |
PTSP-1678 |
IB-11611 |
Delayed triggers are not executed if the records are created through any data maintenance batch job. |
PTSP-1361, PTSP-1564 |
IB-10850 |
Error prompted while creating new tenants if the XML APP contains existing translations. |
PTSP-1825, PTSP-2044, PTSP-1380 |
IB-11892 |
Failure exceptions are thrown while attempting to serialize user records, which occurs in uncommon scenarios for specific user records related to unusually long preference data. |
PTSP-1349, PTSP-1380 |
IB-11169 |
Failure exceptions are thrown while attempting to serialize user records, which occurs in uncommon scenarios for specific user records related to unusually long preference data. |
PTSP-1720, PTSP-1900, PTSP-1689 |
IB-11585 |
ISV partner is unable to access their customer's logs even with valid permission. |
PTSP-1743 |
IB-11768 |
The customer list is not showing accurate results to the ISV partner while installing any published applications. |
PTSP-1084 |
IB-10574 |
The decimal configuration does not work for specific fields while exporting to xls/xlsx/csv file formats from the UI. |
PTSP-837 |
IB-10433 |
View integration name is mentioned as mandatory in edit mode when navigated from the records list view whereas it doesn't show as mandatory while it is navigated from the setup or object definition page. |
- |
IB-11424 |
While the View integration name is mentioned as mandatory, in the edit mode on navigating from the records list view, it has no validation. |
Known Issues
Following is the list of known issues with this release:
-
[Master Cache][Marketplace] - Push Updates button is disabled.
Work around: Refresh the master cache.
-
[Push Updates][Marketplace] - All user-defined object type entities are getting deleted in push updates flow when the user enables the override changes checkbox.
Work around: Un-check the ‘Override Changes’ checkbox during push update operation.
-
[Page Designer] - 'Use List View' property in
pageEdit.jsp
page is not working.Work around: Assign view in the user preferences.
-
[Views] - ‘Hide this View’ from View Selector property is not working when the view is the current.
Work around: Change the current view in view selector and update the previous view properties from the object definition view page.
-
[Embedded Quick Create] - In the
configEmbedQC.jsp
page, 'Component Name' is not a mandatory field. -
[Reports] - Context-specific Custom Reports on preview, edit and save prompts an error.
Work around: Edit the report from the object definition view page.
-
[Reports] - Cloning a document template report doesn't carry the template.
Work around: Upload the template file during the clone action.
-
[Batch Jobs] - Deleting an object type is not clearing up the batch job.
Work around: Delete those batch jobs manually.
-
[Grid Control] [IE11] - Unable to attach records from the Grid Control.
-
[Logging] - Search Engine logs are printed on the tomcat console.
-
[Nodeconfig.json] - Multiple folders mentioned for
FontDirs
key innodeconfig.json
is not being considered. -
Object Type Attribute (Beta feature):
-
Gauges debug formula shows only default records when the object type is enabled
-
Page Title should have an object type name in parentheses.
-
Unless you reload the page, updating record data with inline edit is not saved after navigating between the list views.
-
Object Type field value is exported as $DEFAULT instead of Default.
-
The Search Results page currently does not honor any object types.
-