SR-C33287 · Issue 372600
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-C33290 · Issue 372519
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-C33293 · Issue 372523
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-C33297 · Issue 372517
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-C33299 · Issue 372521
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-C33302 · Issue 372520
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-C33307 · Issue 372518
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-C33338 · Issue 375418
Custom controls work for date time filter windows
Resolved in Pega Version 8.1
The default date time format was displayed in the Filter windows even though other column controls were configured. This was due to a faulty 'if' condition in pzGetGridColUniqueValues and has been fixed.
SR-C33532 · Issue 374635
Lookups fixed for embedded property fields
Resolved in Pega Version 8.1
In Import Wizard, the lookup value applied through the field mapping option was not getting populated into embedded properties of the import class. This prevented using the lookup for ContactRef (which is an embedded property) in Household Data Loader. This has been fixed by adding some translation to the property formatting and then populating the field mapping options with the modified target field.
SR-C33623 · Issue 378007
Record limit removed for pzGetPropertiesForReports
Resolved in Pega Version 8.1
If a site had over 2000 string type properties defined on their case type, not all matches were found in the Edit Report. This was due to the List View pzGetPropertiesForReports having a limit of 2000 records, and has been resolved by setting the maximum rows to retrieve from 2000 to 0, which removes the limitation entirely.