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-B64353 · Issue 313990

Resolved assignment error when competing with SLA

Resolved in Pega Version 7.3.1

An Assignment error was occurring when the SLA competed with the user for an assignment. This was an error with setting the success indicator in the EstablishContext Activity, and has been fixed.

SR-B53049 · Issue 311589

SLA agent honors custom case type time-out

Resolved in Pega Version 7.3.1

Despite an assignment having a 3-hour lock period, the SLA agent was able to advance the assignment and remove access if the goal/deadline passed in less than that lock period. This was caused by a handling error where the order of steps led to not honoring custom timeout mentioned in the case type. This has been fixed.

SR-B57619 · Issue 316602

Bulk processing actions list corrected

Resolved in Pega Version 7.3.1

Even though the filter condition contained 'Assigned to Workbasket', the action list on selected assignments contained action for work objects. This was caused by a defect in the @baseclass.pyGetRelevantActions activity which would conditionally set local.bAssignmentChosen; this setting is not necessary, and the conditional setting has been modified to be 'true'.

SR-B53374 · Issue 312278

Bulk actions RD templates can be overridden

Resolved in Pega Version 7.3.1

Even though the pyBulkProcessingTemplate RDs in the application class were overridden, the RDs in Work- were being picked at runtime. This was because in pzRunBulkProcessReport, the class of RD is hardcoded to Work- while opening the RD. To resolve this, the hardcoding has been removed and instead the workpool class will be passed as the pyClassName while opening the template RD.

SR-B56510 · Issue 312804

Bulk actions RD templates can be overridden

Resolved in Pega Version 7.3.1

Even though the pyBulkProcessingTemplate RDs in the application class were overridden, the RDs in Work- were being picked at runtime. This was because in pzRunBulkProcessReport, the class of RD is hardcoded to Work- while opening the RD. To resolve this, the hardcoding has been removed and instead the workpool class will be passed as the pyClassName while opening the template RD.

SR-B55647 · Issue 313610

Improved page reference passing for subflow with split shapes

Resolved in Pega Version 7.3.1

For named pages, the page reference was not retrieved from pages and classes while performing validation during a subflow from a split shape. This has been fixed by sending pageandclasses as a parameter to findClassOfPageReference.

SR-B46908 · Issue 306223

Corrected incomplete filter clearing in Bulk Action search

Resolved in Pega Version 7.3.1

In Bulk Actions, searching cases using a filter property assigned to Operator with a particular operator, the results were displaying correctly. However, removing the operator ID and searching with an empty value showed the results for previously searched operator ID instead of showing all results. This was traced to the pyUserIdentifer not being cleared when the value of the Assigned To Operator filter value was removed, and has been fixed.

SR-B57138 · Issue 313180

BulkUpdate search function made available for customization

Resolved in Pega Version 7.3.1

In order to support customization for activities such as the updating of display of filters in bulk update, the use of pzBulkUpdateSearchSection has been withdrawn and replaced with pyBulkUpdateSearchSection.

SR-B53230 · Issue 310973

SendEmail shape validation calls updated

Resolved in Pega Version 7.3.1

Inconsistencies were seen with using the SendEmail smart shape to send email to the configured workparty. This was traced to the way pyWorkPartyUri was populated from the CallWorkPartyRetrieve activity. This activity is referred in pyWorkParty property and called when any property on the work party is changed in the UI. However, when the work party is populated programmatically, this activity was not getting called and mandatory properties were not being set or validated. To ensure consistent behavior, pyWorkPartyUri has been included in Validate.

SR-B53918 · Issue 312285

Optimistic locking on resolved case fixed for Back button use

Resolved in Pega Version 7.3.1

It was possible to perform an action on a resolved case when in screen flow, i.e. when in the middle of a screenflow of a case and the case gets resolved due to some action in another case. If Refresh was clicked from the Actions, the case was updated as Resolved-, but clicking on the Back button of the screen flow ignored the Resolved status and allowed changes to be made. The logic to check for stale data (optimistic locking) was missing on the Back button in the screen flow, and has been fixed.

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