SR-127549 · Issue 190837
Improved processing of WSDL for the Create SOAP Integration wizard
Resolved in Pega Version 7.1.8
When running the Create Soap Integration wizard for a selected operation from the WSDL, the wizard was not only generating the necessary rules for the selected operation, but for all operations in the WSDL. To address this, when processTypeContentsAndRelatives is processing a parent type, it now skips type substitutions of the parent.
SR-127743 · Issue 193331
Trace rule servicetype set for Service-File
Resolved in Pega Version 7.1.8
'Trace rule' for the Service-File is not working even though 'Trace rule' for Pega Service type worked correctly. This was caused by an inability to trace the Service-File due to not setting the servicetype, and the API has been updated to explicitly set the servicetype as "File" in ServiceAPI class.
SR-127829 · Issue 192723
Magnifying glass popup fixed for XML-stream element mapping data
Resolved in Pega Version 7.1.8
After importing XSD through the Connector and Metadata Wizard, double-clicking on an element-mapping to bring up the magnifying glass popup returned the error "Unable to open the rule as Base Class Value is empty". This was traced to a recent change that converted Ruleforms from form-based to harness-based, and OpenRuleAdvanced control has been modified to handle the XML stream information correctly.
SR-127853 · Issue 193472
Locking updated for hidden elements in Data Type records
Resolved in Pega Version 7.1.8
If Data Type records were being edited, the lock on the row being edited was not released unless a change was made. This led to locks being left over once the operator has closed the Data Type and other operators were prevented from editing those rows. The problem was that change tracking was not getting invoked for the hidden elements present in the section for each row, and this has been added.
SR-127853 · Issue 193468
Locking updated for hidden elements in Data Type records
Resolved in Pega Version 7.1.8
If Data Type records were being edited, the lock on the row being edited was not released unless a change was made. This led to locks being left over once the operator has closed the Data Type and other operators were prevented from editing those rows. The problem was that change tracking was not getting invoked for the hidden elements present in the section for each row, and this has been added.
SR-127880 · Issue 193696
Rest Connector wizard updated for custom naming conventions
Resolved in Pega Version 7.1.8
After migrating, a data model generated using the Rest wizard would fail when attempting to map a response using pxResults of Code-Pega-List. The mapping logic has been updated to better handle custom naming conventions.
SR-128102 · Issue 193767
Resolved RD filter prompt not showing
Resolved in Pega Version 7.1.8
The Report Definition filter prompt was not displayed even when 'Prompt for filter changes' was checked. This was an issue with PXSHOWREPORT not using the correct step page, and has been fixed.
SR-128171 · Issue 196940
Drill down corrected for leaf node in RD summary report
Resolved in Pega Version 7.1.8
When a summary type report definition as used to source a tree grid, double-clicking a leaf node in the tree did not open the associated detailed view from the report definition. This was traced to a missing null check for the clipboard in the drill down activity, and has been resolved.
SR-128206 · Issue 192572
Added null check for RD column containing a function
Resolved in Pega Version 7.1.8
When running a report definition with a column that has a function, it showed the error "illegal zero-length identifier". This was due to the alias name for the Rule-Alias-Function with return type 'True or False' being empty in the pxSQLStatementPost function, and a check has been added to handle this.
SR-128296 · Issue 197865
Modified SOAP envelope activity to handle Axiom bug
Resolved in Pega Version 7.1.8
The version of InvokeAxis2 provided in updates was encountering a bug with Axiom's implementation for adding OMNodes and not all header elements were being mapped to their SOAP request. To resolve this, the pzAddCustomeHeaderstoSOAPEnvelope activity has been updated to add a line of code to remove a node from its child iterator once it is added.