SR-C18936 · Issue 358807
API added to customize properties used in checksum calculation
Resolved in Pega Version 8.1
In order to provide a way to customize certain system properties from a checksum calculation, an API has been added to set a list of properties to be excluded.
SR-C29742 · Issue 386203
Added check for JSON array when setting context for data transform
Resolved in Pega Version 8.1
When incoming JSON for a data transform had a null property, the data transform failed with a Null Pointer Error. This was due to the system assuming the root context to be null, which works for JSON but not for an Array of JSONs. To correct this, a check for topLevelArray has been added to ensure the system has the correct context of the current JSON Object.
SR-C32739 · Issue 372485
Credentials sanitized when logging exception for invalid primary page name
Resolved in Pega Version 8.1
Whenever an invalid primary page name was passed along with credentials in queryString, the credentials were logged without sanitizing or masking. Current standard behavior is that flows are run in an authenticated session that would not be passing this information, but this scenario was traced to legacy code for a very corner case that was not transitioned to the more secure method. The error information will now be properly sanitized on logging an exception.
SR-C32911 · Issue 373513
Submit button no longer shows <u> tag when accessibility enabled
Resolved in Pega Version 8.1
When a user was accessibility enabled and there was a custom filter section for a report, the Submit button in the pzRRDisplayCustomFilterSection section incorrectly showed "<u>S</u>ubmit" as its label. To correct this, the button has been updated to a new Auto-Generated button and script on click has been added.
SR-C39796 · Issue 383047
Enhancement added to switch tab name localization when locale switches
Resolved in Pega Version 8.1
When launching a Harness in a tab onclick of a link/button from a section, passing tab name as a localized field value was not working properly when switching between different locales. This was caused by the Tab name not getting updated on click on Launch harness, and has been corrected with the addition of a new parameter "bLocalize" for pzActionAppendValue to invoke getLocalizedTextForString if the parameter is true. This value will be passed as true when called from pzActionShowHarness newDocument case.
SR-C32016 · Issue 374775
Handling added for JSON generation when special characters are given in operator fullname
Resolved in Pega Version 8.1
If an operator rule was saved with a special character (for example Horizontal Tab) in the full name field, it resulted in pyGetOperatorsForCurrentApplication producing an invalid JSON object. In order to correct this, the JSON created in step no 3 in pyGetOperatorsForCurrentApplication activity will use @(Pega-AppDefinition:Utilities).pzEscapeJSONSpecialCharacters() for .pyUserIdentifier (operator ID) and .pyUserName (Full Name).
SR-C27585 · Issue 370960
Cassandra startup modified to use absolute path to needed files
Resolved in Pega Version 8.1
DDS was not starting on Windows, reporting that it was unable to find the cassandra.bat file. In this case, Cassandra was started using ".\cassandra.bat" command and the path to cassandra.bat was specified by setting the working directory in ProcessBuilder, but ProcessBuilder doesn't use working directory to find the location of the script. In order to ensure consistent startup behavior, the invocation of Cassandra scripts has been modified to run using an absolute path to Cassandra startup files in the command.
SR-C35969 · Issue 375783
Documentation updated to clarify how to use Tracer on Service Rules
Resolved in Pega Version 8.1
Due to an error in the documentation where the table of contents was pointing to an older version of the file, the information about configuring the Tracer to examine Service Rules was not clear. The document reference has been updated to point to the correct version which reads: Service rule tracing is only enabled in environments where the trace/cluster/ServiceRuleWatchMaxProductionLevel Dynamic System Settings is greater than or equal to the production level. By default, trace/cluster/ServiceRuleWatchMaxProductionLevel is set to 4, which means that the ability to trace service rules would not work in a production level 5 environment until trace/cluster/ServiceRuleWatchMaxProductionLevel is increased to 5.
SR-B92421 · Issue 348757
Email Attachments use given mail encoding instead of defaulting to UTF-8.
Resolved in Pega Version 8.1
For email listener use cases, email attachments were always converted to HTML using UTF-8. This caused email characters to be changed when they were sent using any other type, ex ISO-8859-1 (Western European). To resolve this, the encoding used in the incoming email will be used to generate the HTML content before it is attached to the work object.
SR-C32947 · Issue 378777
Application Wizard works on application built using application type as framework
Resolved in Pega Version 8.1
Trying to run the Application Wizard on an application built on a framework was failing. This happened only when the framework being used was also built by the Application Wizard and no changes were made to that application after creation. The root cause of this was 'pyAccessGroupForAdministrator' not being correctly populated on the framework application during its creation. Setting this property during the framework application creation has fixed the issue.