SR-D5079 · Issue 438383
Handling added for empty UILabel in grid fields
Resolved in Pega Version 8.1.5
When using a Datetime property with a default format, opening the filter popup and clicking on the 'select all' check box caused the format of the values to break. This was traced to ".pyUILabel" being passed as empty, and handling has been added for that in "pzUniqueValuesGridFields".
SR-D5079 · Issue 438381
Handling added for empty UILabel in grid fields
Resolved in Pega Version 8.2.2
When using a Datetime property with a default format, opening the filter popup and clicking on the 'select all' check box caused the format of the values to break. This was traced to ".pyUILabel" being passed as empty, and handling has been added for that in "pzUniqueValuesGridFields".
INC-185434 · Issue 674053
Page group property passed correctly for complex questions
Resolved in Pega Version 8.7
When the Pega Survey Smart shape was used to configure a list of complex set of questions using Question rules and invoked using the Survey shape, the reload system was not passing the subscript value for the Page group property pyQuestionnaire. This caused an Invalid Reference exception and displayed an error pop up for the end user. Investigation traced this to a call to RefreshList to load a section holding pyQuestionnaire(Subscript) page content which was in place as part of a legacy fix but which has since been made unnecessary due to infrastructure changes in the DOM utilities. To resolve this, the ComplexQuestionCheckboxTemplate and pzComplexQuestionCheckBoxTemplateRowDetails section rules have been updated to remove the RefreshList action on checkbox.
SR-C89628 · Issue 430886
Correct values are selected in auto-complete in list configuration after scrolling
Resolved in Pega Version 8.1.5
When a value from the second page of the source list in the auto-complete was selected, the prior value was getting selected and posted. As an example, if the (n)th value was selected by scrolling down the results in the list, the (n-1) value was getting selected and posted to clipboard. Investigation showed this occurred if autocomplete was configured with allow free form input ' no', and that results were not getting selected properly after first scroll when using list configuration. This has been corrected.
SR-C89628 · Issue 430885
Correct values are selected in auto-complete in list configuration after scrolling
Resolved in Pega Version 8.2.2
When a value from the second page of the source list in the auto-complete was selected, the prior value was getting selected and posted. As an example, if the (n)th value was selected by scrolling down the results in the list, the (n-1) value was getting selected and posted to clipboard. Investigation showed this occurred if autocomplete was configured with allow free form input ' no', and that results were not getting selected properly after first scroll when using list configuration. This has been corrected.
INC-180482 · Issue 661513
Browser compatibility update for setActivityAction
Resolved in Pega Version 8.7
After update, the Parameter Configuration popup was blank when using Microsoft Internet Explorer. This was traced to security updates that utilized the SafeURL.prototype.setActivityAction containing the startsWith API which is not supported by Internet Explorer. To resolve this, startsWith has been replaced with indexOf for cross-browser compatibility.
SR-C96703 · Issue 435743
CMIS Timestamp function updated to support more timezones
Resolved in Pega Version 8.1.5
When trying to edit any attachment , a null pointer exception was generated from the out of the box activity pygetobjectfromAPPCMISConnector by the pzFormatCMISTimestamp function in the class PRDateFormat.java. This was traced to CMIS using a library that did not support all the possible timezones for a timestamp. To resolve this, the RUF pzFormatCMISTimestamp has been updated to use java.text.SimpleDateFormat as it currently supports the highest number of timezones and permutations in the CMIS timestamp format. A check has also been added so that if a timezone cannot be found, the date is simply not converted and a warning is logged.
SR-D1441 · Issue 438907
CMIS Timestamp function updated to support more timezones
Resolved in Pega Version 8.1.5
When trying to edit any attachment , a null pointer exception was generated from the out of the box activity pygetobjectfromAPPCMISConnector by the pzFormatCMISTimestamp function in the class PRDateFormat.java. This was traced to CMIS using a library that did not support all the possible timezones for a timestamp. To resolve this, the RUF pzFormatCMISTimestamp has been updated to use java.text.SimpleDateFormat as it currently supports the highest number of timezones and permutations in the CMIS timestamp format. A check has also been added so that if a timezone cannot be found, the date is simply not converted and a warning is logged.
SR-C96703 · Issue 435742
CMIS Timestamp function updated to support more timezones
Resolved in Pega Version 8.2.2
When trying to edit any attachment , a null pointer exception was generated from the out of the box activity pygetobjectfromAPPCMISConnector by the pzFormatCMISTimestamp function in the class PRDateFormat.java. This was traced to CMIS using a library that did not support all the possible timezones for a timestamp. To resolve this, the RUF pzFormatCMISTimestamp has been updated to use java.text.SimpleDateFormat as it currently supports the highest number of timezones and permutations in the CMIS timestamp format. A check has also been added so that if a timezone cannot be found, the date is simply not converted and a warning is logged.
SR-D1441 · Issue 438906
CMIS Timestamp function updated to support more timezones
Resolved in Pega Version 8.2.2
When trying to edit any attachment , a null pointer exception was generated from the out of the box activity pygetobjectfromAPPCMISConnector by the pzFormatCMISTimestamp function in the class PRDateFormat.java. This was traced to CMIS using a library that did not support all the possible timezones for a timestamp. To resolve this, the RUF pzFormatCMISTimestamp has been updated to use java.text.SimpleDateFormat as it currently supports the highest number of timezones and permutations in the CMIS timestamp format. A check has also been added so that if a timezone cannot be found, the date is simply not converted and a warning is logged.