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.
SR-C33672 · Issue 375945
Field Values correctly localized in Rules Explorer
Resolved in Pega Version 8.1
Rules Explorer was not showing localized Field Values. This was traced to an implementation error: in older versions of Pega, the instances list was shown by using the list view. In more recent versions, this list was moved to report definition and the localization was lost. This has been corrected.
SR-C33699 · Issue 373276
Truncation added to handle creation of test case label >64 chars
Resolved in Pega Version 8.1
Attempting to create a strategy-related test case failed if the test case label given was more than 64 characters. To better handle this limit, specific code has been added to form a test case label that will truncate it to 64 characters if the label of the test case exceeds that limit.
SR-C33742 · Issue 373407
AggregationValue object modified to support aggregating records with multiple measurements
Resolved in Pega Version 8.1
VBD Synchronization was failing with the exception "java.lang.IllegalArgumentException: Aggregation failed due to unexpected value type". This occurred when processing a specific sequence of IH Facts on the same day, in which IH Facts without measurements were followed by IH Facts with multiple measurements, such as:1) Fact with dimension values "A,B,C" and without measurements 2) Fact with dimension values "D,E,F" and with multiple measurements (must be multiple) 3) Fact with dimension values "A,B,C" and with any of the measurements from 2. To resolve this, the tracking of field count in each aggregate has been updated to handle multiple added measurements.
SR-C33761 · Issue 376121
pyFileSize changed to type Text
Resolved in Pega Version 8.1
An error occurred when using an RD to fetch pyFileSize of all attachments uploaded from Pulse. This was traced to a type mis-match: while the property itself is a decimal, the activity was setting a string value with alphanumerals. To avoid this error, the pyFileSize property will be created with type as Text.
SR-C33768 · Issue 378863
Fixed ESRI maps offline case causing unending sync
Resolved in Pega Version 8.1
The Pega windows app on desktop was showing syncing all the time when logged in online and ESRI Maps was configured through the non-auto generated section on an offline case. This has been corrected.
SR-C33768 · Issue 379381
Fixed ESRI maps offline case causing unending sync
Resolved in Pega Version 8.1
The Pega windows app on desktop was showing syncing all the time when logged in online and ESRI Maps was configured through the non-auto generated section on an offline case. This has been corrected.