SR-115392 · Issue 164192
Added customization for PDF page numbers
Resolved in Pega Version 7.1.7
Previously, it was not possible to designate the initial page number in the PDF generated by HTMLToPDF activity. Two parameters have been added to allow for greater customization: "header" activates page number support in the document header, and "startPage" is used to set the initial page number for the document. The "startPage" parameter can be used for both the header and footer.
SR-115492 · Issue 169327
Obj-save and commit working for fully-exposed classes
Resolved in Pega Version 7.1.7
If an exposed class was implemented by creating an underlying database table, trying to perform an Obj-Save (or commit) on an exposed class generated errors regarding some properties not having corresponding database columns. This happened when one of the Page names was also the beginning part of a name of one of the simple types, and was caused by a flaw in the logic used to determine if the property is an embedded reference. This has been corrected.
SR-115511 · Issue 168772
Application Express Wizard updated to correctly bind rulesets
Resolved in Pega Version 7.1.7
New Rule-Access-Role-Obj (RARO) rules created using Application Express wizard were being bound to specific ruleset versions vs. ruleset names. This caused failure to any modification to those RAROs, since modifying a RARO with a ruleset version would mean the save-as would fail if the validation found a RARO already present for that ruleset. In order to ensure proper binding and aid migration, a RARO with ties to a ruleset version will have that the version information removed automatically upon saving of the RARO.
SR-115521 · Issue 166317
Repeat Grid navigation enhanced for 'Expand Pane' edit mode
Resolved in Pega Version 7.1.7
If a Repeat Grid in a section was set to 'Expand Pane' as the Edit Mode , the 'previous' and 'next' buttons on the modal dialog were not working. The logic was missing for the Next and Previous APIs when using 'Expand Pane', and has been inserted to fix this issue. In addition, the Next and Previous APIs were enhanced to be appropriately disabled when the first and last rows are reached.
SR-115687 · Issue 165814
Vertical scrollbar fixed for expandable rows in Repeating Grids
Resolved in Pega Version 7.1.7
When using a Repeating Grid layout with pagination, expandable rows, a fixed size, and frozen header, expanding the row during run time caused the vertical scrollbar to disappear. The API has been updated to properly display the scrollbar for this setting combination.
SR-115711 · Issue 165363
Flow Action class correctly retrieved for subprocesses
Resolved in Pega Version 7.1.7
When running a Process Flow in a Data- class that is called from a Work- process flow via a SubProcess, the error "Failed to find a 'RULE-OBJ-WHEN' with the name 'CANMAINTAINCASEREPORT'" was being generated. This was caused by incorrect handling for the class: the flow action and WHEN rule are in a WORK class, but when the sub-flow is executed it looks in the DATA class of the embedded page instead of the WORK class relevant to the overall case. There was a workaround of saving the WHEN rules into the Data- classes, but the system now uses workPage instead of interestPage for localcase to ensure the correct class is retrieved.
SR-115717 · Issue 168256
Rearranging columns in multi-tab sections corrected
Resolved in Pega Version 7.1.7
When using a multi-tab section, re-arranging the columns was only effective in the first tab. This was caused by the tabs lacking individual global variables to give them unique IDs, and has been fixed.
SR-115719 · Issue 165692
WebSphere WorkManager pool setting correction
Resolved in Pega Version 7.1.7
Due to a coding defect, the WorkManager thread pool setting configured through WebSphere was not being utilized. As a consequence, a large number of daemon threads could be created during certain scenarios and the ability to make connections could be reduced. This has been fixed, and the system will now use the WebSphere WorkManager setting.
SR-115742 · Issue 166472
Read-only value validation messages now appear in-line
Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7
By design, validation error messages were not displayed next to read-only values but rather displayed at the top of the harness. As this is no longer the preferred behavior, an enhancement has been added to display these read-only validation messages in-line as is seen in edit mode.
SR-115749 · Issue 167027
Support added for custom filtering and refresh inside a Repeat Grid
Resolved in Pega Version 7.1.7
If a dropdown control was placed in the column header of a repeating grid to work as a filter and perform a section refresh for the list (based on a column present in the list, but not displayed in the grid), checking the option to freeze the column headers (and use a fixed height/width) caused the dropdown to no longer work and no refresh action could be triggered. This was caused by a second hidden dropdown in the grid with the fixed header configuration that overwrote the selected value in the ASYNC request that is sent when the dropdown value changes. To remedy this, changes were made in the HTML generation to make the hidden header input disabled. This works only when configured as "auto": the control generation logic overwrites all readonly conditions to true if the dropdown is configured as "Editable".