SR-B17338 · Issue 294731
Corrected and improved calculations for multiple page Business Calendars
Resolved in Pega Version 7.3
The Business Calendar time zone was not correctly populated when a second page was added to the calendar. This was due to the new page using the operator time zone instead of the business calendar time zone, and has been fixed. In addition, the difference calculations for calendar processing have been improved for greater accuracy.
SR-B17403 · Issue 297717
Resolved concurrent mod exceptions when using getValueInType API
Resolved in Pega Version 7.3
Concurrent modification exceptions were observed in the logs when the getValueInType API was called to fetch property values from multiple threads. To resolve this, the getValueInType API has been made thread safe by synchronizing its access.
SR-B2228 · Issue 273457
WordTextArea control updated for IE
Resolved in Pega Version 7.3
Erratic behavior was seen in saving and displaying a Word document when launched from the WordTextArea control. This was a compatibility issue with IE, and the DoLaunchExtWord function has been modified to fix this.
SR-B2362 · Issue 274142
Corrected newline comparisons for pega.comparePages
Resolved in Pega Version 7.3
When mapping an external table partially to PRPC class, updating the table with Obj-Save caused the un-mapped columns to be updated to null. This was due to the comparePages API not doing an appropriate comparison whenever a property in one of the pages had a new line as a CR ("\r\n") and in the other page had new line("\n"). This has been corrected.
SR-B2709 · Issue 272341
Resolved ConcurrentModification exception in getclass name
Resolved in Pega Version 7.3
Attempting to getclass name while iterating over values of mPageProperties in expandAllToProperties (in the putPropertyOntoClipboard call) was causing a ConcurrentModificationException that resulted in queues being blocked and loss of synch to the server. In order to more cleanly set the pxObjClass for the classless page-properties, pxObjClass has been added to the lookupDictionaryDefinition.
SR-B2709 · Issue 275299
Resolved ConcurrentModification exception in getclass name
Resolved in Pega Version 7.3
Attempting to getclass name while iterating over values of mPageProperties in expandAllToProperties (in the putPropertyOntoClipboard call) was causing a ConcurrentModificationException that resulted in queues being blocked and loss of synch to the server. In order to more cleanly set the pxObjClass for the classless page-properties, pxObjClass has been added to the lookupDictionaryDefinition.
SR-B30914 · Issue 290290
PurgeExtraRecents logging changed from error to info
Resolved in Pega Version 7.3
In order to support increasing the number of recent items to display to more than 30, the existing logging function in System-User-Recents!pzPurgeExtraRecents activity has been changed from error mode to info mode so the logging can be disabled if desired.
SR-B30962 · Issue 291933
SaveOperatorUnavailability error message made generic
Resolved in Pega Version 7.3
Data-Admin-Operator-ID.SaveOperatorUnavailability generates the error message ("You are not authorized to create, modify, or lock operator instance "+myStepPage.getString("pyUserIdentifier")); if the request is not sent with the proper privileges. In order to obscure what the privileges are from potentially malicious use, this message has been made more general with the text "You are not authorized for this operation".
SR-B31667 · Issue 289067
Consistent Work IDs between case types created in different implementations
Resolved in Pega Version 7.3
Creating an Implementation layer on the Warranty application using the New Application wizard of Pega 7.22 GA was resulting in a different Work ID prefix of some case types like Claim Unit or Appeal than when the same case types were created in the built on application. This was traced to different activities being used to populate the data page, and has been updated to ensure uniform work ID generation.
SR-B3208 · Issue 293911
Check added to ensure Tracer finds regular pages
Resolved in Pega Version 7.3
Page D_Properties was mentioned in pages to trace, it was present in clipboard, but was not passed to tracer due to an error in page handing. An extra check has been added as a fallback to look for a regular page if Tracer's data page check does not return a named page.