SR-C38299 · Issue 377521
Handling added for data flow thread hang
Resolved in Pega Version 8.1
If there were errors on some partitions, the data flow was hanging. Handling has now been added for system failures in inputSource so the flow will complete and report errors.
SR-C38355 · Issue 376510
"403 - Forbidden" error replaced with "404 - Not Found" for better security
Resolved in Pega Version 8.1
Previously, invalid path information sent for a static content request resulted in a "403 - Forbidden" response that revealed the existence of the directory, even though access is not allowed. For better security, a "404 - Not Found" response status code will be issued for a forbidden resource.
SR-C38450 · Issue 379292
StartupDelay parameter added to allow spacing threads to improve database performance
Resolved in Pega Version 8.1
When starting a data flow with DBDataSet as source shape, all data flow nodes (threads) started hitting the Database at the same time, overloading the system and causing delays for other requests. To resolve this, a new RunOption has been added; pyStartupDelay will add a delay between each thread starting. For example, when setting the delay to 2 seconds, thread 1 will start immediately, thread 2 will start after 2 seconds, thread 3 after 4 seconds etc. In this fashion only one thread at the time will start hitting the DB in a distributed context.
SR-C38510 · Issue 383350
Next >> buttons localized for French
Resolved in Pega Version 8.1
Next >> buttons were not getting translated when using the French locale. This has been corrected by updating the pyButtonLabel parameter.
SR-C38824 · Issue 383747
Fixed warning issue for opening a harness that's already open
Resolved in Pega Version 8.1
When launching the harness using Harness action, there was no warning displayed when trying to open the harness which is already open. This was caused by an incorrect parameter being passed to the "showConflictDialog" method call, and has been corrected by modifying the pzpega_ui_dynamiccontainer.js file "display" method to pass "viewHost" variable instead of "hostName" as the first parameter to the "showConflictDialog" method call.
SR-C38825 · Issue 374870
Corrected bulk actions 'select all' behavior
Resolved in Pega Version 8.1
BulkActions:"Select All" was not considering records in all of the pages. This has been corrected.
SR-C38825 · Issue 377452
Corrected bulk actions 'select all' behavior
Resolved in Pega Version 8.1
BulkActions:"Select All" was not considering records in all of the pages. This has been corrected.
SR-C38860 · Issue 377053
Hotfix manager missing class handling improved
Resolved in Pega Version 8.1
A missing class triggered a failure to open that class during hotfix scanning, resulting in an error within the hotfix manager installer which caused the schema changes to be bypassed automatically. This resulted in an error message being added to the running step page, and the activity running the scan handled the error by exiting the activity. This skipped the one remaining step in the activity - preparing the schema changes. Thus, schema changes were not installed. To correct this, during system scan error messages will be prevented on the step page as it can not be guaranteed that all instances will be available. The system also will no longer exit the activity on error as there is no specific error handling for the exit available.
SR-C38902 · Issue 377561
Parameter added to support Hotfix manager access group
Resolved in Pega Version 8.1
Previously, there was no provision for Hotfix Manager functionality to accept the access group as the parameter and run it in the access group context. In addition, Cloud customers were not able to specify a pega.username and pega.password. Attempting to do either of these resulted in an exception. In order to support these uses, a new access group parameter has been added to the prpcUtils.properties for manage hotfix functionality If an access group is provided that will be used; otherwise it will attempt to use PRPC:Administrators, then fallback to using the BATCH requestor’s AG (PRPC:Agents).
SR-C38931 · Issue 382819
Corrected Listener open error when using ListenerManagement page
Resolved in Pega Version 8.1
When clicking on any Listener on the ListenerManagement landing page, it displayed the following error page: "Unable to open instance - Possible causes may be (1) Rule may no longer exist. (2) Availability of the rule may be set to No/Draft, Blocked or Withdrawn. (3) Circumstance of the rule may be preventing access. (4) Current date is not within the date range specified in the rule. (5) Access group or role may not have the appropriate privileges to open the rule." However, the same rule could be opened from Records Explorer. Analysis found that the .pyListenerInsName property used to open the listener rule was blank in the pyListenersList in ListenerManagementPage; initialization of the mListenerInsName field has been added to correct this issue.