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-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.
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.
INC-177323 · Issue 672420
Search string wildcard use documentation updated
Resolved in Pega Version 8.7
The support article for the search API has been updated to clarify the ability to use the wildcard character "*" by manually adding it to the prefix of each term in the search string.