SR-A5730 · Issue 213019
Namecase check added to DB2/ZOS split schema installation
Resolved in Pega Version 7.2
An omission in the documentation for the installation wizard guiding the creation of a split schema on DB2/ZOS failed to specify that the database username on the UI screen or in the setupDatabase.properties file as well as the properties in the DB2SiteDependentProperties file are required to be in all upper case. As a result, some installations experienced a runtime exception and an unexpected process termination due to name mismatch. The documentation has been updated. and a check has been added which will take a supplied mixed/lower-case user name and uppercase the value used to set the currentSQLID parameter.
SR-A8556 · Issue 218132
Removed unexpected 'History-' DB instances
Resolved in Pega Version 7.2
Due to an error, 61 additional Data-Admin-DB-Table instances that should not have been part of the media were packaged in the software distribution. The impact was low as all started with 'History-' and contained the name 'Engineering', but their presence and lack of matching associated Class Definitions caused them to be reported on the Database Landing page as "Invalid Class Mappings". We apologize for this confusion.
SR-A2519 · Issue 210033
Added check for assembler handling after upgrade
Resolved in Pega Version 7.2
Due to differences in assembler versions, some SOAP services were not properly executing after upgrade and exhibiting record mapping inconsistencies. A check has been added to call the switchtooldassembler function if appropriate, resolving this problem.
SR-A4641 · Issue 211783
Added handling for null values in JSON
Resolved in Pega Version 7.2
When attempting to serialize a property of type Boolean or Number, a null value caused empty value mapping in the JSON stream (expected is {"Name":null}, but the result is {"Name":} thereby resulting in incorrect JSON). This has been resolved by modifying getPropertyAsJson() of ServiceHelper.java to stream "null" value (without quotes) when a scalar property (of type other than Text) exists in clipboard with an empty/null value. Properties assigned with null objects are considered and shown in the JSON response as below: Ex: {"pyLongDescription":"null","pyauto":"null","pyDueBy":"null"}
SR-A3789 · Issue 212055
Corrected Chinese font PDF margin errors
Resolved in Pega Version 7.2
PDFs generated using Chinese fonts had margin errors that truncated content. To correct this, the htmlWidth will be handled as a parameter and not a fixed value.
SR-A3610 · Issue 217555
Corrected ParseXML clipboard mapping
Resolved in Pega Version 7.2
The ParseXML rule was not correctly mapping data to the clipboard after upgrade. This was a regression: the design limitations of the new parse rule caused an issue with calling child parse rules on the fly based on the context page, and has been fixed by parameterizing the override class of the new parse rule.
SR-A3992 · Issue 212220
Fixed appendment handling for ComplexType elements
Resolved in Pega Version 7.2
If an element was of ComplexType, the attributes were appended before the sequence of elements are appended; this has been corrected.
SR-A5222 · Issue 215076
Fixed Vcalendar meeting invites propagation
Resolved in Pega Version 7.2
Because the VCalendar file was considered a text file while sending calendar invite request, it was not being properly handled for meeting invites. Code has now been added to treat meeting requests as attachments
SR-A5659 · Issue 214180
HTTP Connector Simulation properly runs for both Global and User sessions
Resolved in Pega Version 7.2
When attempting to use a simulation activity for a HTTP Connector, it worked when set to Global Session but did not appear to run when set to User Session. At run time, the list of simulation activities was picked from the pyISSimulation clipboard page. Because that page was available in the "STANDARD" thread only, the code responsible for loading the simulation activities was not able to find the correct page. This has been fixed to allow the table to properly execute the Connector simulation for both Global and User Session.
SR-A5103 · Issue 214155
Improved Rule-Connect-SOAP connector performance
Resolved in Pega Version 7.2
Performance issues seen when running Connect-SOAP with NTLM authentication and tracing it using Performance Profiler have been resolved by modifying the parsing to improve use of the cached objects.