SR-A100923 · Issue 269979
Property null check added to TrackSecurityChanges
Resolved in Pega Version 7.2.2
When using the out-of-the-box TrackSecurityChangesLogic activity in an application to track the property changes, an Null Pointer Error was generated when saving the property. This was due to a missing null check for the property, and has been fixed.
SR-A94690 · Issue 261686
Report Editor displays Associations
Resolved in Pega Version 7.2.2
When using a custom activity to display properties in the data explorer, the "More" link is not displaying the associations when added. This was an error in the logic which determined whether pyReportEditorProperties exists for the class or not, and has been fixed in pzGetCustomPropsForTreeGrid.
INC-191356 · Issue 679163
External Input setting available on Strategy Batch Performance Test
Resolved in Pega Version 8.7
It was not possible to specify the External Input as part of a strategy when using a Batch Performance test. This has been resolved by updating the pzDisplayTestStrategyContext When condition to "true" the so external input selector is properly displayed.
INC-191902 · Issue 677412
Updated security for importing Excel to a decision table via a delegated rule
Resolved in Pega Version 8.7
An error was seen when attempting to import an Excel file into a delegated decision table when using the case manager portal. This has been resolved by correcting a BAC issue for decision table import in the pzRuleDeclareDecisionTableStandard.js file.
SR-A39964 · Issue 259183
Corrected unexpected rounding of decimal property
Resolved in Pega Version 7.2.2
Decimal value was incorrectly being rounded in the control for a decimal property which has Use Validate in place. This happened when the edit validate rule on the property failed and was then formatted using Double instead of BigDecimal. This has been fixed by updating the pxNumber control generation logic in the pzGenerateTextInput RUF to use BigDecimal instead of Double.
SR-A39964 · Issue 265562
Corrected unexpected rounding of decimal property
Resolved in Pega Version 7.2.2
Decimal value was incorrectly being rounded in the control for a decimal property which has Use Validate in place. This happened when the edit validate rule on the property failed and was then formatted using Double instead of BigDecimal. This has been fixed by updating the pxNumber control generation logic in the pzGenerateTextInput RUF to use BigDecimal instead of Double.
SR-115912 · Issue 168208
Updated failure handling for Word editing with IE
Resolved in Pega Version 7.1.7
When using IE, failure to load correspondence for editing in Word generated the message "Error: Loading Open Authoring Control". This was caused by the carried-over use of a span tag that is not valid under HTML5, and has been corrected with updated JavaScript.
INC-172521 · Issue 651553
Email template content visible in user application
Resolved in Pega Version 8.7
An issue was seen with email templates functionality where the body content given during the email template creation was not visible when the template was used in the application by an end user. This was a missed use case for recent security updates, and has been resolved.
SR-A67007 · Issue 255075
Catch improved to close Message Explorer connections
Resolved in Pega Version 7.2.2
When using the Message Explorer functionality provided on the JMS Connect rule form, it only allows a number invocations equal to the size of the connection pool. Due to an issue with releasing the connections when using Resource Reference mode or IIOP protocol, the pool was being exceeded and the error "Couldn't create connection object" appeared. This has been fixed by changing the conditional catch for closing the connection with a more effective try catch.
INC-139619 · Issue 597334
Agent tracing handling updated
Resolved in Pega Version 8.5.2
When attempting to trace agents the error "Unable to trace the agent" appeared on screen. Investigation showed that the data page used by the Tracer was not always available in a thread that was displaying the section, most commonly if the section was using deferred loading. This has been resolved by using a data page available in a thread that opens a Tracer's section.