INC-182572 · Issue 663555
Support added for multiple host proxy architecture
Resolved in Pega Version 8.5.5
When using an architecture where certain types of users were sent through multiple proxy servers to get the Pega Cloud instance, an exception was generated at the point of accessing the environment. This was traced to the use of Apache 2.4 with mod_proxy. As the request passed through each proxy, the x-forwarded-host header had values appended to it by mod_proxy which resulted in the error "com.pega.pegarules.pub.context.PRSecurityException: Multiple host names in header X-forwarded-Host". This has been resolved by updating the code to support using a multiple host proxy configuration.
INC-184668 · Issue 665956
Check added for null mColumn values while estimating size
Resolved in Pega Version 8.5.5
A null pointer error indicating an issue with AbstractDataPageHandler.estimateDataSize was traced to missing handling for null values in mColumns while calculating size. This has been resolved with the addition of a null check.
INC-160485 · Issue 655296
Trailing "/" added to public links for SSO use
Resolved in Pega Version 8.5.5
Links generated using pyWorkLinkWithLabel were not working with SSO due to not having a trailing "/" on the URL. This has been corrected by adding code to append the "/" if the public link url doesn't end with it.
INC-167139 · Issue 658620
Functions are packaged with "--" suffix
Resolved in Pega Version 8.5.5
Validation rules were not executed as expected. Investigation showed this was caused by functions referenced in the validate rule through a function alias being packaged without the "--" suffix (for example isNameInvalid--(String) was packaged as isNameInvalid). This has been corrected.
INC-168290 · Issue 663426
Signature Accept callback fires correctly in offline app
Resolved in Pega Version 8.5.5
Clicking on the Accept button in the Pega mobile signature control was not properly calling the necessary pega.ui.signature.acceptSignatureCallback method. This has been resolved by adding code for the Post Success and Failure callback on Signature accept in the offline app.
INC-172124 · Issue 651291
Improved Operator ID selection in Mobile Logs Retrieval section
Resolved in Pega Version 8.5.5
Data-Admin-Operator-ID.pzOperatorsByApplication returns only the first 500 operators, which is insufficient for large-scale use. There was a workaround of turning off paging for this report definition and setting maximum records to a bigger value, but this caused potential performance issues when opening very large users list. To resolve this, an autocomplete control will now be used to select Operator ID in the Retrieve Device Logs section of Mobile Channel. When part of an operator ID is typed into this control, the first 100 best results are shown and may be selected.
INC-172315 · Issue 652602
Resolved intermittent attachment save error
Resolved in Pega Version 8.5.5
A Flow Action error was intermittently being displayed when saving attachments. This was traced to the activity pzUploadAttachmentToDocument-->Step 25 which uses the step page CallExtensionAct which can cause a page null exception if it is not initialized, and has been resolved by adding a Page-New step to initialize the page.
INC-175000 · Issue 657005
Handling added for Address Map control in Microsoft Internet Explorer 11
Resolved in Pega Version 8.5.5
Microsoft Internet Explorer 11 does not support Class, async, await and arrowed functions due to not implementing the necessary EC6 features. This caused Address Map Control to not work in this browser because pypega_map_googlegis js creates a js class. To resolve this issue, alternate methods have been added for use with Microsoft Internet Explorer 11.
INC-175684 · Issue 658696
Parameterized data pages updated on record change
Resolved in Pega Version 8.5.5
Changing source data page records without changing the parameter value was not updating parametrized data pages. This has been resolved by updating the system so the parametrized data page populator function is now called every time the page is accessed.
INC-179175 · Issue 665173
Mobile barcode scan sets value with correct context
Resolved in Pega Version 8.5.5
After implementing a list of items where each has a unique barcode, scanning the barcodes using the mobile app worked correctly the first time but subsequent scans were setting the value on the first element of the list and missing the context of the current scan position. This has been resolved with an update to ensure the scan barcode action sets the value on the correct property when using repeating dynamic layers.