SR-C47580 · Issue 386290
Assertion Type results count updated to allow input of filter class for validation
Resolved in Pega Version 8.1
When using the assertion type result count and trying to validate a property in pxResults class, it was not possible to save the test case. This was due to the system trying to validate the class in a rule under test class and not pxResults class. To fix this, the AUT rule form has been updated to show the filter class filter class text box so that when no class is been populated the filter class can be entered to enable selecting the properties from this class inheritance.
SR-C47633 · Issue 386353
Agent management made more resilient against DB connection errors
Resolved in Pega Version 8.1
Intermittently after a database interruption occurred, agents would end up in a state where they did not run. When viewed via SMA they appeared to be running, but the next runtime was blank and the agent did not execute. Attempts to stop/restart an affected agent yielded an error, but restarting the system put the agents back into a operable state. This was a corner case caused by a DB connectivity issue where agents were first being stopped and then attempts to instantiate AgentNotification() also failed due to the DB connectivity issue. To resolve this, AgentNotification will be instantiated during AgentQueue creation itself so it will remain available. All exceptions /errors in AgentNotification will be logged.
SR-C47733 · Issue 389568
Handling added to maintain grid size when resize is run in a hidden DOM
Resolved in Pega Version 8.1
Grid layout height was getting set as 2px after opening a work item. This was traced to Grid height being reduced when the grid is in a hidden DOM and the resize handler was fired after a new tab was opened, making the grid content not visible. To correct this, a check has been added for contentHeight to avoid setting zero height when this code is run in hidden DOM.
SR-C47868 · Issue 391533
Corrected code error in executeMBeanOperation
Resolved in Pega Version 8.1
An null pointer exception was generated while trying start listeners from executeMBeanOperation. This was due to an error in the code related to String names in ListenerManagementAPI, and has been fixed.
SR-C48072 · Issue 388475
Corrected URL formation problem when using Tomcat
Resolved in Pega Version 8.1
A blank screen was seen when trying to open Decision Table headers, and the color picker pop-up was blank when trying to choose a color for the skin. This was traced to an incorrect URL formed when using Tomcat, caused by the prweb/hash being appended twice in the URL. The root cause was unnecessary decoding of extURL in 'pzDisplayModalDialog' , and this has been fixed by adding the proper urlCrossScriptingFilter.
SR-C48084 · Issue 388816
Repaired Activate Feature in revision management
Resolved in Pega Version 8.1
After creating a revision package jar and importing it into the environment, attempting to Activate the revision to the users resulted in the error message "There are changes from another session. Replaced with latest revision data." This issue was traced to an error in the pyActivateToAll activity from Pega-DecisionManager:07-10-31, and has been fixed.
SR-C48633 · Issue 390528
Missing rules will be inserted into pr4_rule_vw table
Resolved in Pega Version 8.1
On running ExposeCols from prpcutils, if pr4_rule_vw table was truncated or had some rules missing, then the records were not being updated. Logging indicated there were view rules which were present in pr4_rule_vw but not present in the actual class, causing a duplicate key exception when the system tried to insert the same rule again into the pr4_rule_vw table. Previously, ExposeCols functionality always updated the rule record and its corresponding Data-Rule-Summary record but would never insert a new rule or Data-Rule-Summary record. This meant that if the pr4_rule_vw table was truncated before running the column expose, none of the rows were getting updated as the table was empty. To resolve this, if the rule is missing in the pr4_rule_vw table, insert queries will be executed and the rule will be populated in the corresponding Data-Rule-Summary record.
SR-C49089 · Issue 388092
File input handling added to trigger file browsing popup
Resolved in Pega Version 8.1
When the 'Browse' icon received focus in the operator ID rule with tab navigation, pressing the 'Enter' key did not open the file browsing popup. This was due to the Enter event not working with file input, and a check has been added for file input in pzega_ui_events to allow it as an enter key event.
SR-C49089 · Issue 388866
File input handling added to trigger file browsing popup
Resolved in Pega Version 8.1
When the 'Browse' icon received focus in the operator ID rule with tab navigation, pressing the 'Enter' key did not open the file browsing popup. This was due to the Enter event not working with file input, and a check has been added for file input in pzega_ui_events to allow it as an enter key event.
SR-C49097 · Issue 389781
Added missing tooltips for JAWS to read "+" and other buttons in Operator ID and Access Group rules
Resolved in Pega Version 8.1
A few buttons like "+", "Open", etc., were being read by JAWS as unnamed buttons in operator ID and Access Group rules. This was due to missing Tooltips, and has been corrected.