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-118305 · Issue 171562
Report definition reference columns expanded to include data type smallint
Resolved in Pega Version 7.1.7
Report definitions with reference columns of data type SmallInt in their database were not able to run as expected after migration due to missing support for that data type. This support has been added.
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-118604 · Issue 175098
Externally mapped class hierarchy given precedence over default mapping
Resolved in Pega Version 7.1.7
If a series of properties in the same class hierarchy were explicitly mapped to columns in the external database table and shared the names of some of the database columns, the Obj-save failed. Sporadically when the system restarted, the properties that share the names of the database columns were mapped to those columns. The code has been updated to ensure that external mapping takes precedence over PRPC's default property-column mapping
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.
SR-119148 · Issue 173101
MSSQL columns with spaces in the name will generate an error seeking correction before submission
Resolved in Pega Version 7.1.7
While Microsoft SQL Server (MSSQL) tables allow columns with spaces in their name, the PRPC engine does not allow such names at this time. In order to handle the incompatible name issues, the Integrator Wizard will detect that it is dealing with a table that has spaces in its column names, and fail up front with a targeted error message.
SR-119538 · Issue 177397
Detection added for custom work history tables
Resolved in Pega Version 7.1.7
In order to fully embrace mobile capabilities, columns were added to the work history tables to allow actions to be tracked as a geographical map where each history event is a numbered locale indicator on a map instead of a row of entries. From lat/long it is also possible to call a Google service and get the street address as well. However, this functionality caused some issues post-migration with if there were customized pc_history_work tables mapped to custom classes. To remedy this, a check has been added to only query for pxlatitude/pxlongitude if columns are exposed and shown, and that will detect if the columns aren't present.