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-A8387 · Issue 217780
Added prevention for inappropriate Google Chrome autofill
Resolved in Pega Version 7.2
When login userid and password were stored in the Google Chrome browse and autofill was enabled, Google Chrome was using those values to populate the RuleSet rule form's input field (hidden on UI on Versions tab) and password field (on the Security tab). Those invalid values caused a save failure. To fix the issue, the system will pre-populate the hidden input field so that Google Chrome does not auto fill this field on the client side.
SR-A3950 · Issue 209476
Corrected order of tabbing focus in Activity rules
Resolved in Pega Version 7.2
After opening an Activity rule, the Description text field did not receive focus at the expected point when tabbing through the steps. The activity steps have been rebuilt to correct the tabbing order.
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.