SR-B15463 · Issue 287079
New Application operator mapping refinements
Resolved in Pega Version 7.3
When using the New Application Creation wizard, the newly created operators were unexpectedly mapped to the same access group even though the access groups contained different roles. This has been corrected with changes in the pxPrepareApplicationDemoUsers and pxPrepareClonedAccessGroup activities to set transient properties for the original access group name as well as for use in lookup by demonstration users.
SR-B16337 · Issue 288963
BIX TotalInserts and TotalInstance counts made consistent for nested pages
Resolved in Pega Version 7.3
The pxTotalInsertsCount and pxTotalInstanceCount values were being calculated incorrectly when using PageLists and a Page under those PageLists. This was a missed case, and the system has been updated to address it.
SR-B16825 · Issue 292599
WordMacroManagerDot updated for 64-bit compatibility
Resolved in Pega Version 7.3
The WordMacroManagerDot macro has been updated for Word-64-Bit environment compatibility.
SR-B16921 · Issue 287323
BIX documentation for Obj-Save help updated
Resolved in Pega Version 7.3
The BIX Extracts help file has been updated to clarify which properties are or are not updated when using Obj-save, explicitly noting that pxUpdateDateTime is not updated in the database when the Obj-save method is invoked and that a data transform should be applied to cause an update. Obj-save does update pxCommitDateTime.
SR-B17080 · Issue 289244
saveAllOrNone API more robust for multi-tenant shared BIX
Resolved in Pega Version 7.3
Intermittent errors appeared when two BIX command line extraction scripts were running in parallel when both used BixUser_Tenant as the operator. This was traced to the saveAllOrNone API, which was not equipped to prevent other nodes from writing data into the DB while the current thread was also trying to write that same data to the DB. Further diagnostics are required to formulate a solution to this intermittent error, but the API has been made more robust: the system will not throw an IllegalStateException when the DB exception is DuplicateKeyException.
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.