INC-166048 · Issue 659534
Navigation icons added for use in offline mobile
Resolved in Pega Version 8.7
When using an offline mobile app, clicking on an image / link on the home page for navigation resulted in the error “Resource missing. See client logs.” This was traced to a missed use case that resulted in some icons not being available in the package, and has been corrected by including the following: webwb/py-menu-toggle.png webwb/pzgrid_downarrow.png webwb/pymenuleftarrow.png webwb/pymenurightarrow.png webwb/pymodal_mask_img.png webwb/py-grid-sort-down.svg
SR-D50350 · Issue 519077
Added keydown event handler for JAWS use
Resolved in Pega Version 8.4
Clicking the "Select file(s)" button worked for mouse and keyboard users but did not work when a screen reader was used. Investigation showed that Keydown events were not firing while the JAWS screen reader was running. Since the screen reader was prompting a space key press to activate, an event keycode for space has been added in the pzMultiFilePath control for Select file button to resolve this issue. In addition, a role application has been added for a button to fire keydown events while running the JAWS screen reader.
SR-D42451 · Issue 518068
ExecuteRDB call updated to use NativeSQL for blob
Resolved in Pega Version 8.4
After creating a test activity to clear data set records that used the DataSet-Execute method and passed the data set name and truncate operation, only 51 records were deleted in a single run when the data set had more than 51 records. Investigation showed that for blob tables, the database truncate operation was using executeRDB with an empty results page, i.e. it didn't specify pyMaxRecords, which on some databases might have limited the number affected records. To resolve this, the executeRDB call in the database truncate operation has been modified to use NativeSQL for blob tables.
SR-D42451 · Issue 518067
ExecuteRDB call updated to use NativeSQL for blob
Resolved in Pega Version 8.2.6
After creating a test activity to clear data set records that used the DataSet-Execute method and passed the data set name and truncate operation, only 51 records were deleted in a single run when the data set had more than 51 records. Investigation showed that for blob tables, the database truncate operation was using executeRDB with an empty results page, i.e. it didn't specify pyMaxRecords, which on some databases might have limited the number affected records. To resolve this, the executeRDB call in the database truncate operation has been modified to use NativeSQL for blob tables.
INC-192159 · Issue 691022
Handling added for designtime page used in runtime
Resolved in Pega Version 8.7
After creating a survey with branch Create survey cases routed to different actors, some cases missed the assignments and were left idle with no access to progress. Survey cases (with branches) having the 'when' conditions in flow connectors experienced this intermittently in production. This was traced to the use of D_pzSurveyPage data page called from the ProcessUpdate data transform while creating the survey: this data page is for design time and should not be used at runtime as it requires design time pages like CaseTypePage which will not be available at runtime. To resolve this issue for runtime, in Step 3 of pzGetAllConnectors, pyClassName will be copied from the step page and set for pzGetConnectorsForDecision.
SR-118159 · Issue 174990
Improved handling for Case notes when spellchecker is active
Resolved in Pega Version 7.1.7
If a lot of content was added for a case Note, clicking on the Notes tab caused the text to display in a big yellow box which could not be dismissed. This was traced to the spell checker not properly handling RTE's hidden textarea field, and the code has been modified to correct this.
SR-119909 · Issue 176760
Fixed page toggle when a grid contains an error
Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7
It was not possible to navigate to a different page in a grid when a validation error existed on any page.The error could be corrected if it occurred on the current page and paging ability would return, but if the error as in a different page it was not possible to navigate to correct it. This was traced to code which prevented moving to another page if there was an error on refresh. While there was a workaround, the code has been updated to allow moving to another page unless the error occurs on the current step page.
SR-D28859 · Issue 502006
Declare expressions validation message persists when clicked
Resolved in Pega Version 8.4
After configuring a section with fields and validation through validate rule where some of the field properties were sourced in declare expressions, clicking on the validation message caused it to disappear. Investigation showed that when validations are displayed on the screen, clicking on any of the fields which have calculatexpression as validationtype triggers a check for errors on the field with caluclateexpression validationtype. As there were no errors, the existing validation message on the field was removed. To resolve this, the system has been updated so that If the calculate expression does not have any error and the field has existing validations, the removal of validation message will be skipped.
INC-185847 · Issue 669526
Handling added for disabling weekends when no weekends are available
Resolved in Pega Version 8.7
A browser exception was generated while selecting the option “Disable weekends”. This was traced to a malformed array of weekends in a scenario where the Data-Admin-Calendar instance had all business days checked (i.e., no weekends). To resolve this, DatePickerAssembly and pzGenerateDatePicker have been updated to handle the case when there are no weekends available in the Data-Admin-Calendar instance.
SR-D17919 · Issue 491582
Corrected thread switching when moving between interactions tabs
Resolved in Pega Version 8.4
When using Create New for a Phone Call-Consumer in one tab and Create New for an Outbound Phone Call on another tab, the thread was not changing when switching between the tabs of the interactions. Closing the Outbound call interaction resulted in null pages on the clipboard. This has been resolved by updating the pzpega_ui_doc_tabsupport file so it switches to root document context if called from onActivate function using a flag.