Skip to main content

Resolved Issues

View the resolved issues for a specific Platform release.

Go to download resolved issues by patch release.

Browse release notes for a selected Pega Version.

NOTE: Enter just the Case ID number (SR or INC) in order to find the associated Support Request.

Please note: beginning with the Pega Platform 8.7.4 Patch, the Resolved Issues have moved to the Support Center.

SR-B6980 · Issue 278169

fixed naming in multiple extracts run from the command line

Resolved in Pega Version 7.3

When running multiple comma separated extracts at a time using command lineoption -i, all of the rules in the manifest file contained the value of the last extract name only. This was a missed use case, and ExtractImpl has been modified to correct it.

INC-159244 · Issue 627863

Bulk actions check in preserves declare expression legacy setting

Resolved in Pega Version 8.7

When a declare expression was saved in legacy mode with "Whenever used" selected in change tracking, performing a bulk check-in of the rule caused the expression to default to the new forward chaining method. This did not occur when using a direct check-in. Investigation showed this was caused by the check-in page holding a legacy value before the step execution, and has been resolved by adding a pre-save activity before the validation activity that will restore the .pyIsLegacy value from .pyExpressionTypeSelector, if set.

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

INC-175707 · Issue 655347

Multi-level strategy gives correct rules during Batch run

Resolved in Pega Version 8.7

When using a nested page structure with multi-level strategies that loop through each page and process the customer, a customer with two linked customers A and B had the results of A overridden by B during Batch Processing while single case canvas testing showed the correct results. This was caused by the DSM clipboard page method of carrying the parent page info not supporting the re-use of pages, and has been resolved by adding an enhancement that will sanitize the strategy stage processor to ensure the correct page reference is used.

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.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us