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-C32943 · Issue 372905
Values correctly generated for elements with attributes in ParseXML134
Resolved in Pega Version 8.1
The new SOAP integration wizard was not creating "Value" properties in WSDL with several ComplexType elements using SimpleContent definition, though it did create properties for all the attributes. This resulted in data mapping anomalies. This was traced to a missed use case in rule generation, and the rule generation implementation has been updated to generate the "Value" property for ComplexType element with SimpleContent and configure it in the mapping rules.
SR-C32944 · Issue 372911
Values correctly generated for elements with attributes in ParseXML134
Resolved in Pega Version 8.1
The new SOAP integration wizard was not creating "Value" properties in WSDL with several ComplexType elements using SimpleContent definition, though it did create properties for all the attributes. This resulted in data mapping anomalies. This was traced to a missed use case in rule generation, and the rule generation implementation has been updated to generate the "Value" property for ComplexType element with SimpleContent and configure it in the mapping rules.
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.
SR-C32990 · Issue 372289
Enhanced whitelist/blacklist use for Alert logging
Resolved in Pega Version 8.1
An enhancement has been added to allow Alert logging to all sources (remote and local) to utilize a whitelist instead of a blacklist for parameter page inserts by default. This ensures appropriate sensitive information security regardless of destination.Alert parameter page data is white listed with allowed keywords by default for local and remote alerts. Previously, it was possible to set remote alerts to use whitelist or blacklist obfuscation. The code checked the black list for the local alerts (file) and then decided if it needed to do the whitelist as well. The new method checks if it needs to do whitelist (default) or blacklist and then does the obfuscation only once.
SR-C32991 · Issue 372305
Enhanced whitelist/blacklist use for Alert logging
Resolved in Pega Version 8.1
An enhancement has been added to allow Alert logging to all sources (remote and local) to utilize a whitelist instead of a blacklist for parameter page inserts by default. This ensures appropriate sensitive information security regardless of destination.Alert parameter page data is white listed with allowed keywords by default for local and remote alerts. Previously, it was possible to set remote alerts to use whitelist or blacklist obfuscation. The code checked the black list for the local alerts (file) and then decided if it needed to do the whitelist as well. The new method checks if it needs to do whitelist (default) or blacklist and then does the obfuscation only once.
SR-C32992 · Issue 372307
Enhanced whitelist/blacklist use for Alert logging
Resolved in Pega Version 8.1
An enhancement has been added to allow Alert logging to all sources (remote and local) to utilize a whitelist instead of a blacklist for parameter page inserts by default. This ensures appropriate sensitive information security regardless of destination.Alert parameter page data is white listed with allowed keywords by default for local and remote alerts. Previously, it was possible to set remote alerts to use whitelist or blacklist obfuscation. The code checked the black list for the local alerts (file) and then decided if it needed to do the whitelist as well. The new method checks if it needs to do whitelist (default) or blacklist and then does the obfuscation only once.
SR-C33019 · Issue 374880
Logic fixed for displaying Multi-Select control values
Resolved in Pega Version 8.1
Multi-Select control was not showing all of the values once the existing values were de-selected. This was due to a missed use case in the logic designed to prevent a user from seeing selected values in the multiselect dropdown, and the loadResults method has been modified to fix the issue.
SR-C33163 · Issue 374368
Customizable pyGridFilterRangeFields added to RD filters
Resolved in Pega Version 8.1
The filter for date fields in RD uses Spinner for the calendar navigation by default. In order to allow customization such as using a dropdown instead, a new section named pyGridFilterRangeFields has been added and made available.
SR-C33284 · Issue 372390
Enhanced whitelist/blacklist use for Alert logging
Resolved in Pega Version 8.1
An enhancement has been added to allow Alert logging to all sources (remote and local) to utilize a whitelist instead of a blacklist for parameter page inserts by default. This ensures appropriate sensitive information security regardless of destination.Alert parameter page data is white listed with allowed keywords by default for local and remote alerts. Previously, it was possible to set remote alerts to use whitelist or blacklist obfuscation. The code checked the black list for the local alerts (file) and then decided if it needed to do the whitelist as well. The new method checks if it needs to do whitelist (default) or blacklist and then does the obfuscation only once.