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

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

      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

        This is the controller panel for Smart Panels app

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

                Created:
                Updated:
                Resolved: