SR-D68572 · Issue 543004
Added check for duplicate attachment names with S3
Resolved in Pega Version 8.5
S3 Storage does not allow duplicate file names, but the AttachContent function was allowing duplicate file attachments. Due to this, the sync was failing to attach on the server and the message was never communicated to the client. This has been resolved by adding a check for duplicate file names when the storage is repository.
SR-119074 · Issue 175337
Calendar Control accessibility enhanced
Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7
In accessibility mode, the Calendar Control defaulted to the current year +/- 10 years. This did not allow dates for lifetimes or for long-term activity dates. In order to improve functionality, the dynamic system setting 'pyNumberofYears' has been inserted to allow modification of the datetime cell properties as desired.
SR-119074 · Issue 176791
Calendar Control accessibility enhanced
Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7
In accessibility mode, the Calendar Control defaulted to the current year +/- 10 years. This did not allow dates for lifetimes or for long-term activity dates. In order to improve functionality, the dynamic system setting 'pyNumberofYears' has been inserted to allow modification of the datetime cell properties as desired.
SR-A13115 · Issue 224892
Corrected sizing collapsed grid height to content
Resolved in Pega Version 7.2.1
A Repeating Grid using Progressive pagination and "Size grid height to content" with a configured number of rows to be shown without expansion was not accurately sized down when the content was below the display number. The function to adjust height of progressive grid has been fixed to display the content as expected.
SR-A20030 · Issue 238280
Corrected sizing collapsed grid height to content
Resolved in Pega Version 7.2.1
A Repeating Grid using Progressive pagination and "Size grid height to content" with a configured number of rows to be shown without expansion was not accurately sized down when the content was below the display number. The function to adjust height of progressive grid has been fixed to display the content as expected.
SR-A100653 · Issue 270340
Recent list refreshes in portal
Resolved in Pega Version 7.2.2
The 'Recent' section in the portal should be updated whenever multiple work objects are opened such that clicking on each case brings it to the top. In some environments, the user scenario Recent List was not properly updating due to exceptions in the pzFindAndupdateElement model; that function has been updated to handle exceptions properly.
SR-B67903 · Issue 330405
Params passed to createNewWorkWithParams and displayed
Resolved in Pega Version 7.4
An issue with createNewWorkWithParams where parameters were not displayed in the UI even if they were available in the pyWorkPage was traced to a code function-ordering error with passing parameters to createNewWorkWithParams that caused Work Page data that was set in CreateNewWork to be overridden before it was used. This has been corrected in the process engine createNewWorkAction.
SR-B67903 · Issue 331567
Params passed to createNewWorkWithParams and displayed
Resolved in Pega Version 7.4
An issue with createNewWorkWithParams where parameters were not displayed in the UI even if they were available in the pyWorkPage was traced to a code function-ordering error with passing parameters to createNewWorkWithParams that caused Work Page data that was set in CreateNewWork to be overridden before it was used. This has been corrected in the process engine createNewWorkAction.
SR-B91752 · Issue 340794
TrackSecurityChanges passes correct values for page groups
Resolved in Pega Version 7.4
The pzTrackSecurityChanges Utility is called from the TracKSecurityChangesLogic activity whenever the value changes for an audited property. For this function, current value and previous value are passed from the clipboard. However, in cases of page groups, the parent property was being passed instead of the current and previous values. This has been fixed.
INC-132897 · Issue 576549
UseSSL correctly set for password reset email
Resolved in Pega Version 8.2.8
Email was not being sent as part of the password reset functionality for Agile Studio when the email account was set to use SSL. An EmailClientException was logged. This was traced to the 'forgot password' flow reading .pyUseSSL as false, and has been resolved by setting pyUseSSL from the email account page.