SR-B35965 · Issue 302489
Fixed copy from data page with optional data mapping
Resolved in Pega Version 7.3
When 'Optional data mapping' was used on a pageList property with the 'copy from data page' option enabled, data was not getting populated to the PageList if the filtered result was page type. This was traced to an issue with optional data mapping in a keyed data page, and has been resolved by changing the function to add the indexed page instead of directly using the FilteredClipboardProperty.
SR-B16337 · Issue 287224
BIX TotalInserts and TotalInstance counts made consistent for nested pages
Resolved in Pega Version 7.3
The pxTotalInsertsCount and pxTotalInstanceCount values were being calculated incorrectly when using PageLists and a Page under those PageLists. This was a missed case, and the system has been updated to address it.
SR-B34230 · Issue 292359
BIX TotalInserts and TotalInstance counts made consistent for nested pages
Resolved in Pega Version 7.3
The pxTotalInsertsCount and pxTotalInstanceCount values were being calculated incorrectly when using PageLists and a Page under those PageLists. This was a missed case, and the system has been updated to address it.
INC-190380 · Issue 678643
CreateVersion rule updated for REST Integration Wizard
Resolved in Pega Version 8.7
When using a JSON response in the Create REST Integration wizard to generate the rules, the wizard displayed a null pointer exception during the final generation. The error pop up message "Generation process has been canceled and all created records have been removed" was displayed on the screen. This was traced to the REST Integration Wizard putting data rules in the wrong ruleset version when the context of both the Integration Layer and the Data Layer were configured to use an existing ruleset and to create a new version of that ruleset, and has been resolved by modifying the pzCreateVersion rule to support this.
SR-B5820 · Issue 276037
Properties of type Integer text value properly formatted
Resolved in Pega Version 7.3
Properties of type Integer text value were not properly formatted when set to property. This has been fixed by modifying the assembler code to pass the property type and use it properly for runtime mapping.
INC-196313 · Issue 688605
Added pause after Library Extraction to ensure Rule-Utility-Functions are present
Resolved in Pega Version 8.7
After upgrade from Pega 7 to Pega 8, nodes were not starting and the error "pub.context.InitializationFailedError: PRNodeImpl init failed" appeared. This was traced to an issue with the pzSharedTenant rule: when pzSharedTenant (Rule Access When) is assembled by the system, it uses the compareTwoValues Rule-Utility-Function. If the system is not able to find the correct version of compareTwoValues, it adds an UnresolvedAssemblyError in the assembly of the pzSharedTenant, causing the startup failure. This has been resolved by adding an await call after the LibraryExtraction task to wait for it to complete. This wait will ensure that the library extraction task completes before starting the search task which uses Rule-Utility-Functions
SR-A102222 · Issue 270905
Command line BIX extract includes pzinskey in XSD
Resolved in Pega Version 7.3
When running an extract to XML from within the UI, the generated XML and XSD both include the pzInskey. However, when the extract rule was saved to a file and run from the command line using the -I option, the XML file had the pzInskey but the XSD file did not. This has been corrected by ensuing the pzInsKey is included as part of XSD generated with the -I option.
SR-B159 · Issue 272693
Wizard will halt if rules to be deleted are in locked rulesets
Resolved in Pega Version 7.3
After running the Connector and Metadata wizard using a WSDL metadata file and then locking the current ruleset version, running the same wizard again using the same WSDL file and selecting OverWrite in the OtherConflicts step caused the rules in the locked first ruleset to also be overwritten. To prevent this, the CompleteRuleGeneration activity will cause the wizard to halt if it encounters rules that would be deleted that are in locked rulesets. When the ruleset(s) are unlocked, the wizard will continue.
SR-B42305 · Issue 299199
Parse-XML generation updated for complex XML element
Resolved in Pega Version 7.3
When generating the datamodel using the REST wizard, if the response XML had a page with type attribute then the value was ignored at run time. This has been fixed with updates to the "RuleGeneratorREST.java" for data model generation and "ParseXMLSAXRuleWrapper.java" for run time handling.
INC-182572 · Issue 663557
Support added for multiple host proxy architecture
Resolved in Pega Version 8.7
When using an architecture where certain types of users were sent through multiple proxy servers to get the Pega Cloud instance, an exception was generated at the point of accessing the environment. This was traced to the use of Apache 2.4 with mod_proxy. As the request passed through each proxy, the x-forwarded-host header had values appended to it by mod_proxy which resulted in the error "com.pega.pegarules.pub.context.PRSecurityException: Multiple host names in header X-forwarded-Host". This has been resolved by updating the code to support using a multiple host proxy configuration.