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.
SR-C38965 · Issue 378228
Hotfix Scanner updated to clarify the status of uncommitted but superseded hot fixes
Resolved in Pega Version 8.1
The Hotfix Manager scanner identified any uncommitted but superseded hotfixes as committed even though they were not actually committed. This occurred if any part of a hotfix had been superseded and did not require the entire hotfix to be superseded. To clarify, superseded hot fixes means the system already has the hot fix installed in it. During import of new hot fixes, if it has any superseded hot fixes those hot fixes cannot be rolled back. This means if the system is scanned after the rollback, it considers all the superseded hot fixes as committed once as there is nothing to rollback. This is "as-is" behavior, but the way the information was presented was causing some confusion. In order to ensure the status is easy to understand, the metadata will be saved so that superseded but uncommitted hot fixes will not be shown as committed.
SR-C38997 · Issue 379285
Mobile buttons revised to workaround iOS browser click bug
Resolved in Pega Version 8.1
When using the iOS browser, buttons were getting stuck or frozen and requiring multiple clicks to execute. This was traced to an error in the iOS browser version 11.4 where click events are triggered with event.timeStamp as a negative number. To avoid this, the system will not rely on event.timestamp, but will instead get the current datetime and maintain it in prevEvent object.
SR-C3904 · Issue 353053
JAWS able to read validation errors on child of modified element
Resolved in Pega Version 8.1
After overriding some JS functions in UserWorkForm to prepend the field name to the validation message, JAWS was not reading out the validation errors. This occurred because JAWS was not able to read an alert from the child of a modified element, and a role alert has been added on the parent div to enable this use.