SR-126545 · Issue 189937
Added remote case handling for password protected implementation applications
Resolved in Pega Version 7.1.8
There was a problem creating an implementation application in Application Express if the built-on application was password protected and the current logged-in application was also password protected, and the cases from built-on have remote case types. This was caused by validation issues, and has been corrected by modifying 'CreateObjectByPage' to pass the parameter 'SkipAddRemote' while calling save activity as true. Save will use this activity to skip current validation through 'ManageRemoteWorkTypesInApplication'.
SR-130671 · Issue 198217
Sort and filter check added for embedded sections in repeat grid columns
Resolved in Pega Version 7.1.8
In a repeat grid where sort and filter options were enabled on all the columns and one of the columns contained an embedded section, the sort and filter functions were not working on the column with the embedded section if the name of the embedded section was the same as the name of any property used for other column in the repeat grid. This issue was due to an incorrect call to pzGenerateControl for the cell containing the section include, and has been fixed by adding a check for section includes.
INC-136091 · Issue 598907
Activity updated for Mobile attachment access
Resolved in Pega Version 8.3.5
Preview and download were not working for attachments stored in Pega Cloud Storage repository for mobile devices. Attempting to open an email attachment to preview or download resulted in a console error and the tracer showed the message 'Class pxLinkedRefTo does not exist'. This has been resolved by updating "pzpega_control_attachutil" to use the activity "GetAttachmentReference" for interactions with the attachments from any storage type.
SR-122513 · Issue 184655
Resolved missing alert for dirty Dynamic Select pages
Resolved in Pega Version 7.1.8
At runtime when the user selects some value in first dynamic\c select and tries to close the work object by clicking on the red cross mark(X), the expected dirty form alert message was not appearing. The system should set SectionReloaded to true to trigger an alert in this circumstance, but in this was not happening for this case and has been corrected.
SR-123712 · Issue 184471
Resolved schema qualification for dedicated tables
Resolved in Pega Version 7.1.8
When creating a data table / data class via the wizard, selecting "Create Dedicated Table" would show success on the wizard screen but the class was mapped to "pr_other" and an error was logged. This was caused by incorrect schema qualification for WorkHistory, and has been resolved by inserting a requirement for implicit schema privileges.
SR-125937 · Issue 190307
Aligned Connector lines in Process Modeler
Resolved in Pega Version 7.1.8
Upon opening a flow rule, the Connector lines in Process Modeler were rerouted inconsistently with what was the saved state of the rule. The root cause was traced to code defects that resulted in the incorrect display of an error message and the incorrect drawing of the connector lines when the process modeler is loaded. These have been corrected.
SR-129928 · Issue 198643
Corrected naming difference for DateTime validation
Resolved in Pega Version 7.1.8
If the short description of a date or dateTime type property was different from the property ID, at runtime the required DateTime fields did not turn red when validation failed. This was caused by the Input ID for the datetime field being generated with the property short description instead of the property name. This has been fixed.
INC-144601 · Issue 602424
Empty addresses removed from email
Resolved in Pega Version 8.3.5
After upgrade, an issue was seen when sending email to multiple 'To' addresses generated an exception if any 'To' address had an empty value. To resolve this, a check has been added that will remove any empty address from the recipientTo address list.
INC-118918 · Issue 562155
Table Pagination elipses display properly for more than 10 pages
Resolved in Pega Version 8.4.2
When a table layout was configured with a report definition as the Data Source, the Pagination format in the grid header properly showed 'Page 1,2,3 ...' if there were fewer than 10 pages, but if there were more than 10 pages the '...' (elipses) were not appearing. This has been corrected.
SR-126654 · Issue 192199
Context retained for nested grids
Resolved in Pega Version 7.1.8
The base reference was computed incorrectly when RDL is dropped inside a repeating structure, causing local action to be executed in the wrong context. To resolve this, the system has been updated to return null if a RDL row is encountered in getRepeatObject, so that base_ref is calculated from the node where action is invoked.