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

Using Java API, I can set removal time for standalone decisions asynchronously

    XMLWordPrintable

Details

    • Feature Request
    • Resolution: Fixed
    • L3 - Default
    • 7.11.0, 7.11.0-alpha5
    • None
    • engine
    • None

    Description

      AT

      • Removal time is calculated based on the engine's configuration settings for the removal time strategy (start, end, none) and the TTL of the decision definition: 
        Batch batch = historyService.setRemovalTimeToHistoricDecisionInstancesAsync()
      .byQuery(query)
      .calculatedRemovalTime()
      .executeAsync();
        • if removal time strategy is set to ...
          • start or end: removal time = evaluation time + TTL
          • none: no update is performed
      • Removal time can be set to an absolute value or to null: 
        Batch batch = historyService.setRemovalTimeToHistoricDecisionInstancesAsync()
      .byQuery(query)
      .absoluteRemovalTime(new Date())
      .executeAsync();
        • the engine's configuration settings in terms of the removal time strategy (start, end, none) are disrespected
      • the fluent builder offers a flag #hierarchical; All instances which are present in the hierarchy are updated
      • Throw BadUserRequestException if ...
        • no historic decision instances can be found
        • no mode (i. e. calculatedRemovalTime / absoluteRemovalTime) was selected
        • no query was defined

      mgm-controller-panel

        This is the controller panel for Smart Panels app

        Attachments

          Issue Links

            is related to

            Bug Report - A problem which impairs or prevents the functions of the product. CAM-10249 Removal time is not cleared by calculation

            • L3 - Default - Minor issue or issue with existing workaround, feature requests and questions
            • Closed

            Feature Request - A new feature of the product, which has yet to be developed. CAM-10224 I can set a removal time by instance ids via batch asyncronously

            • L3 - Default - Minor issue or issue with existing workaround, feature requests and questions
            • Closed

            Task - A task that needs to be done. CAM-10173 Introduce specific create auth permission for all removal time batches

            • L3 - Default - Minor issue or issue with existing workaround, feature requests and questions
            • Closed

            Task - A task that needs to be done. CAM-10174 Introduce operation logs for all removal time batches

            • L3 - Default - Minor issue or issue with existing workaround, feature requests and questions
            • Closed

            Task - A task that needs to be done. CAM-10175 I can read documentation about removal time batches

            • L3 - Default - Minor issue or issue with existing workaround, feature requests and questions
            • Closed

            Task - A task that needs to be done. CAM-10176 Using REST API, I can set a removal time via batches asyncronously

            • L3 - Default - Minor issue or issue with existing workaround, feature requests and questions
            • Closed

            Task - A task that needs to be done. CAM-9967 History data created with versions < 7.10.0 are not removed by removal-time-based strategy

            • L3 - Default - Minor issue or issue with existing workaround, feature requests and questions
            • Closed

            Activity

              People

                Unassigned Unassigned
                tassilo.weidner Tassilo Weidner
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  Salesforce