SR-C93555 · Issue 431598
BulkMover updated to not treat Numerics as strings
Resolved in Pega Version 8.3
When attempting to update Pega platform 8.1.1 to 8.1.3 with Oracle on a Windows machine with German locale using the out-of-place upgrade of the rules schema, the migration failed at the migration step with the error message "ORA-01722: Ungültige Zahl". This was traced to BulkMover failing when trying to convert a string to a Numeric due to the locale using commas as the decimal separator, and has been resolved by updating BulkMover to not treat Numerics as strings.
SR-C87757 · Issue 431643
Country Code for Austria saved correctly
Resolved in Pega Version 8.3
When trying to save an address with CountryCode=AT, the code was saved as "at" instead. This was caused by a temporary field value not being correctly cleared, and has been resolved.
SR-C86138 · Issue 431775
Security updates for avatar upload function
Resolved in Pega Version 8.3
Updates have been made to enhance security around the avatar upload function.
SR-C79017 · Issue 431816
Metadatatree updated to be function-scoped in UI to resolve custom tab control display issue
Resolved in Pega Version 8.3
When switching rapidly between two custom tabs, especially clicking in and then clicking away before the busy icon could be displayed, the section containing the tab controls was intermittently refusing to display. Refreshing the browser or clicking on the Pega button made the section visible again. This was traced to the template "metadatatree" getting overlapped with subsequent template processing due to a timing issue as "metadatatree" was being maintained in the global window object. To resolve this, "metadatatree" has been updated to be function-scoped in renderUI to avoid timing issues.
SR-C89954 · Issue 431930
Rule-Connect-SOAP error fixed for WAS/JBOSS environments
Resolved in Pega Version 8.3
After upgrade, SOAP webservice was failing with the error “Couldn't create OMElement from string value for the activity InvokeAxis2 in class Rule-Connect-SOAP". This occurred on sites using a WebSphere/JBoss environment, and was traced to an issue where the WAS classloader was loading its default jar at the same time the Pega classloader was loading the same jar into JVM. This has been resolved.
SR-C89716 · Issue 431990
Rule-Connect-SOAP error fixed for WAS/JBOSS environments
Resolved in Pega Version 8.3
After upgrade, SOAP webservice was failing with the error “Couldn't create OMElement from string value for the activity InvokeAxis2 in class Rule-Connect-SOAP". This occurred on sites using a WebSphere/JBoss environment, and was traced to an issue where the WAS classloader was loading its default jar at the same time the Pega classloader was loading the same jar into JVM. This has been resolved.
SR-C89677 · Issue 432537
Optimation added for Oracle queries
Resolved in Pega Version 8.3
Certain versions of Oracle may suffer from sporadic poor performance with all_constraints queries. To alleviate this, Pega has been updated to provide some processing optimization where possible in the TableInformationMapImpl function. Additional timing alert and debugging logic has also been added in this class for all platforms, especially for lookupForeignKey.
SR-C87463 · Issue 432613
Required image replacing Mandatory Asterisk displays correctly
Resolved in Pega Version 8.3
After creating a mandatory text input field in a section and uploading the required image in place of the default image, the previous default image was still displayed in the portal even after clearing the browser cache and /temp folder on the app server. This was caused by the CSS rule 'pzbase-div-layouts' using specific selectors that had a hard-coded content hash for the image, which has been corrected.
SR-C92060 · Issue 432775
Null check added to resolve issue with manipulating operator access group list
Resolved in Pega Version 8.3
When using an operator access group list where there were multiple access groups already listed, picking any one of them except the last and clicking '+' (Add item) to create new line item or clicking on the delete icon to delete the row was generating a Pega busy indicator which never resolved. This was traced to the value label.prop("tagName") being returned as undefined, and has been resolved by adding a null check.
SR-C94047 · Issue 432967
Updated Static Progress Bar Control to resolve parse error
Resolved in Pega Version 8.3
When configured in a section with no parameters, the Static Progress Bar control was refreshing every second. After 5-10 seconds, a parse error appeared. This has been resolved by updating the value of bUseProcess to check for both string and boolean.