SR-117840 · Issue 170516
Autopopulate correctly set/disabled in the CSR portal
Resolved in Pega Version 7.1.7
Switching to some clipboard pages caused a null pointer error in the CSR portal for the operator. This was caused by an autopopulate call being made even when autopopulate was disabled. This has been corrected.
SR-117921 · Issue 174204
Warning message displays for ruleset save in lower version
Resolved in Pega Version 7.1.7
If a developer tried to save a rule in lower ruleset version while the same rule is already in a higher ruleset version, this was allowed with no warning. This behavior has been corrected.
SR-117961 · Issue 174233
Datetime conversion smoothed for SQL queries
Resolved in Pega Version 7.1.7
If the date time format on an SQL Server 2008 instance is set to ydm, a datetime conversion error was created due to the PRPC query using ymd format. In order to support all date formats for SQLServer, Timestamp is now formatted as "yyyyMMdd HH:mm:ss:SSS".
SR-118029 · Issue 173069
BIX filtering corrected
Resolved in Pega Version 7.1.7
Bix filters were not working consistently due to a missing call in the logic handling the ruleset references, and are now working correctly.
SR-118036 · Issue 171165
Corrected column width auto expand issues in decision table
Resolved in Pega Version 7.1.7
Decision tables which have many columns (8+) will expand the width very wide automatically by just clicking on the resize cursor (no dragging is necessary). However, trying to resize it back to a more reasonable width caused it to keep getting wider and wider due to an error with the dynamic display logic. This has been fixed.
SR-118125 · Issue 171188
Circumstance property value carried into dropdown options
Resolved in Pega Version 7.1.7
If a property of mode single value and type text was created with a defined local list of property values for the property, the value field was not automatically included in the dropdown options when attempting to use this property for circumstance/specialized flows. This was caused by an incorrect refresh section strategy used to determine when to reload the section for the circumstance by property, and has been corrected.
SR-118259 · Issue 173287
LookupList opened to unauthenticated requests
Resolved in Pega Version 7.1.7
When a list lookup was called from an unauthenticated service, it failed due to the lack of required authentication. The activity RULE-CIRCUMSTANCE-DEFINITION LOOKUPLIST has been modified to allow its execution by an unauthenticated requestor.
SR-118415 · Issue 172879
Ensured Application Document wizard captures all subflows
Resolved in Pega Version 7.1.7
The Application Document wizard was documenting only some of the flows that were expected to be included. This was caused by an incorrect null check on the input parameters which treated the subflows as duplicate flows, and has been updated.
SR-119030 · Issue 172922
Clipboard privileges tightened to enhance security
Resolved in Pega Version 7.1.7
Using standard browser development tools, it was possible to insert a client-side modification into a Pega-served HTML page to allow a customer to access partial clipboard inspection functionality. To correct this, starting activity privileges have been tightened.
SR-119095 · Issue 174195
TagCloud rendering corrected
Resolved in Pega Version 7.1.7
When opening pxTagCloudViewGadget it generated the error: 'Unable to open an instance using the given inputs: pxObjClass = "Rule-Obj-Report-Definition", pyClassName = "", pyStreamName = ""' . The tag cloud gadget reported "Can not render @baseclass.pxTagCloudInit", and when run or included in a section, it did not render any tags. This was found to be a design time error in Obj-Open of the report definition, and has been fixed.