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-B71423 · Issue 319981
Localization added to pyAccountSettings field labels
Resolved in Pega Version 7.4
Field label localization for the pyAccountSettings section rule has been added to the Pega-IntegrationArchitect ruleset.
SR-B54277 · Issue 336406
Trimmed unneeded properties from doUIAction call
Resolved in Pega Version 7.4
Null pointer exceptions were generated when relaunching the manager portal after saving a work-object, and the error "Request-URL Too Large. The requested URL's length exceeds the capacity limit for this server" appeared. This was traced to the number of properties included in the doUIAction call; unnecessary parameters have been removed to resolve this issue.
SR-B66164 · Issue 325166
Handling improved for pzActiondropdown's Action label value
Resolved in Pega Version 7.4
When an alternate flow action was picked from LocalAction's list and then submitted, the presence of any page-set messages would cause the submission to fail and the flow remained on the same flow action. This was an issue with handling the changed value of the FlowAction label, and the pzActionDropdown control has been modified to get the correct pyDefaultActionIndex parameter value.
SR-B70422 · Issue 326897
Removed unnecessary add/delete history entries related to empty page properties
Resolved in Pega Version 7.4
The field level auditing configured for page group or list property types was creating multiple add and delete entries in the history of the case even though the pagelist/pagegroup had not been modified. This was traced to method used by the pagelist change audit process to compare current pages to the previous value of the pagelist pages: during pagetostring conversion, sometimes the empty properties in page are present in the String and sometimes they are not, resulting in a difference that generated the non-essential audit entries. This has been fixed by changing the getProperty references in getPageAsString function to use getIfPresent instead. Null checks have also been added.
SR-B70595 · Issue 328754
Out of box REST API creates Page Lists with pxObjClass
Resolved in Pega Version 7.4
Page-Merge-Into was implemented in such a way that the pxObjClass was added for a page but not for a Page List until the case was created. This interfered with validating pagelists and identifying problems with the message data that would allow the case to be rejected before creation. To allow for more flexibility, the pzCreateCaseInternal activity contains an added a property-set so that the pxObjClass is updated on embedded pages.
SR-B74583 · Issue 325617
SendEmail smart shape fixed to populate PartyRole correctly
Resolved in Pega Version 7.4
Due to issues with populating the pxPartyRole property, emails were not being sent to all members in a repeat party after upgrading. This was traced to a missing call in the modified SendEmail smart shape, and has been fixed.