SR-122761 · Issue 188488
Tuned logic for propagating shape flow actions
Resolved in Pega Version 7.1.8
When a work flow has moved from an assignment shape to an assignment service shape, the other actions menu was showing the flow action from the previous assignment. Work-.Connect activity invoked populateFlowActions function to populate the assignment local action. By the time this was invoked, the pxFlow() was not updated with the correct assignment details and the old assignments actions were being populated. This has been fixed by tuning the logic of invoking populateFlowActions.
SR-126121 · Issue 189977
Improved Global Search box dismissal on iPad
Resolved in Pega Version 7.1.8
On an iPad, prforming a search with any application that shows the global search control in its header displayed a pop-up that could not be dismissed by tapping on the application below the search box. This issue occured when the script pega_desktop_AppControllerLite.js is included in the header section of the harness.To address the problem, the event binding logic for search on mobile devices has been updated to listen for a tap event instead of a click event.
SR-128430 · Issue 194956
Pagination removed from OwnersList to facilitate large category lists
Resolved in Pega Version 7.1.8
After having created a large number of categories from the "Reporting" landing page, the list of available owners was not the expected one when creating a new shortcut. The owner drop down list is generated by the ListView called "Rule-Category.pzGetCategoryOwnersList." Unfortunately this ListView is a FINAL rule and paging was enabled with a default count of 50 entries. In order to allow for customizations like the above, OwnersList has been modified to disable paging.
INC-135335 · Issue 588512
Parent flow next step will take precedence over sub-process
Resolved in Pega Version 8.3.5
A Breadcrumb configured in the screen flow was not displaying at the last assignment when there were multiple embedded sub processes and the last assignment was called in a sub process. This was traced to the parent flow next step information not being passed due to the next step in the sub process being marked as an end shape. To resolve this, the pzFlowSteps7 html control has been updated to pass the parent flow's next step information in this situation.
SR-D84126 · Issue 545039
Resolved delegated data type exception for new line character
Resolved in Pega Version 8.4.2
After delegating two data types to certain access groups, the data type appear with the specified detail in the case manager portal under the configurations tab but the exception "Class not defined in dictionary" appeared when the edit button was clicked. This was related to the handling for parseJSON, and has been resolved by adding handling for escaping new line characters in the catch block of correctActionArgs method inside the ui_events file.
SR-122732 · Issue 182663
Cleaned up error logging for Oracle split schema multi-tenant upgrade
Resolved in Pega Version 7.1.8
When upgrading a multi-tenant environment with an Oracle split schema database, the log file was filling with warning messages on all tenant IDs during Rules upgrade. While errors are expected if there are tenants in the database that are no longer valid, the failure to resolve the tenant ID was being reported twice. In order to smooth the upgrade process, the log messages in this environment have been changed from warnForced to info, and each error will only be logged once.
SR-124206 · Issue 186503
Clarified handling of unlocked work objects in multinode environments
Resolved in Pega Version 7.1.8
Release lock was not working correctly on a multinode environment. When trying to release the lock from same operator different requestor from different nodes, the error "Unable to unlock this work object" was generated. In a multinode environment, system pulse takes time to update the cache across the nodes, hence the option is not effective immediately. Messaging has been updated to reflect this delay. Once System pulse executes then other requestor will be able to work on this item.
SR-124245 · Issue 188290
Clarified handling of unlocked work objects in multinode environments
Resolved in Pega Version 7.1.8
Release lock was not working correctly on a multinode environment. When trying to release the lock from same operator different requestor from different nodes, the error "Unable to unlock this work object" was generated. In a multinode environment, system pulse takes time to update the cache across the nodes, hence the option is not effective immediately. Messaging has been updated to reflect this delay. Once System pulse executes then other requestor will be able to work on this item.
SR-128178 · Issue 192632
DataOnly upgrade modified to handle pr_data_products tables
Resolved in Pega Version 7.1.8
Running the upgrade.bat dataOnly true to upgrade the data schema failed while trying to insert values into the pr_data_products table. Promoting upgraded rules schema to higher environments and then upgrading the data schema is a supported upgrade procedure, but the dataOnly upgrade did not take this into account. The system has been updated such that when migrating post upgrade, it will not migrate pr_data_restore and pr_data_products tables and will fail if there are uncommitted hotfixes.
SR-130751 · Issue 198798
Clarified handling of unlocked work objects in multinode environments
Resolved in Pega Version 7.1.8
Release lock was not working correctly on a multinode environment. When trying to release the lock from same operator different requestor from different nodes, the error "Unable to unlock this work object" was generated. In a multinode environment, system pulse takes time to update the cache across the nodes, hence the option is not effective immediately. Messaging has been updated to reflect this delay. Once System pulse executes then other requestor will be able to work on this item.