SR-121277 · Issue 181001
Deployment user privileges updated for upgrades
Resolved in Pega Version 7.1.8
When attempting to upgrade some installations, the upgrade script was failing while trying to determine the current PRPC version. This was caused by the deployment user lacking the DBA privileges to read/write the tables in the rules and data schema, and has been updated.
SR-121709 · Issue 179068
New default directory setting added to DDL generation
Resolved in Pega Version 7.1.8
If the DDL for a new PRPC installation was generated without using the optional parameter for the file location, the file was created in the root directory. To avoid this, a default gen_dir setting (./schema/generated) has been added to generateDDL.sh to handle cases when the parameter has not been set.
SR-121746 · Issue 182390
Country code TLS (Timor-Leste) added for FieldValue
Resolved in Pega Version 7.1.8
In the ruleset Rule-Obj-FieldValue, the country code TLS (Timor-Leste) was missing for localization. This has been added.
SR-122215 · Issue 180037
Resolved installation errors for DB2 Z/OS with WebSphere
Resolved in Pega Version 7.1.8
A problem was encountered while installing split schema on a DB2 z/OS system with WebSphere. This was caused by an erroneous system setting where the ports to the DB2 database were not open in this environment. While the Admin could correct the environment to open the ports and allow the application server node to connect to the DB2 database, this has been changed in the software to default to the correct settings.
SR-122292 · Issue 182878
Operators and Access Groups are now automatically force re-indexed during import
Resolved in Pega Version 7.1.8
If a number of new OperatorIDs were created and added to two workgroups and then the changes were exported, the new OperatorIDs were present when the file was imported to other environments but a query run against the table PR_INDEX_OPERATOR_WORKGROUP did not incorporate the new IDs. While there was a workaround of manually forcing a re-index during import to fully incorporate the new IDs, the Operators and Access Groups are now automatically force re-indexed during import to ensure data is up to date.
SR-122314 · Issue 178491
Resolved installation errors for DB2 Z/OS with WebSphere
Resolved in Pega Version 7.1.8
A problem was encountered while installing split schema on a DB2 z/OS system with WebSphere. This was caused by an erroneous system setting where the ports to the DB2 database were not open in this environment. While the Admin could correct the environment to open the ports and allow the application server node to connect to the DB2 database, this has been changed in the software to default to the correct settings.
SR-122591 · Issue 183772
Addressed migrate.bat file datetime format issue
Resolved in Pega Version 7.1.8
The script 'migrate.bat' sets up a logfile name based on the current time/date. However, the script was only working when using United States/English as the locale where the format of the '%date%' variable was MM/DD/YYYY, and failed with an obscure error in locales using the DD/MM/YYYY format. There was a local change of hardcoding the 'TIMESTAMP' variable, but this has been resolved by adding the use of a local insensitive datetime from the WMIC utility on Windows systems for the install.bat, upgrade.bat, resume.bat and migrate.bat scripts. The WMIC utility (Windows Management Interface Cmdline) is supported in XP and beyond.
SR-122618 · Issue 185154
SetNewReportColumn now defaults to 20px
Resolved in Pega Version 7.1.8
No nominal column width was assigned to new columns added to a report. If the other columns in the report had an assigned cumulative width that exceeded the width of the browser window, the added column was not visible or selectable either in the Report Editor or in the Report viewer. The added column behaved as if it had zero width. To resolve this, SetNewReportColumn has been modified with a default of FieldWidth as 20 and FieldWidthUnit as px.
SR-122619 · Issue 188285
Ensured Excel reports contain fresh data
Resolved in Pega Version 7.1.8
A sporadic issue was found when running multiple reports and exporting them to Excel where new reports sometimes contained data from previously exported results. This was found to be an issue with stale data being left on the TmpExportResultsPageOrig because this page was not listed in the Page-Remove at the end of the RDExportWrapper activity. This has been corrected.
SR-122641 · Issue 182813
Edit filters repaired for Report Definition text fields with Microsoft Internet Explorer 9 & Microsoft Internet Explorer 11
Resolved in Pega Version 7.1.8
Using Microsoft Internet Explorer 9 and Microsoft Internet Explorer 11, all of the Report Definition text Fields (including auto complete) in the Edit Filters were disabled and would not accept input when trying to select the property using the mouse. To resolve this, the UI functions have been modified to handle range text native functions for these browsers.