SR-A17748 · Issue 233597
TrimLog performance improved
Resolved in Pega Version 7.2.1
Activity log.trimlog is called several times from the systemCleaner agent to clean up old entries of generally unused Log- classes. In order to improve performance on large logs, the previous partial load and delete method has been updated to a bulk cleanup using the purgeTableContainingClass() API in the Pega Database.
SR-A17758 · Issue 234057
Check added to avoid duplicate encryption
Resolved in Pega Version 7.2.1
When a property of type TextEncrypted was edited from the clipboard viewer, the encrypted value was being encrypted again. This was caused by the server side trimming the string values of parameters sent in a post body, removing '\t' from the encrypted value '\t{ps}XXXXX' and triggering encryption of an already encrypted value. To prevent this, the system has a check for strings starting with '\t{ps}' at the time of parsing URL Parameters or post body.
SR-A17773 · Issue 234118
Custom field value visible for maxloginattempts message
Resolved in Pega Version 7.2.1
In order to support a customized field value message once a user crosses the allowed invalid login attempts threshold, a new overloaded method of prepareStatusInfo() has been introduced in PRDiagnosticStream.java that will not mask the exception details with generic error message.
SR-A17976 · Issue 239119
Updated SendEmailMessage to handle images with spaces in the filename
Resolved in Pega Version 7.2.1
When an image was inserted into a draft email and sent, the image was visible in PRPC but not at the receiving end. This was a problem with the regex available in the SendEmailMessage activity not being able to handle file names containing spaces: handling for this has now been added.
SR-A18193 · Issue 238469
SystemCleaner correctly purges pr_perf_stats
Resolved in Pega Version 7.2.1
It was noticed that SystemCleaner was working well except for a periodic dramatic purge that suddenly filled logs and sometimes caused a system crash. When BIX runs via command line, this updates the associated DSS in the application. If the DSS usage/usagetrackingenabled or its associated prconfig.xml setting are set to false, Step 12 of the SystemCleaner does not perform a number of activities including regular purging the pr_perf_stats table. This has been modified to remove the setting usage/usagetrackingenabled from prconfig.xml as agents are by default enabled.
SR-A18404 · Issue 235467
New parameter to disable logging of Tidy PDF processing warnings
Resolved in Pega Version 7.2.1
When purge/archive was enabled, the system logs were filling with Tidy warning errors during PDF conversion. To resolve this, the new parameter 'pyShowWarning' has been added to the HTMLTOPDF Activity: set it to 'false' to avoid Tidy processing warnings in logs.
SR-A18624 · Issue 239177
Fixed post-upgrade data table conversion to local storage
Resolved in Pega Version 7.2.1
After upgrade, updating a data table into a local storage source generated the error "Cannot change keys for a class with (725) instance(s) ". This occurred when the local variable ?classKeysChanged? is true, which happened during comparison of the Key fields of the step page (classPage) and the primary page (ClassForm) because the order of the keys had changed even though the number of keys were same. The "AddProperties" activity has now been modified to check if there are keys already set in the class and if there are any, then skip resaving the class and exit the activity.
SR-A18694 · Issue 246976
Method changed for locating Word Templates folder
Resolved in Pega Version 7.2.1
The method used to obtain the Word templates folder always lower cases the folder path, but this poses a problem for the Turkish locale when the path contains capital I with no dot. Turkish has two variants of I - one with dot and one without dot. To resolve this, the Office templates folder path will be determined based on a combination of certain registry keys dependent on the Word version.
SR-A18813 · Issue 236196
Support added for auto-generated numeric IDENTITY columns in RD
Resolved in Pega Version 7.2.1
Because IDENTITY auto-generated columns were not supported , RD did not identity the column of type numeric() IDENTITY and generated an error when accessing a table with NUMERIC column types in SQL Server 2012. Numeric() TYPE was already supported for generation in RD, and an SQL connector has been added to handle tables with numeric() IDENTITY as well.
SR-A18899 · Issue 236697
Operator ID screen messages localized
Resolved in Pega Version 7.2.1
Localization has been added for error messages generated in the Operator ID Screen.