Uploaded image for project: 'camunda BPM'
  1. camunda BPM
  2. CAM-8301

History Cleanup: Improve Cleanable Data List

      The list/table of cleanable data has a couple of issues we need to address:

      1. Scope
      We're currently showing all versions of all process definitions (PDs) regardless whether they have a) finished instances and b) cleanable instances. This feels odd when looking at the page, as it will simply result in a list of all versions of all PDs, that is completely out of scope of the current usage context (History Cleanup) and will result in a long, unwieldy, and hard-to-navigate list.

      We will need to show items with 0 clanable instances, since History-Time-to-Live can be configured here and this can/will affect the scope of the current view. Still, showing everything seems impractical.

      Possible Solution: Show only items that have >0 finished instances, since these might get inside the scope of the current view if HistoryTimeToLive. Items with 0 finished instances will never be in scope of this view so the ycan (and should) be omitted.

      2. Sequence of data
      The sequence of data/columns in the list/table does not seem logical or natural:

      [TBD…]

      3. Title/headline
      In "Cleanable Instances Report", "Report" is obsolete and should be removed.

        This is the controller panel for Smart Panels app

            [CAM-8301] History Cleanup: Improve Cleanable Data List

            We decided the following:

            • the table should contain the tenant id
            • the columns should be re-ordered: [Process|Case|Decision] Definition | Version | Tenant | ...
            • the report is sorted by finished instances in descending order

            Roman Smirnov added a comment - We decided the following: the table should contain the tenant id the columns should be re-ordered: [Process|Case|Decision] Definition | Version | Tenant | ... the report is sorted by finished instances in descending order

            Fabian added a comment -

            Ticket is reopened as sorting functionality isn't implemented yet. Currently, the required changes are made in the backend.

            Fabian added a comment - Ticket is reopened as sorting functionality isn't implemented yet. Currently, the required changes are made in the backend.

              michael.schoettes Michael Schoettes
              franz.heidl Franz
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: