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-B13702 · Issue 287232

SLA correctly calculated for migrated rules

Resolved in Pega Version 7.3

After upgrade, using the case designer view to look at a case type created in an earlier version displayed errors in the right panel for the goal-HH:MM:SS and deadline-HH:MM:SS fields if the assignment had the SLA rule "Default". This was an error in backwards compatibility related to whether the "pzIsAutoGenerated" property used to distinguish the SLA was auto generated or not, and has been corrected by setting the Visibility condition .pzAutoGenerated to 'true' in the lower Dynamic layout to avoid a null value in migrated rules.

SR-B13872 · Issue 290520

StartDependencies RUF logging updated from Error to Debug mode

Resolved in Pega Version 7.3

After calling a utility to create a child case through an activity on a parent sub-flow, updating the parent case status with the "UpdateStatus" activity logged an error message that the dependent had not been created successfully. This was an unintended side effect of a logging change made for diagnostic purposes, and has been fixed by changing the logs from Error mode to Debug mode in the pzStartDependencies RUF.

SR-B13929 · Issue 289408

Instances Count updated to better handle external DB checks

Resolved in Pega Version 7.3

Opening the Data table list from the Designer studio DesignerStudio > Data Mode > Data Tables > Data Tables generated an exception related to obtaining a count of instances from an external DB. This has been resolved by adding a check which modifies the activity based on whether the call is to an internal or external DB.

SR-B14129 · Issue 284313

JSON mapping updated to support page list class given as string value

Resolved in Pega Version 7.3

Connect Rest was not parsing the value of the Boolean property "isEligible" returned as part of a JSON response or mapping it on to the clipboard. This was traced to the unexpected scenario of the string "$ANY" being used as class for a page list and inside a pagelist Boolean property. To support this use, the JSONMappingUtils.java file mapObjectToPage method has been modified to handle the Boolean property before the generic else if condition.

SR-B14153 · Issue 284939

Only relevant records shown for work objects in select property picker

Resolved in Pega Version 7.3

The select property picker for all work objects with record identifiers was showing all records whether or not they were relevant. This was an issue where show relevant was being set to false when record identifier and show relevant was true in pyGetCategoryItems for all classes, and has been corrected by skipping this step for work object classes.

SR-B14288 · Issue 289182

Command line BIX extract works as expected for -l option

Resolved in Pega Version 7.3

When a BIX extract was generated using rule XML of the extract rule (-I) from the command line, the manifest generated had "pxExtractIdentifier" in an unexpected format. The command line option has now been modified to generate the extract with the correct pzInsKey of the rule.

SR-B14774 · Issue 285008

Optional Process Child Case correctly sets ObjectClass

Resolved in Pega Version 7.3

When creating a Child Case from an Optional Process on the Case Type Rule, the ObjectClass of WorkPage did not update to the object class of the child case. The proper class was set when generated using an Automatic Process on the ObjClass. This has been corrected by using a performAssignmentCheck before acquiring work object.

SR-B14774 · Issue 285027

Optional Process Child Case correctly sets ObjectClass

Resolved in Pega Version 7.3

When creating a Child Case from an Optional Process on the Case Type Rule, the ObjectClass of WorkPage did not update to the object class of the child case. The proper class was set when generated using an Automatic Process on the ObjClass. This has been corrected by using a performAssignmentCheck before acquiring work object.

SR-B1495 · Issue 273198

Workaround to resolve HP NonStopDB column label bug

Resolved in Pega Version 7.3

Using HP Non Stop DB as an external DB with Type 4 driver caused Connect-SQL with Browse to generate the error "UNKNOWN_COLUMN_0: Column number 0 has an invalid name errors in clipboard" but still return the data. This was traced to a bug in the HP driver that caused the getColumnLabel() to be returned as empty, and the system has been updated to return the Column Name when Column Label is null or empty to overcome this.

SR-B15101 · Issue 296224

Logic added to convert UTC Date for REST clipboard mapping

Resolved in Pega Version 7.3

An error was generated while mapping UTC format Date fields to the clipboard in REST. This was traced to the DateTime properties in the JSON response not being converted to Pega-supported datetime format, and the necessary parsing logic has been added.

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