SR-A21015 · Issue 239858
AddTime calendar logic updated
Resolved in Pega Version 7.2.1
An issue was found with the final output of using the AddTime function in a Business Calendar with Australian Time Zone to add the difference between GMT and Australian time. In the internal APIs being used by this function, whenever parameters to addTime() were given in such a way that the time to be subtracted was same as the difference between the time of a given input date, start time of a business day, it was considered that there was nothing to add to input time and hence incorrect result. The logic in the engine API, CalendarUtitlity.addTime() which is used in addTime() function, has been changed to correctly calculate the desired time.
SR-A21017 · Issue 239317
Parameter label mismatch corrected for import
Resolved in Pega Version 7.2.1
During upgrade, activities or functions which had Parameter type 'Double' were automatically converted to String data type upon Import into the target Environment even when the XML indicated DOUBLE. This was an issue with rendering the value in the UI: the pyLabel for double parameter type was "Double" not "DOUBLE" in the Data Transform rule pyLoadDataTypes, which didn't match. The activity has now been updated to use DOUBLE.
SR-A21298 · Issue 239141
NPE on mobile list open resolved
Resolved in Pega Version 7.2.1
A null pointer exception was being generated on mobile device when opening list items. A null check has been added to pega_ui_modaldialog to resolve this exception.
SR-A21588 · Issue 241928
Name retrieval updated for node sub-units
Resolved in Pega Version 7.2.1
A retrieval error for the sub-unit name of a node was causing a "Cannot render section" error in the Organization Chart tab. This has been corrected.
SR-A21636 · Issue 240162
Fixed auto-complete use in iPhone Opportunity creation
Resolved in Pega Version 7.2.1
Issues were seen when selecting items using Auto-Complete on an iPhone while creating an Opportunity. This was due to a positioning error in the logic, and has been fixed.
SR-A21810 · Issue 231480
PreClose updated to better handle inactive DC documents
Resolved in Pega Version 7.2.1
The PreClose extension point was not always being triggered for inactive DC documents utilizing the pzClearRecentItem and pzClearAllRecentItems APIs due to stale settings. The correct this, the handlegadgetLoad method has been updated to delete the docObj after the document has loaded.
SR-A21830 · Issue 244836
Improvements made to History Compare
Resolved in Pega Version 7.2.1
The SMS treatment rule full history provided by Pega Marketing was not reflecting the actual changes that were applied in each revision and the compare differences functionality was not showing expected differences. The handling of the comparison has been updated to correct this, and the logic has been further improved to include the "initial creation" version when appropriate.
SR-A21830 · Issue 246779
Improvements made to History Compare
Resolved in Pega Version 7.2.1
The SMS treatment rule full history provided by Pega Marketing was not reflecting the actual changes that were applied in each revision and the compare differences functionality was not showing expected differences. The handling of the comparison has been updated to correct this, and the logic has been further improved to include the "initial creation" version when appropriate.
SR-A22067 · Issue 243520
Corrected passing Current Parameter Page in Collections
Resolved in Pega Version 7.2.1
When attempting to call a rule in a Response Actions entry on a Collection flow, the configuration panel would not submit when "Pass Current Parameter Page" was checked and there were required parameters on the rule being called. This was traced to an unneeded validation being performed, and has been resolved.
SR-A22090 · Issue 243573
Activity method loading works with encryption
Resolved in Pega Version 7.2.1
Activity method loading was not working with URLEncryption enabled. This was a problem with populating the parameters with the encryption function in use, and has been fixed by making use of SafeURL to prepare the querystring of the URL.