INC-220616 · Issue 718051
maxConsecutiveViolations default set to 5
Resolved in Pega Version 8.8
Attempting to make API calls using the PegaMKTContainerV2 REST service resulted in an IllegalArgumentException. This was traced to the MaxViolations under Application Settings for "Development" (the current environment) production level being set to 0, which caused the exception because the value must be a positive number higher than 0. This has been resolved by setting the value to default to 5.
INC-212354 · Issue 711210
Scenario Planner performance improvements
Resolved in Pega Version 8.8
Scenario planner runs were causing out of memory errors on the dataflow nodes. To resolve this, updates have been made to improve performance. Only relevant information will be kept for decision funnel simulations out of SR pages, the memory footprint of data structures used to aggregate and rollup counts has been reduced, and temporary objects will be released as soon as they are not needed anymore.
INC-202218 · Issue 697349
Input from Microsoft Windows keyboard numpad enabled
Resolved in Pega Version 8.8
After entering a currency amount using the right side number pad keys on a Microsoft Windows keyboard, a mandatory field validation was being thrown on what appeared to be a correct input. This was due to an if condition in the keyup function that caused entries from the right side number keys to not be considered as input, and has been resolved by removing the condition from the pzpega_control_textinput file.
INC-154290 · Issue 613471
Signature capture exception resolved
Resolved in Pega Version 8.4.4
The signature capture control was throwing a JSON parse exception when the value was set and section was refreshed. This was caused by the signature for PIMC passing incorrect data which Preview could not parse, and has been resolved by ensuring the correct data for PIMC local store.
INC-179106 · Issue 662617
Null data page check added for DataPageTelemetryImpl
Resolved in Pega Version 8.7
Recent work was done to modify the StreamChangeTracker trackValueChanges API to return false when invoked for properties of mode page. An additional null check has been added in DataPageTelemetryImpl.recordDataPageLoaded to handle a null pointer exception caused by null data page definitions.
INC-231704 · Issue 741219
Email template fragment updated to correct footer handling
Resolved in Pega Version 8.8
After creating a new Email correspondence rule and configuring the place holders as per the selected template, when the preview was rendered the "Footer" verbiage was being displayed irrespective of the footer region configurations. This has been resolved by updating the template fragment.
INC-225615 · Issue 725299
BAC updated for delegated circumstanced decision table rule
Resolved in Pega Version 8.8
An unregistered request error was encountered while launching the DelegatedRulesPage harness when pyBlockUnregisteredRequests >=1. This was traced to a delegated circumstanced decision table rule which caused a request error for the @baseclass.pzLookupCircumList activity, and has been resolved by updating the BAC handling for this activity.
INC-179683 · Issue 664452
Handling added for decoding file names containing umlauts
Resolved in Pega Version 8.7
Two issues were seen with file names that contained an umlaut: When sending file with an umlaut in the name via PegaCHAT, the error "Failed to load resource: the server responded with a status of 404 (404)" appeared on the Client side and a preview was generated. On the Agent side, the message was sent but attempting to open it resulted in an error that the file did not exist. This was traced to the unescape javascript API returning the wrong decoded values if the encoded value of an umlaut character was sent, and has been resolved by adding a safe check to avoid a malformed URI. Second, an image was not displayed in the Rich Text Editor if the image name contained the ä or Ä character in it. Investigation showed the activity parameters were being changed when it was invoked from the script. If the file name sent was "aysnÄ1626292145235.png" it was encoded to "aysn%C3%841626292145235.png" as expected, but when the parameter was passed to the Activity the value further changed to "aysn%C3%83%C2%841626292145235.png", causing the file open failure because the names did not match. To resolve this, code has been added which will correctly decode the encoded values of umlaut characters.
INC-187039 · Issue 678865
Handling added for decoding file names containing umlauts
Resolved in Pega Version 8.7
Two issues were seen with file names that contained an umlaut: When sending file with an umlaut in the name via PegaCHAT, the error "Failed to load resource: the server responded with a status of 404 (404)" appeared on the Client side and a preview was generated. On the Agent side, the message was sent but attempting to open it resulted in an error that the file did not exist. This was traced to the unescape javascript API returning the wrong decoded values if the encoded value of an umlaut character was sent, and has been resolved by adding a safe check to avoid a malformed URI. Second, an image was not displayed in the Rich Text Editor if the image name contained the ä or Ä character in it. Investigation showed the activity parameters were being changed when it was invoked from the script. If the file name sent was "aysnÄ1626292145235.png" it was encoded to "aysn%C3%841626292145235.png" as expected, but when the parameter was passed to the Activity the value further changed to "aysn%C3%83%C2%841626292145235.png", causing the file open failure because the names did not match. To resolve this, code has been added which will correctly decode the encoded values of umlaut characters.
INC-207009 · Issue 718286
Explicit expiration added to avoid searching for expired requestor
Resolved in Pega Version 8.8
A login page was taking long time to display. This was traced to pre-authentication cookie in the browser pointing to the requestor object on the server which triggered a lookup across the entire cluster of servers to find the requestor. This was not only taking time, but the attempt to find the requestor in the cluster would always fail to return results as the requestor was not passivated but instead removed after two minutes. To resolve this, an expiration has been added to the Pega-RULES cookie when the value is pre-authenticated. The time to expire is derived based on the short-lived requestor time for unauthenticated requestors + 1 minute, and will be 2 minutes by default. This will avoid searching for a requestor across all nodes in cluster when the requestor has already timed out and been destroyed by server.