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-B41316 · Issue 306260

Resolved missed cases in the WO case tree

Resolved in Pega Version 7.3.1

Sometimes several cases were missed in the case tree, shown in the right side of an opened WO. Access was not available for the corresponding WO and assignments. The root cause was a WHEN condition in WORK-COVER- PZLOADNESTEDCASESFORCLASS property "local.ProcessedItemKeys" containing numbers of processed WOs separated by a space, for example, "KPI-101 KPI-72 KPI-52". The WHEN condition checks for presence using "contains", leading "KPI-10" to be ignored and not displayed in cases where "KPI-101" already presented. To correct this, the system will consider the delimiter "\t" while checking the WHEN condition.

SR-B53650 · Issue 310574

Handling added to AssignmentListGadget for missing required properties

Resolved in Pega Version 7.3.1

The first step of pyPopulateCaseContents has multiple "break" statements in it. If any of those break statements were executed (such as due to a missing property) and resulted in "missingRequiredProperties" being set to true, the display of the gadget became broken. This was related to missing leading icons when a property doesn't exist, and pyPopulateCaseContents has been updated to resolve this issue.

SR-B52942 · Issue 311092

ResumeFlow modified to ensure all activity params show in SLA rule form

Resolved in Pega Version 7.3.1

The full list of activity parameters in the SLA rule form were not visible if the ResumeFlow activity had parameters called 'flowName' or 'calledFromServiceLevel'. This issue was caused by missing handling for parameters that are given but not needed. The ResumeFlow API has three parameters: 'flowAction', 'flowName', and 'calledFromServiceLevel'. Of these three, the value for 'flowAction' needs to be provided in this use. The other two parameters do not, as the runtime facility passes them through and they do not need to be set. To handle this scenario, logic has been added to skip these parameters for the ResumeFlow activity.

SR-B55376 · Issue 313068

Mandatory field highlighting fixed for attachment window

Resolved in Pega Version 7.3.1

The mandatory field highlighter (asterisk) was not getting displayed for " Window Name" and "Note" in the Attach A Screen Shot window. This was due to a handling error for an accessibility check, and has been fixed.

SR-B54175 · Issue 313627

Complex question Survey collection modified to support pagegroup reference handling

Resolved in Pega Version 7.3.1

Using a valuelist property embedded in a pagegroup to map the response of a Complex question resulted in a clipboard.InvalidReferenceException and the screen did not render the complex question. This was traced to the getMode function on ImmutablePropertyInfo returning the mode for the first property instead of the last property due to the first character being truncated if the property name started with "." To resolve this, SurveyAccessMethodBodyQuestionCollection has been modified to getMode from ClipboardProperty instead of ImmutablePropertyInfo.

SR-B65658 · Issue 294252

New case creation save errors resolved

Resolved in Pega Version 7.3.1

When a new case was created in an application built on top of Pega Pharmacovigilance, data propagation was throwing an error on the screen. Creation worked as expected when the pyDefault case type rule was opened and saved. This issue was traced to the case type rule not being created properly as part of the application creation, and has been resolved by updating pzDoesClassRequireBasicSave to not include Rule-Obj-CaseType in rows so the new application process performs a standard Save instead of an Obj-Save. In addition, it was not possible to save associated rules for selected data type when data type was in a locked ruleset and the pxUpdateRecord API was not setting pyrulename correctly when doing a save-as of the rule; these issues have also been corrected.

SR-B67239 · Issue 317809

pyCaseWorker offered during portal choice

Resolved in Pega Version 7.3.1

When choosing a portal on the access group, the pyCaseWorker one was not shown even though it was described in the documentation. To resolve this, an activity to update the property "pyDesktopType" to "User" has been added for the pyCaseWorker, pyCaseManager7, and pyPega7Express portals.

SR-B54548 · Issue 312031

Calendar Tab in Case Manager Portal shows Deadlines

Resolved in Pega Version 7.3.1

When opening the Calendar in the Case Manager Portal, it is expected that Goals and Deadlines are visible. However, Deadline was not visible in the Calendar even after the Goal time was reached. This was traced to the pxCalendarViewGadget taking the inputs for both GoalCalendar and DeadlineCalendar even though the latter is deprecated. In order to ensure pzCalendarAssignmentWorklist7 fetches the correct records, the pxCalendarViewGadget deadline source activity parameter has been modified.

SR-B46803 · Issue 306470

Button added to enhance chapter selection for Summary Tree

Resolved in Pega Version 7.3.1

When selecting specifications to include in a specification document, the "Chapters To Include" section did not always show the same specifications that were selected. To fix this issue, a new button labelled 'Update chapters to include' has been added; clicking on this will include the selected chapters in the Chapters Summary tree.

SR-B65006 · Issue 315528

Corrected validation for radio button labels in Survey

Resolved in Pega Version 7.3.1

When trying to save complex questions in Pega Survey with Answer mode as Radio button Matrix and giving radio button label as numbers, an exception was generated with the error "Label - Must start the value with a letter". This was due to incorrect validation, and has been corrected.

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