SR-D86079 · Issue 548108
Label truncation added for pinned item title
Resolved in Pega Version 8.3.3
While pinning a Space, document, or URL, the length of the item title was causing validation issues if it exceeded 64 characters. This has been resolved by modifying the pzGetPins activity to truncate pyLabel to 64 characters using the truncateLongText function.
SR-D73237 · Issue 539124
Pagination updated to resolve repeating Pulse notes
Resolved in Pega Version 8.3.3
After adding a case and entering 15 Pulse notes, scrolling down resulted in the notes being duplicated. Investigation traced this to entering more than 10 posts in a single interaction on a previously empty case when "Progressive pagination" was enabled for the repeating dynamic layout. On Private Edit, if the pagination was changed to "NONE" then the issue was resolved. Pagination depends on the pzPagingStartDateTime property, which is set on D_pzFeedParams, but since there were no results in this scenario this property was not being set. To resolve this, an update has been made so that pzPagingStartDateTime will be set if it is empty.
SR-D76620 · Issue 544576
Resolved touch events issue with updated Google Chrome
Resolved in Pega Version 8.3.3
After upgrading Google Chrome, touch events on a flow action under the Action Button in a case or on the application under "Launch web interface" were not reacting and the flow actions were not accessed. Investigation showed that Google Chrome's latest upgrade (79.0.3945.130) removed the ontouchstart property in the window, causing the isTouchable capability identification method to fail. This has been resolved by adding a check for navigator.maxTouchPoints to identify for Google Chrome whether the device involved has a touchscreen.
SR-D85551 · Issue 548075
Resolved touch events issue with updated Google Chrome
Resolved in Pega Version 8.3.3
After upgrading Google Chrome, touch events on a flow action under the Action Button in a case or on the application under "Launch web interface" were not reacting and the flow actions were not accessed. Investigation showed that Google Chrome's latest upgrade (79.0.3945.130) removed the ontouchstart property in the window, causing the isTouchable capability identification method to fail. This has been resolved by adding a check for navigator.maxTouchPoints to identify for Google Chrome whether the device involved has a touchscreen.
SR-D82882 · Issue 544165
Special characters excluded in the create tag activity
Resolved in Pega Version 8.3.3
The system was allowing the creation of a tag with special characters at the case level from the Actions tab. This was traced to the pxCreateTag activity 3rd step, which passed the current page parameter without invoking the pyValidateTagName activity. This has been corrected by updating the logic.
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.