SR-A24414 · Issue 260410
Flexibility added for ruleset persistence with dynamic locale
Resolved in Pega Version 7.2.2
When launching an intent in CS, the content sporadically failed to localize all or part the content until the browser was refreshed and the task re-entered. This was caused by a configuration that was trying to set the locale dynamically, an unsupported function. To better support flexibility, changes have been made to honor the current Ruleset List instead of the default Ruleset List so that even if the locale changed dynamically, the changed rulesets will be persisted.
SR-B34004 · Issue 292912
New config added for tuning PropertyInfo threads on high-load systems
Resolved in Pega Version 7.3
In order to resolve an issue with blocked threads due to contention while getting PropertyInfo objects from the dictionary during periods of extremely heavy loads, the new config setting "cache/dictionarycache/reduceContentionGetPropInfo" has been introduced. This config will default to false to preserve the current performance functionality; setting it to true will change the behavior to acquire locks on smaller blocks of code instead of bigger blocks to reduce contention.
SR-B34004 · Issue 276857
New config added for tuning PropertyInfo threads on high-load systems
Resolved in Pega Version 7.3
In order to resolve an issue with blocked threads due to contention while getting PropertyInfo objects from the dictionary during periods of extremely heavy loads, the new config setting "cache/dictionarycache/reduceContentionGetPropInfo" has been introduced. This config will default to false to preserve the current performance functionality; setting it to true will change the behavior to acquire locks on smaller blocks of code instead of bigger blocks to reduce contention.
SR-B54175 · Issue 313627
Complex question Survey collection modified to support pagegroup reference handling
Resolved in Pega Version 7.3.1
Using a valuelist property embedded in a pagegroup to map the response of a Complex question resulted in a clipboard.InvalidReferenceException and the screen did not render the complex question. This was traced to the getMode function on ImmutablePropertyInfo returning the mode for the first property instead of the last property due to the first character being truncated if the property name started with "." To resolve this, SurveyAccessMethodBodyQuestionCollection has been modified to getMode from ClipboardProperty instead of ImmutablePropertyInfo.
SR-B52348 · Issue 308690
Restored option to allow PDF export for chart actions
Resolved in Pega Version 7.3.1
Updates to the version of Fusion included in Pega caused support to be lost for "Export to PDF". This broke a 'when' rule that allowed export of a chart embedded in a section by selecting "Show data". To restore that function, the 'when' step in pyReport_ShowChartWhenShowingData that disables the chart when running the report in "dataonly" mode has been changed. The 'when' rule will default to not showing the chart for backwards compatibility, but can be overwritten to show the chart.
SR-B67935 · Issue 319257
Updated decision shape iteration for StarCaseFlow
Resolved in Pega Version 7.3.1
When a decision shape in the pyStartCase flow contained only a boolean expression and the connector (true and false) of decision shape was attached to two assignment shapes, the flow worked on the desktop but did not work on mobile. This was due to 'ForDecisionShape' case being offline enabled while Library functions were not, and has been fixed by modifying the system to iterate and evaluate all the decision shapes in Create New Work .
SR-D91344 · Issue 560627
Resolved PageCannotBeSerializedForPassivationException in logs
Resolved in Pega Version 8.1.9
The exception "One or more properties could not be serialized during passivation and have therefore been lost. They will not be available on activation. Please ensure that all property data is Serializable" was observed in the logs. Investigation showed there was an HTML fragment in 'pzGridOpenAction' that was adding non-serializable properties to the clip board. This did not cause a functional issue, but has been resolved by modifying the way the system obtains and reuses the class definition.
SR-D91344 · Issue 560624
Resolved PageCannotBeSerializedForPassivationException in logs
Resolved in Pega Version 8.2.8
The exception "One or more properties could not be serialized during passivation and have therefore been lost. They will not be available on activation. Please ensure that all property data is Serializable" was observed in the logs. Investigation showed there was an HTML fragment in 'pzGridOpenAction' that was adding non-serializable properties to the clip board. This did not cause a functional issue, but has been resolved by modifying the way the system obtains and reuses the class definition.
INC-147457 · Issue 621709
Elapsed time in Work History Table includes sub-flow
Resolved in Pega Version 8.5.3
Elapsed times were not captured when an assignment was in a wait shape followed by a utility which set a ticket and moved the assignment to a sub-flow. Investigation showed that when flow execution is in a sub-flow and a ticket is raised, the assignment in sub-flow was removed but audit history was not captured. To handle this scenario, the functions pzCleanSplitForTicket and pzRemoveFlowForTicket have been added, and FlowMethodBody FUA has been modified to include pzCleanSplitForTicket instead of CleanSplit
SR-C36306 · Issue 389694
Handling added for double-click on previous step in TreeNavigation7
Resolved in Pega Version 8.1
After configuring a screen flow navigation that utilized the TreeNavigation7 Section rule, double clicking on a previous step generated the error "Modal Dialog: Ajax Call Failure!".On double click, the onclick on <li> tag was executed and throwing the callback failure alert which was not expected, causing the system to skip the execution of the "nodeExpandCollapse" function in TreeNavigation section. This has been fixed.