SR-127799 · Issue 192294
Included CMIS library updated
Resolved in Pega Version 7.1.8
Using Connect-CMIS Rule form, attempting to get a list of Repositories from a CMIS Server that allows Web service binding with Basic Authentication was failing with 401 - Unauthorized error. The getRepository operation succeeded when using SOAPUI or Apache Chemistry CMIS client Workbench. This was a defect with the particular CMIS library version included with Pega 7.1.7, and has been corrected by updating to a revised version.
SR-127838 · Issue 194007
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-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-131162 · Issue 201045
Corrected inheritance for Data classes
Resolved in Pega Version 7.1.8
After migration, an API used to pull the list of concrete classes from RootClass Work- was pulling an additional class (Data-Portal-Padportal) when work- was supplied as an argument for rootclass. This additional class caused issues with reports due to it pointing to pr_history_data table and looking for non-existent columns. These inheritance issues have now been corrected.
SR-131162 · Issue 201046
Corrected inheritance for Data classes
Resolved in Pega Version 7.1.8
After migration, an API used to pull the list of concrete classes from RootClass Work- was pulling an additional class (Data-Portal-Padportal) when work- was supplied as an argument for rootclass. This additional class caused issues with reports due to it pointing to pr_history_data table and looking for non-existent columns. These inheritance issues have now been corrected.
SR-127035 · Issue 193206
Improved opening custom flow rules with Microsoft Internet Explorer 9
Resolved in Pega Version 7.1.8
Opening up a flow rule with many sub-process references was taking an excessive amount of time when using Microsoft Internet Explorer 9 due to general browser slowness and the system loading all referenced flow rules at that time. This has been resolved by tuning the JavaScript code to improve the performance of the viewer and to disable drilldown functionality from the server.
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.