Release 5.12.0 Private Cloud

Infinite Blue®Platform Version 5.12.0 Release Notes

Release Date

January 2021

Fixed Issues

Following is the list of fixed issues with this release:

Support ID

Bug ID

Public Description

PTSP-16

PTSP-748

PTSP-2079

IB-12213

Batch jobs are getting invoked intermittently for inactive tenants.
PTSP-1926 IB-12259 Explanation of behavior for visibility of detach button is missing for Orphan records controls options.

PTSP-988

PTSP-2239

 IB-12600 Frequent bulk update jobs cause the platform to submit many duplicate re-index jobs in the queue.

PTSP-2063

PTSP-2227

 IB-12464

Invoking setFieldValue method within Data Maintenance Batch job, causing lock wait timeout.

PTSP-1976

PTSP-2160

 IB-12403

REST API Logout not terminating the session in case of the JWT token used for authentication.

PTSP-604

PTSP-1405

PTSP-1620

 IB-9985 Tabular report export hangs if the export button clicked multiple times in sequence.

PTSP-1753

PTSP-1768

PTSP-2158

 IB-11769 The expression field is not assigned to a new field during marketplace push updates.
PTSP-2189 IB-9769 The expression field is not holding values after the Push Update if there is any conflict in the db column names for any other field.
PTSP-2224 IB-12844 The rbv_api.sendHttpRequest API is not supporting the PATCH method.

Known Issues

Following is the list of known issues with this release:

  1. [Server-Side API][RESTv2.0] - Unable to update same record using invokeSystemRESTV2 Server-Side API in ‘After Create’ Trigger.

  2. [Server-Side API][RESTv2.0] - Validate Formula in the Template Helper section commits all the RESTv2.0 API calls while validation.

  3. [Server-Side API][RESTv2.0] - Post Customer Create Script for invokeSystemRESTV2 API does not function.

    Workaround: While creating a customer, if an application is attached, and the application has an expression field with the method invokeSystemRESTV2 used and attached in seed records, then an exception 'Unauthorized access or user session is not available' is thrown and so the customer creation fails. To handle this exception, the customer must use try-catch blocks in the expression field.

  4. [Dedicated Tables] - Application updates won't honor incoming dedicated attribute over already installed, existing object definitions marked non-dedicated.

    Workaround: Tenant admins may move any shared object definition to dedicated table later manually

  5. [Dedicated Tables][MySQL] - Unsuccessful 'Move to dedicated table' operation may leave orphan dedicated table schemas over MySQL databases.

    Workaround: Administrator can manually drop dedicated table schema from MySQL database before attempting Move to dedicated table job again over same object definition.