SR-A100118 · Issue 287256
Auto-populate updated for better page copy references
Resolved in Pega Version 7.3
After upgrade, an error was generated at a page-remove step on the Group information screen while running the quoting process. This happened in cases where a copy was made of a page containing an auto populate property and the data page referred by the AP had Common Parent references, and was traced to the parent page of the reference property having been removed from the common parent page. To resolve this, the auto-populate function has been updated to better maintain references in copies.
SR-A100558 · Issue 271513
Oversized file null-pointer exception resolved
Resolved in Pega Version 7.3
A 413 exception was being generated by uploading files with a size greater than the Initialization/MaxFileUploadSize DSS value. The controls have been modified with a check to restrict properly restrict file size during this process.
SR-A100558 · Issue 274795
Oversized file null-pointer exception resolved
Resolved in Pega Version 7.3
A 413 exception was being generated by uploading files with a size greater than the Initialization/MaxFileUploadSize DSS value. The controls have been modified with a check to restrict properly restrict file size during this process.
SR-A100717 · Issue 275645
Certificate validation handling updated to work with single-entry CN or DN
Resolved in Pega Version 7.3
Previously, the Gateway connectivity test assumed valid certificates would contain more than one CN entry. This caused an invalid certificate error on the host landing page of prgateway gateway test if the certificate in use had only CN entry. To address this, code has been added to handle cases where a certificate has only a single entry of either CN or DN.
SR-A100717 · Issue 277670
Certificate validation handling updated to work with single-entry CN or DN
Resolved in Pega Version 7.3
Previously, the Gateway connectivity test assumed valid certificates would contain more than one CN entry. This caused an invalid certificate error on the host landing page of prgateway gateway test if the certificate in use had only CN entry. To address this, code has been added to handle cases where a certificate has only a single entry of either CN or DN.
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-A102237 · Issue 271876
Unmapped columns from an external table skipped in DDL query generation.
Resolved in Pega Version 7.3
The OBJ-SAVE method was generating a query in which unmapped columns were also getting updated. As these columns were not mapped, DB columns were being updated with the value NULL. This was due to the Obj-Save function always saving the entire object, causing an issue when only part of a table is mapped to a class. To correct this, new prconfig and DASS settings have been added to exclude unmapped columns of an external table as part of DDL query generation.
SR-A102447 · Issue 276743
Corrected post-rule migration SOAP null-pointer exception
Resolved in Pega Version 7.3
In some multi tenant environments, a null-pointer exception exception was appearing for the first SOAP call after a rules migration. Subsequent calls worked as expected. This was caused by a timing issue related to loading the global context cache for a given access group, and the event order handling has been improved to correct it.
SR-A23571 · Issue 279027
ExtractSection data transform optimized
Resolved in Pega Version 7.3
The code in pzExtractSectionPostDT and pzExtractSectionPostActivity has been optimized to improve data transform processing time.
SR-A80436 · Issue 278157
Federated Case Management GetNextWork function resolved
Resolved in Pega Version 7.3
When an operator had Work Basket configured with Federated Case Management, the Get Next Work function generated an error. This was due to the GNW settings from the operator IDs of the 'remote' systems not being correctly respected, and has been resolved.