SR-A7205 · Issue 219651
Rule history included in save-as
Resolved in Pega Version 7.2
After upgrade, using "save as" on a rule from a particular version was not maintaining the rule history correctly. Information was not included about the version from which it was being saved (previous version and ruleset, but did display the check-in comments. This was traced to an error with passing the History Memo as parameter when calling the SaveAs activity, and has been fixed.
SR-A12345 · Issue 224099
Improved visibility for roles associated with objects
Resolved in Pega Version 7.2
Issues were encountered while attempting to access roles associated with objects on the access role name rule form if 'Rule-Access-Deny-Obj' was used. Not all of the ARO and ADO definitions for the Access role were visible and the error "Failed to find a 'RULE-OBJ-FLOWACTION' with the name 'PZADDMODIFYROLE' that applies to" was generated. This has been corrected by adding and updating the required rules to support displaying both Access role objects and access deny objects on access role name rule form: the grid will be updated to display both RARO and RADO, but to simplify, the add-a-row functionality at the bottom will be limited to RAROs only.
SR-A8289 · Issue 218291
Improved visibility for roles associated with objects
Resolved in Pega Version 7.2
Issues were encountered while attempting to access roles associated with objects on the access role name rule form if 'Rule-Access-Deny-Obj' was used. Not all of the ARO and ADO definitions for the Access role were visible and the error "Failed to find a 'RULE-OBJ-FLOWACTION' with the name 'PZADDMODIFYROLE' that applies to" was generated. This has been corrected by adding and updating the required rules to support displaying both Access role objects and access deny objects on access role name rule form: the grid will be updated to display both RARO and RADO, but to simplify, the add-a-row functionality at the bottom will be limited to RAROs only.
SR-A7642 · Issue 218030
Code added to support automated unit tests on Microsoft Internet Explorer 11
Resolved in Pega Version 7.2
When attempting to create automated tests for a decision table, the dialog to create the test cases was coming up without the version dropdown box. This was traced to a null object being returned for the WebWB_New_Available rule due to Element.all support being dropped by Microsoft Internet Explorer 11. To resolve this, that rule has been modified in order to work on all versions of Microsoft Internet Explorer .
SR-A10487 · Issue 221146
Resolved BIX command line NPE for username/password
Resolved in Pega Version 7.2
Attempting to run a BIX extraction from the command line without specifying -a/-p (username and password) parameters failed with a NullPointerException. This has been corrected.
SR-A11445 · Issue 222408
Wildcard extraction trims extraneous spaces from BIX output
Resolved in Pega Version 7.2
An extra space was being appended to the XML output file name when %t was used. The ExtractImpl.replaceWildCards() method has been updated to trim any additional spaces at the end.
SR-A12684 · Issue 224534
Extracts count corrected when using XML as output
Resolved in Pega Version 7.2
While running an extract using XML as output, a difference was observed in the number of records being extracted when compared with 'Database Schema' as output. The Pega-BIX logs contained failed records with 'Index out of bounds' exceptions. This was traced to missing handling for the value group property references in this scenario, and has been corrected.
SR-A10974 · Issue 223153
BIX Manifest enhanced to include fully qualified property names
Resolved in Pega Version 7.2
If an page list property with the same name existed under two levels in the extracted data (specified in the extract rule multiple times), there was no way to differentiate them when viewing the BIX Manifest file. To resolve this, an enhancement has been added to ExtractImpl to include the fully qualified name for the property.
SR-A12324 · Issue 226656
XML manifest output support added for nodes with 'px' naming schemes
Resolved in Pega Version 7.2
When the 'pxSkillsRequired' value Group property was part of the properties being extracted, node names starting with px generated an exception while writing to XML manifest output format. Handling has now been added to support node names starting with 'px'.
SR-A14732 · Issue 228331
pxObjClass correctly applied to nodes for extract rule form
Resolved in Pega Version 7.2
If pxObjClass was selected for the top level node in the extract rule form, BIX would use use pxObjClass for all of the embedded nodes irrespective of whether pxObjClass was selected for the embedded node or not. If pxObjClass was not selected in the top level node but then selected for all of the embedded nodes, then the system would not use pxObjClass for any of the nodes. To correct this, changes have been made to ExtractImpl and BIXXMLStream so that pxObjClass will be added to those nodes for which pxObjClass property has been explicitly selected in the extract rule form.