SR-114807 · Issue 162848
"Transfer to an Operator" dynamic list was not sorted
Resolved in Pega Version 7.1.7
The "Transfer to an Operator" dynamic list was not sorted, while the "Transfer work from" dynamic list was. This was caused by different function calls in the system, and has been corrected so the lists sort properly by property name.
SR-114917 · Issue 166117
Alignment issues with IAC resolved
Resolved in Pega Version 7.1.7
When a dynamic layout of stacked style was used in conjunction with IAC, resizing the window caused the elements to not be properly aligned. CSS issues in the HTML handling of overflow properties have been corrected with the resizing harnesses.
SR-118050 · Issue 169612
Alignment issues with IAC resolved
Resolved in Pega Version 7.1.7
When a dynamic layout of stacked style was used in conjunction with IAC, resizing the window caused the elements to not be properly aligned. CSS issues in the HTML handling of overflow properties have been corrected with the resizing harnesses.
SR-115000 · Issue 165234
Operator substitutions restored to the availability settings
Resolved in Pega Version 7.1.7
The operator availability setting links for Case Manager portal and Case User portal were missing substitute assignee details. These have been restored.
SR-115104 · Issue 165556
IAC functionality enhanced for secure environments
Resolved in Pega Version 7.1.7
In order to ensure IAC functionality in a secure environment, the following updates were made: HTTPOnly support has been enabled for prGatewaySESSIONID cookies; encryption and obfuscation have been set up for web nodes; added a check for login-config.xml to add default-users.properties and default-roles.properties to the other application-policy.
SR-115268 · Issue 166797
Cleanup improved for resolved work-items
Resolved in Pega Version 7.1.7
An error in the logic for Stage Flows caused improper cleanup of resolved work items, leading to outsized assignment tables. This has been corrected.
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-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.