INC-220251 · Issue 732073
New prconfigs added to handle lob closed error
Resolved in Pega Version 8.8
BIX extraction was encountering the SQL error "Invalid operation: Lob is closed" while reading the BLOB, but the rest of the records were able to be extracted. This was traced to previous work done to resolve an issue where Oracle temporary space used to write the LOB was not freed up after writing records to Log-Service-File when using OJDBC8 or OJDBC10 versions. This change caused an issue for DB2 where the freed BLOB was still trying to be extracted. To address this, new prconfig settings have been introduced to control freeing BLOB memory. If the error is seen regarding the lob being closed, add and disable these settings (set value as false) in the pronfig.xml file. DATABASE_MANAGEMENT_FREELOB: settingName: database/management/freeLOB description: If this flag is set to false, it controls the free memory calls defaultValue: true DATABASE_MANAGEMENT_FREEPAGEDBMAPPERLOB: settingName: database/management/freePageDBMapperLOB description: If this flag is set to false, it controls the free memory calls. defaultValue: true Following this change, restart the server.
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-220652 · Issue 721384
Added explicit clearing for AsyncServiceManager cache
Resolved in Pega Version 8.8
Heap size for multiple JVMs increased after update. Investigation showed data pages loaded via Load-DataPage during service processing using requestor pools were cleared after each service interaction but the AsyncServiceManager cache was not cleared. To resolve this, an update has been made that will clear the async cache when the requestor is returned and when flush all is called.
INC-220789 · Issue 720198
Editable data page properly refreshes after interaction
Resolved in Pega Version 8.8
A data page using editable mode was adhering to the "Reload once per interaction" option used for readonly mode. This led to issues such as tables not refreshing after sorting or applying filters. To resolve this, refreshReloadInteraction has been updated to false when mode is not readonly.
INC-220837 · Issue 729122
Number formatting a separator corrected for Greece
Resolved in Pega Version 8.8
When the locale was set to el_GR, number formats for currencies in monetary digit grouping was using 3;2 formatting instead of 3, causing errors such as 10,00,000.00 being displayed instead of 1.000.000,00. This has been corrected.
INC-221950 · Issue 720052
SendEmailNotification activity updated for forgotten password flow
Resolved in Pega Version 8.8
The "Trouble logging in?" mechanism was not working after update due to the verification code not being sent to the user. This was an issue with security policy, and has been resolved by disabling the checkbox "Require authentication to run" for the SendEmailNotification activity in this scenario. The SendEmailNotification activity is used to send mails to the user during the forgotten password flow and requires the provision to run in an unauthenticated context for this usecase.
INC-223240 · Issue 723230
Added debug logging and exception recovery for unexpected data object
Resolved in Pega Version 8.8
When rules were complied in lower environment and deployed into production, they later became corrupted and system behavior changed. The error "Java generation failed: caught exception while expanding property pyGetCasePredictionsByClassName on page CurrentRecord" was generated. Investigation showed the auto-populate property pyGetCasePredictionsByClassName was attempting to get the metadata property "pzDataObjectParams": this was a string value in this scenario instead of the expected java object, and caused the exception. To resolve this, a debugger has been added which will check if the property is a java object or not. If it is not, the system will skip the processing and then display an error message with a stack trace.
INC-224034 · Issue 735692
Data page definition reload made more robust
Resolved in Pega Version 8.8
The data page was intermittently being removed from the cache. This was traced to the use of a thread from ThreadContainer to reload the data page definition: a null thread could be returned if the request came from a master agent, which would then cause the definition reload to fail. This has been resolved by updating the system to use the current thread in context to reload the data page definition.
INC-224268 · Issue 724023
Cleaned up outdated prprivcommon class references
Resolved in Pega Version 8.8
After update, an exception was generated related to FirstUseAssembler. This was a missed use case for the WriteEFormToFile activity from previous work which restricted loading classes from prprivcommon.jar, and has been resolved by removing references to the following classes which were made inaccessible by the changes to prprivcommon: com.pega.pegarules.storage.FileStorageManager com.pega.pegarules.storage.fs.resadaptor.RAFile com.pega.pegarules.storage.fs.resadaptor.OutputStreamWrapper
INC-225046 · Issue 729892
Currency Code updates
Resolved in Pega Version 8.8
A Section configured with an editable currency input using auto-formatting failed to render at runtime if configured using Type -> Number, Symbol -> Currency, Other currency, and Currency -> "USD". The error "Invalid Locale : USD" was logged. This was an unintended side effect of work done to configure currency codes for the Number control, and has been resolved by accounting for the locale settings and handling the condition for the error "Invalid local-USD" so that the the UI rendering appears as expected. In addition, when the Currency control was configured with editable mode "Editable" and "Display value using read-only formatting" checked, read-only formatting generation did not happen for the control. Entering a value and tabbing out caused the ReloadCell activity to return empty content, which resulted in the server returning full HTML markup with a message "Operation Successful". Because the ReloadCell activity handler expected only control markup with formatted value to be returned, the HTML markup containing inline CSS styles in it appeared in the Currency input field on tab out. There was a workaround of unchecking "Display value using read-only formatting" on the control's presentation tab, but this has been resolved by using Post value infrastructure to get the formatted value from the server.