Resolved Issues

Repository Delete API updated for better use with cloud storage

Previously, the Repository Delete API immediately checked if a file existed after attempting to delete it. When deleting files in S3, the file may not be immediately removed: due to S3's eventual consistency policy, the file could still exist at the time Pega was attempting to verify the deletion but be "deleted" according to Amazon. This caused a false alert that the file deletion was unsuccessful, leading to alert emails being sent and the Manifest file not being created, and in some cases generating an exception. To resolve this issue, the logic in Repository Delete that checked if file existed after attempting to delete it has been removed.

Repository Delete API updated for better use with cloud storage

Previously, the Repository Delete API immediately checked if a file existed after attempting to delete it. When deleting files in S3, the file may not be immediately removed: due to S3's eventual consistency policy, the file could still exist at the time Pega was attempting to verify the deletion but be "deleted" according to Amazon. This caused a false alert that the file deletion was unsuccessful, leading to alert emails being sent and the Manifest file not being created, and in some cases generating an exception. To resolve this issue, the logic in Repository Delete that checked if file existed after attempting to delete it has been removed.

Added when check for Strategy and Event Strategy to preserve pagelist property

When editing a test case that has been built from a strategy, clicking on the 'add properties' link in the side panel was not working. This was traced to the strategy rule being loaded each time while the data page is only loaded once per session, and has been resolved by adding a 'when' condition to the Strategy and Event Strategy rule that will check for the existence of an embedded page before the pagelist property which displays results is removed.

JavaILCompiler updated to skip a type convert when generating code for a ternary operation

A compilation error was generated when attempting to save a Data Transform with a java expression giving the ternary as boolean. In this case, the pyWorkPage.Channel was set to  @java("tools.findPage(\"TempInputAccelPage\").getProperty(\"Channel\").getMessageCount()>0") ? "" : pyWorkPage.Channel.

The system previously used EL code generation, which had a gap which allowed such expression to work. Since the system now uses IL code generation, this expression failed. In order to ensure backwards compatibility, logic has been added to  JavaILCompiler to skip a type convert when generating code for a ternary operation where the source is ILProgramText (java expression).

UIKit 12 updated to ensure data pages are cleared when switching applications

When using UIKit 12, switching applications without logging off resulted in the 'Recent reports' list and Public Category containing reports and folders that belonged to the previous application. Investigation showed that the pyCMReportBrowserHeader function in UIKit 12 did not include the custom control "pzRBIncludes7", which clears the data pages. This has now been added to ensure that report browser data pages are now automatically cleared on app switch.

Resolved harness error after using pagination 'load more'

After using the Pagination 'load more' option and clicking on any of the newly loaded items, a blank harness was opened. This was traced to missing change tracking data for the newly loaded rows, and has been corrected.

Resolved harness error after using pagination 'load more'

After using the Pagination 'load more' option and clicking on any of the newly loaded items, a blank harness was opened. This was traced to missing change tracking data for the newly loaded rows, and has been corrected.

Resolved harness error after using pagination 'load more'

After using the Pagination 'load more' option and clicking on any of the newly loaded items, a blank harness was opened. This was traced to missing change tracking data for the newly loaded rows, and has been corrected.

Back/Previous years calculation fixed to use current year

In the year dropdown for Date control, the number of back/previous years was calculated based on the selected year and not from the current year. The calculation logic has been fixed to resolve this.

Div fixed for Add button using GridAction section include

After upgrade, using the "Add" button configured as a section include with pzGridAction caused UI issues. This was due to pzGridAction (@baseclass) not closing the div tag properly after calling pzGadgetInclude, and has been fixed.