SR-A10681 · Issue 221581
Resolved tracer issue for new operators
Resolved in Pega Version 7.2
A tracer issue was found where selected events for newly-created operators were clearing off. This has been fixed by refactoring the code handling adding new event types.
SR-A6265 · Issue 214301
Enhanced justification carryover during migration
Resolved in Pega Version 7.2
It was noted that after upgrade, some justifications were lost due to the differences in the warning messages between versions. Justifications are attached to each individual warning and each individual warning is saved with the rule, and the intent was that the justifications come with the RAP on a migration. However, many warning messages have been updated for language, style, content, etc., in new versions. This meant that after migration, resaving a rule caused the old warning (and hence justification) to be lost when the new and improved warning message was attached in its place. To ensure expected behavior, the system will now look for old warnings and map them to updated warnings while keeping the associated justification.
SR-A6567 · Issue 216325
Specification data linking allowed for all decision types
Resolved in Pega Version 7.2
When entering specification data in the properties panel of a decision shape, a specification rule automatically created in the background could be opened and viewed but the specification rule was not linked correctly to the flow rule. The specification was not present in the 'For flow components' section of the Specification tab of the flow rule, and it was incorrectly documented in a section headed 'Other Specifications (outside the process)' in the Application Document. This was found to be inconsistent execution of the specifications function where the existing code supported use case linking only for few decision types while the UI allowed link specifications for all decision types. To resolve this issue, 'Data-MO-Gateway-Decision.Validate' has been updated to allow linking for all decision types.
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.