SR-A5453 · Issue 215368
Fixed Edit in Excel with load balancing enabled
Resolved in Pega Version 7.2
Edit in Excel was not working for decision tables if a load balancing was enabled. This was traced to the load balancer port number being added to the RequestHomeURL, causing a malformed strURL for opening the decision table in Excel. A check has been added to evaluate whether the strURL starts with a proper protocol and host instead of checking for RequestHomeURL.
SR-133163 · Issue 203273
Refined property-set expansion to support complex activities
Resolved in Pega Version 7.2
Attempting to expand a property-set in an activity with many steps (20+) caused a failure and the activity locked up. Tin order to support complex activities, the activity call and clipboard functions in this call have been refined for efficiency.
SR-A5355 · Issue 215511
Resolved browser hang with large Map Values
Resolved in Pega Version 7.2
While opening very large Map Value ruleforms, some systems were hanging and thread dumps were seen in the logs. With Microsoft Internet Explorer , the error was "There was an error while loading the content given. Microsoft Internet Explorer Error Description: Not enough storage is available to complete this operation." This was an issue with the display grid not being able to show huge number of records in the map value grid. To resolve it, the map value grid will be hidden if it exceeds the given cell threshold.
SR-A8561 · Issue 217554
Resolved browser hang with large Map Values
Resolved in Pega Version 7.2
While opening very large Map Value ruleforms, some systems were hanging and thread dumps were seen in the logs. With Microsoft Internet Explorer, the error was "There was an error while loading the content given. Microsoft Internet Explorer Error Description: Not enough storage is available to complete this operation." This was an issue with the display grid not being able to show huge number of records in the map value grid. To resolve it, the map value grid will be hidden if it exceeds the given cell threshold.
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.