SR-127838 · Issue 194658
Parse XML validation default set to "Never"
Resolved in Pega Version 7.1.8
In some cases, the parse XML rules function was not correctly mapping all of the input types. The root cause for the different failure modes seen was found to be that validation was set to "Always" by default, and the rule data did not reflect this until after a manual Save or Save-As. The default has now been set to "Never", and can be manually adjusted to "Always" or "When" as desired.
SR-127237 · Issue 189891
Time-related RUFs now use operator's time zone
Resolved in Pega Version 7.1.8
Date properties and Time properties were taking their reference from the server's default time zone, which created unexpected behaviors for operators in other time zones using start and end date functions. This has been resolved by updating the time-related RUFs to use the operator's defined time zone
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-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.
SR-128634 · Issue 195936
Enhanced authentication setting carryover
Resolved in Pega Version 7.1.8
An issue was found with calling out-of-the-box authenticated activities from unauthenticated service activities. For example, when the declare page reload was triggered by a SOAP request (e.g. soap request creates new work which refers to the declare page), the report definition failed with an error saying that the requestor was not authorized to execute pxRetrieveReportData. This happened even though the SOAP Service Package and data page load activity had been set up to not require authentication. This authentication conflict was caused by the rule resolution disregarding the initial setting skipping authentication when it encountered the authentication requirement for the pxRetrieveReportData activity. This has been resolved by setting the authentication requirement to be applied to all rule execution in the same requestor.