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 update your bookmarks. This site will be discontinued in Dec 2024.

Pega Platform Resolved Issues for 8.1 and newer are now available on the Support Center.

SR-D21555 · Issue 501106

Resolved command line BIX/PRPCUtils creating unreachable nodes

Resolved in Pega Version 8.4

BIX and PRPCUtils scripts were creating nodes that showed as unreachable or that were never cleared. This was traced to a code change that resulted in nodes starting as stream nodes unless given a node type or DSS settings, and has been resolved by setting the asyncExecutor/enable setting value as false in the prconfig.xml. The BIX command line JVM argument should also be set to NodeType=BIX.

SR-D22075 · Issue 501345

Wild card character escape added for filtering data records

Resolved in Pega Version 8.4

It was not possible to export data type records which were filtered with either _ or % in the value. This was due to the characters being wild card characters in the SQL-like operator, and has been resolved by modifying the NativeSQLAPIResolver to add escapecharacter to the runtime value of the filter.

SR-D22468 · Issue 502037

Bix extract performance improved by only checking cipher type for encrypted properties

Resolved in Pega Version 8.4

Previously, if no cipher was configured in extract Rules the cipher type defaulted to null and wasn't cached. This caused performance issues when running against the database. In order to improve performance, the code has been modified to only check for cipher type if the property is encrypted. Performance issues were also seen when running a BIX extraction via the command line where the BIX extract was set to extract all properties, the BIX extract rule used Extract to XML, and DisableEpochDateTime and DisableEpochDate settings were not created and thus the default (false) value was used. This slowness was traced to the command line extract not caching the "miss" for the values of the Epoch settings and therefore repeatedly querying the pr_data_admin table for the date and datetime property for each record. Investigation showed that BIX was depending on DASS files that are not shipped out-of-the-box: since the DASSs were not present, the query to retrieve their value returned null and was not cached for future access. To resolve this, the system has been updated to pass default values for the two required DASSs if they are not present, ensuring a value will be cached and the DB query will not be fired unnecessarily.

SR-D23490 · Issue 496577

Interface changes made to avoid unexpected workitem deletions when removing stale locks

Resolved in Pega Version 8.4

Attempting to delete lock instances of work objects by directly opening the lock item found through navigating to (Dev Studio) App > Classes > System-Locks actually resulted in deleting the work item instead of just the lock. This was due to System-Locks being uniquely identified by the WorkItem that they belong to rather than having their own specific key. This meant that clicking on one of the instances caused the system to respond by presenting a "default RuleFormLayout section" which included a delete button keyed to the actual workitem, but this was not made explicitly clear in the interface. In order to prevent unexpected item deletions, the table has been replaced with a link to the proper System-Lock interface, specifically the "My Locks" window.

SR-D25902 · Issue 510083

DSS added for reference Page Group fields extraction using Dictionary

Resolved in Pega Version 8.4

Reference properties were not being resolved when the useDictionary option was set to false, resulting in empty data being extracted from the blob for embedded pagegroup and pagelist properties. To resolve this, a new dynamic system setting in Pega-RULES ruleset, "BIX/enableDictionaryLookUpForDBExtract", has been added to enable dictionary resolution so that the embedded page group reference property values are resolved for extraction. The default value is "false".

SR-D27540 · Issue 502969

Null check added for ObjClass filter value

Resolved in Pega Version 8.4

When a report definition was run with "Starts with" as a filter condition and "Use null if empty" was not checked, the message "An error occurred during resolving the report definition - null java.lang.StringIndexOutOfBoundsException" was logged. This did not appear if the filter condition was "is equal" and "Use null if empty" was checked. To resolve this, the system will check for a null or empty value on pxObjClass filter values before processing it for class descendants.

SR-D29901 · Issue 505063

Additional numeric decimal method added to Class mapping wizard

Resolved in Pega Version 8.4

If a table was created with column type numeric(18,2) and then the database class mapping wizard was run to map the column to a property, the wizard generated a property of type Integer, which is incorrect - it should be a property of Decimal type. When generating columns on the pega side using the SQL types of an external database (in getBestPegaTypeForColumnType), the switch statement falsely had numerics as being integers. To resolve this, an additional method has been added with numerics being treated as decimals.

SR-D32307 · Issue 500955

BIX extracts traverse up from embedded pages to find target tables

Resolved in Pega Version 8.4

For BIX Extracts with Output Format : Database Schema, the target table name was not being generated if the properties were buried under two levels of Embedded Pages. Instead, in case of multiple nested levels of PAGE property types, the system ended up referring the immediate Parent page or its parent PAGE for pySourceName. Since this is of type PAGE, an empty value was returned for the target table name and the extract would fail. To resolve this, the system has been updated to traverse up the node parents until the correct target table name is found.

SR-D33003 · Issue 511231

Queue Batch activity correctly passes chlld process access group

Resolved in Pega Version 8.4

Attempting to create an index using the schema tools landing page was throwing an error in the table history stating "Create index failed". Investigation showed that this happened when a user was authenticated without the PegeRULES:DatabaseAdministrator role and then switched to an Access Group with the PegeRULES:DatabaseAdministrator role. The issue was traced to the activity that launched the batch requestor missing the parameter pzUseCurrentAccessGroupForChild due to the Queue Batch activity only passing the default access group authorization. This has been resolved by adding code to pass the additional authorization which will allow users to create an index in this scenario.

SR-D33934 · Issue 503335

Parent case lock properly released when child case is resolved

Resolved in Pega Version 8.4

After creating Parent-Child casetypes with default locking where the child case had the “Allow access to parent” check box checked, the temporary lock acquired on the parent during resolution of the child case was not released afterwards. If “Allow access to parent” was not checked, then the locks were released on both the parent and the child. This was traced to a combination of parameters used by the openIfStale() API where aUnlockOnCommit could be set to false despite the provided locking strategy expecting it to be true, as well as honoring UnlockOnCommit when maintainLockingStrategy is false. To resolve this, the system has been updated to always check whether the lock is available in the map already and if it is, then set unlockonCommit to true. Otherwise, under all cases, honor the passed-in unlockOnCommit value.

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