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.

INC-143320 · Issue 602281

Support added for email addresses with hyphen in domain name

Resolved in Pega Version 8.3.5

When attempting to enter a email with a hyphen '-' in the domain part of an email ID ([email protected]), the reply button was getting disabled. This was caused by the regex validation implemented in the "pzValidateEmailAddress" (Work-Channel-Triage-Email) standard activity not covering all the possible cases. To resolve this, regex has been changed to instead use a platform-provided rule to ValidateEmailAddress.

INC-136091 · Issue 598907

Activity updated for Mobile attachment access

Resolved in Pega Version 8.3.5

Preview and download were not working for attachments stored in Pega Cloud Storage repository for mobile devices. Attempting to open an email attachment to preview or download resulted in a console error and the tracer showed the message 'Class pxLinkedRefTo does not exist'. This has been resolved by updating "pzpega_control_attachutil" to use the activity "GetAttachmentReference" for interactions with the attachments from any storage type.

INC-135720 · Issue 594794

Case link shows in Social messages for the old cases

Resolved in Pega Version 8.3.5

After upgrade from v7, the case link was not visible for the cases that were created in the old platform version. In Pega 7.1.7, metadata was stored in .pyPrivacyContextor while the later versions are using .pxContextType for Case type to show the related data. To resolve this, new properties have been implemented to hold the Case ID link.

INC-139160 · Issue 590255

Case tags made available for search filtering

Resolved in Pega Version 8.3.5

An enhancement has been added for obtaining the list of cases (of a specific type) based on a tag or case type. Clicking on a tag associated to the case will filter all the cases (of that case type) with that tag, and selecting more tags will refine the filter.

INC-146114 · Issue 604413

Create Survey routes case correctly

Resolved in Pega Version 8.3.5

The Create Survey utility was not routing the case to the user who initiated the case, but instead was routing it to the user who checked-in the case. This was traced to an error related to pxRequestor.pxUserIdentifier in the data transform pzpopulate survey params which is called when the survey utility is used, and has been corrected.

INC-146676 · Issue 601942

Field Service app localizations updated

Resolved in Pega Version 8.3.5

Localization has been added to the 'getDirections' alert and other popup alerts in the Field Service app.

INC-131592 · Issue 583437

Jsoniter parser upgraded

Resolved in Pega Version 8.3.5

After upgrade, the pxTextinput property Prompt List was being converted into decimal upon clicking finish assignment. This was traced to the jsoniter parser, and has been resolved by upgrading the parser in the jsoniter library.

INC-131961 · Issue 571699

Mobile app correctly determines online status after sleep

Resolved in Pega Version 8.3.5

After not using the mobile device for some hours, the app was not recognizing that the device had become online again and continued to show the red 'offline' bar. Restoring network connectivity required logging off and relogging into the network. This was traced to a bug in Android webview which causes window.navigator.onLine to return as false after wakeup despite the connection being present. To resolve this, version 8.5.103 of PIMC (Pega Infinity Mobile Client) contains new native mechanisms which are exposed to the webview as plugins and that work completely independent of webview.

INC-136768 · Issue 588452

Question Wizard import will downcase answer types to match system requirements

Resolved in Pega Version 8.3.5

The Question Upload wizard would not create a File type question while using a survey template. The template has a column Answer mode in which accepts an input of the type of answer expected, but in this use case "File" was given instead of "file", resulting in the question being created using the default values. To resolve this, during the import process when the system parses the file and gets the contents from the data using the pzSetdefaultValuesforQuestions DT, mode values will be explicitly set to lowercase.

INC-148099 · Issue 607290

Resolved button flicker

Resolved in Pega Version 8.3.5

The buttons were flickering when moving between screens in an offline-enabled mobile app. This has been corrected.

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us