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

I cannot distinguish cascading from non-cascading user operations in the user operation log

    XMLWordPrintable

Details

    • Bug Report
    • Resolution: Won't Fix
    • L3 - Default
    • None
    • None
    • engine
    • None

    Description

      It should be possible if an operation was executed with cascade option or not.

      For example ManagementService#suspendJobDefinitionById(String jobDefinitionId, boolean suspendJobs) with suspendJobs=true does only write one op log entry for the job definition. It is not possible to tell whether jobs were suspended afterwards by using the op log.

      In CAM-4163, we have implemented this such that two entries are written, one for the job definition and one for the jobs the operation cascades to. So the behavior should be consistent for all the cascading methods.

      mgm-controller-panel

        This is the controller panel for Smart Panels app

        Attachments

          Issue Links

            is related to

            Feature Request - A new feature of the product, which has yet to be developed. CAM-4163 I can see job priority changes via API in the user operations log

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

            Activity

              People

                Unassigned Unassigned
                thorben.lindhauer Thorben Lindhauer
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  Salesforce