7.2.1 Release Notes

Improvements

• document state macro report has two new parameters to define sorting of the report

  • Sort: defines the value to sort by with the following options

    • Title

    • Updated

    • Created

    • Created by

  • Sort Order: defines the order of the sorting as either

    • ascending

    • descending

• workflow parameter information is now stored in the page JSON content properties and the value of a workflow parameter can be retrieved using CQL

Updates

• compatibility update for Confluence v8.7

• improved error handling in the workflow editor

• document states report macro updates

  • report displays dates as an exact date

  • parent parameter accepts the @self value reference

  • descriptions added for the parameters Columns and CQL filter in the macro editor

• Document Report now displays dates as an exact date

• Attach Activity utility generating page activity attachments is now ignored by any workflow triggers with the attachmentadded or attachmentchanged event to avoid triggering undesired actions

Bugfixes

• resolved an issue using wiki markup to format the display of text in the add-comment macro

• fixed an issue using the parent filter in the document states report and the document stats report page macros

• fixed errors in the workflow translator translating a workflow if it included either

  • blank spaces, tabbed spaces or new lines in the workflow description

  • a description for an approval

• fixed an edge case that prevented updating the properties for app reports

• fixed a problem saving a workflow if more than one value reference was used for the user or group values in the set-restrictions macro

• fixed a problem attaching CSV files when running the Attach Activity utility

• fixed an issue that limited the number of states displayed in the document management report

• resolved some use case errors in the document activity data upgrade pre-checks

• fixed a performance problem (introduced in v6.17.10) for an applied page workflow

• fixed a bug that caused the page restrictions modification trigger action to be set on page creation

• resolved an error displayed when trying to access the app global configuration