SR-C75689 · Issue 413136
restored to correct "pg empty after db.open" errors
Resolved in Pega Version 8.1.2
When opening the data page D_RepositorySettings, the error "pg empty after db.open" appeared in the logs. This was due to the data page referring to the files webwb/zchecked.gif and webwb/zchecked.gif in many sections of the data page rule form despite these files having been removed as part of a recent cleanup meant to reduce storage requirements. In order to resolve this error, the zunchecked.gif and zchecked.gif images have been added back and the error message generated in the RUF pzGetbase64encodedImagehas been improved to add the target filename: "error occurred while opening the image:webwb/zunchecked.gif"
SR-C53866 · Issue 402883
Added handling for custom skin using the $ symbol for value
Resolved in Pega Version 8.1.2
After upgrade, using a custom style sheet to display the $ symbol prior to values being shown or entered caused the application skin to not log and throw an error. This was caused by a missed use case for adding $ in css :before or :after content due to a dependency on this "$" notation for fetching right mixin color from skin color. The array index out of bounds exception was generated by the statemachine parser while handling special characters because it considered the quotes of csscontent to be corrupted. To resolve this, an extra check has been added for handling """ and "'" cases in cssCustomParser.java and junits have been updated.
SR-C64243 · Issue 412374
Data flow region switching method added to prevent truncating event strategy data
Resolved in Pega Version 8.1.2
An enhancement has been added to allow customers to switch data flow execution from one region to another without clearing event strategy data. This process looks like (1) Dataflow is started on one region. (2) Dataflow is paused in same region. (3) Dataflow is started in second region. Previously, step 3 would delete the existing event strategy data. To prevent that, a new run option has been added named 'pyDataFlowStorageTruncateOnStart'. By default, this is set to true and truncation will occur. If set to false, the event strategy data will not be deleted.
SR-C51798 · Issue 412382
Modified pzPopulateTrainingandTestDetails to resolve input error in test model
Resolved in Pega Version 8.1.2
After creating a text model, trying to update it resulted in errors. This was caused by the input bean for pzPopulateTrainingandTestDetails getting reset and causing a nullpointerexception while trying to load the spell checker because the taxonomy data was empty. This has been fixed by ensuring the input param object is created after setting the taxonomy data. A null check has also been added in the creation process of the input param object in pzPopulateTrainingandTestDetails.
SR-C70539 · Issue 412522
Open API passes 'true' for aUnlockOnCommit parameter to minimize pr_sys_locks table filesize
Resolved in Pega Version 8.1.2
The Archive/Purge Wizard was not removing the locks acquired during the execution from the pr_sys_locks table, resulting in locks remaining in the table for up to three days. This could potentially cause an enormous filesize and lead to other processes failing to acquire locks due to contention on the table. To resolve this, the system will pass 'true' for aUnlockOnCommit parameter on the open API so that the lock is released on commit of the deferredDelete on purged instances.
SR-C60247 · Issue 413680
pzRuleFormToolbarPopulateActions works when @ is present in the operator ID
Resolved in Pega Version 8.1.3
Using pzRuleFormToolbarPopulateActions to get all the versions of the rule was not working as expected if the '@' symbol was present in the user ID. This was caused by the Rule-.pzRuleFormToolbarPopulateActions activity not forming the private rules correctly in this use case, and has been fixed.
SR-C65381 · Issue 415189
Added check for pyType when refreshing the Declare_pyDisplay Page
Resolved in Pega Version 8.1.3
The standard behavior of clicking a link in the left navigation of the Pega Diagnostic Cloud manager portal is to open a new thread which automatically adds/updates the Declare_pyDisplay Page. However, in some circumstances opening the work items and clicking the navigation link followed by a refresh/F5 from the Google Chrome browser caused the Declare_pyDisplayDatapage to become corrupted and either froze the screen or caused a new popup window to open. This was traced to a situation where the parameter "pyType" was not present in one of the cases, causing the system to rely on "harnessName" instead. To resolve this, a check has been added that will retrieve pyType from the docObj parameter page of the pzpega_ui_dynamiccontainer.js file if needed.
SR-C67397 · Issue 416252
Added check for missing rule data when using abstract class in CSS
Resolved in Pega Version 8.1.3
Including CSS optimization with abstract class in the Advanced tab of the 'Add Optimization' Screen resulted in a Null pointer exception error. This has been resolved by adding a check for missing data from a rule to make the system more resilient in its handling of a corrupt flow-action clipboard page.
SR-C68069 · Issue 416698
Page group use added to referenced properties context for RDL
Resolved in Pega Version 8.1.3
After upgrade, a stack mismatch error was generated by a previously-working configuration that used a nested RDL with a section under Work- class that itself contained an RDL with Data- property that then included a section from Data -- class which contained another RDL that referred to the Work- Page Group. This error was caused by the use case of page group being missed during implementation of referenced properties in ContextProcessor processListNode, which has now been resolved.
SR-C68993 · Issue 416163
Expression exngine correctly evaluates boolean type property with expression
Resolved in Pega Version 8.1.3
When using a dynamic layout with a visibility condition expression and 'Run Visibility Condition on client' checked, a condition such as .VehicleDetails != '' && .VehicleDetails = true was not being evaluated as expected after upgrade. This issue was related to changes made to the expression engine to get the initial evaluation result at the server side, and was caused by a missed use case for a boolean type property with expression. This has been corrected.