SR-A94142 · Issue 263214
Check added to handle submitModal button use
Resolved in Pega Version 7.2.2
After upgrade, running a script under the actions tab of a button was not working as expected though the standalone run did work. This has been fixed with the addition of a check to differentiate between a pzModalButton and a normal button.
SR-A99523 · Issue 266451
LockInformation section uses field value label
Resolved in Pega Version 7.2.2
The label in pzLockInformation section was hard coded, causing the string "You have lost the lock! Please reopen the item to continue your work." to not have a field value. This has been changed to create a Field Value and use the same in the label.
SR-A85709 · Issue 255759
Cleared erroneous dirtycheck popup on DropDown using lazyload
Resolved in Pega Version 7.2.2
When a pxDropDown was configured with load mode "After screen renders", the "selected" attribute was not correctly set on the HTML and the dirtyCheck failed even when the values were saved. This was due to the "Selected" attribute on options tag not being set properly when the dropdown mode was set to lazyload (after screen render), and has been fixed.
INC-158813 · Issue 629486
Updated report handling for simulations using database output
Resolved in Pega Version 8.5.3
When running a simulation with a database table as the output destination, the pxObjClass property was not populating with a value in the results. This caused sub-reports to not be populated with data. Investigation showed that issue happened when the simulation output destination database table was inferred as an external table due to not having an exposed column for pzinskey. To resolve this, the pxObjClass and pxCreateDateTime properties, which were added to simulation output destination tables for compatibility with Report browser, will not be added to those tables when they are created. Instead, to address compatibility issues of simulation output destination classes with Report browse in the Customer Decision Hub, the pyDefaultSummaryReport has been brought up into the Data-Decision-StrategyExecution-ResultOutput class from the @baseclass.
SR-A88481 · Issue 256518
VBS starts with DDS configured to use external Cassandra
Resolved in Pega Version 7.2.2
If DDS is configured with Internal Cassandra which is then switched to External, DDS reports to be in state NORMAL and VBD can start. However, when starting from scratch with DDS configured to use External Cassandra, DDS was failing validation and reporting to be in state CLIENT, so VBD was unable to start due to VBD's check that ensures at least one DDS is in the NORMAL state before starting. To address this, the validation code that checks the DDS state when VBD is starting has been removed and the system will instead rely on the DSM service layer to ensure that DDS is functional before VBD can start.
SR-A22284 · Issue 249432
Data pages used as search fixed for mobile clients
Resolved in Pega Version 7.2.2
In an application accessed via mobile client, a data page used as source for a search was not rendering results when attempting a second search. This issue was happening because of a race condition, and has been resolved with an added settimeout for the asyncrendercallback of the RDL template.
SR-A90821 · Issue 258447
Delayed Learning data flows use dynamic objects
Resolved in Pega Version 7.2.2
Data flows with delayed learning enabled were failing to run when initiated by a campaign. The root cause for this bug was the process where a data flow object was created only once and the same object was shared between multiple data flow runs in the node. The changes for this fix include making the DataFlow object non-static in the DelayedLearning.java class.
SR-A77555 · Issue 259289
Improved handling for multiple access 'when' in business event processing
Resolved in Pega Version 7.2.2
It was possible to encounter a missing page in the business event processing if event processing performed a call to tools.getThread().getAuthorization().haveAccess in multiple activities and there were several access 'when' actions defined for the class. The access 'when' requires that a work page be present to evaluate against, and depending on how the call was being performed or if passivation has occurred the process could throw an IndeterminateConditionalException and pass a null as parameter value for "aPage" parameter. To prevent this error, the activities pxCreateSummary and pxGetPrimaryClasses have been changed to pass the ClipboardPage of class for which haveAccess() is being called.
SR-A77555 · Issue 260161
Improved handling for multiple access 'when' in business event processing
Resolved in Pega Version 7.2.2
It was possible to encounter a missing page in the business event processing if event processing performed a call to tools.getThread().getAuthorization().haveAccess in multiple activities and there were several access 'when' actions defined for the class. The access 'when' requires that a work page be present to evaluate against, and depending on how the call was being performed or if passivation has occurred the process could throw an IndeterminateConditionalException and pass a null as parameter value for "aPage" parameter. To prevent this error, the activities pxCreateSummary and pxGetPrimaryClasses have been changed to pass the ClipboardPage of class for which haveAccess() is being called.
SR-A22996 · Issue 250572
Logic updated for 'when' controlled edit modes in embedded sections
Resolved in Pega Version 7.2.2
Complex layers of 'when'-controlled edit modes were not being properly applied in embedded sections. For example, if the main section included another section and the read-only nature of the included section was controlled by a when rule and the included section went on to include another section that contained a Repeat Grid/ Row repeat, the edit mode of the parent was not considered when evaluating the edit mode of the child. This was an issue with the logic governing precedence considerations, and has been updated with additional checks.