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

Return top-level decision instance id in evaluation result

    • Icon: Feature Request Feature Request
    • Resolution: Duplicate
    • Icon: L3 - Default L3 - Default
    • None
    • None
    • dmn-engine

      User Story (Required on creation):

      After evaluating a decision definition via API (Java or REST), I want to find all decision instances that were involved in creating the result of the evaluation. Since all involved elements are connected by a root decision instance ID, I want to receive this ID together with the evaluation result to allow querying with this later on.

      Functional Requirements (Required before implementation):

      • Receive an identifier in the evaluation result that allows searching for all involved decision instances

      Technical Requirements (Required before implementation):

      • Return a unique id in the decision evaluation result that is attached to all involved decision instances - the rootDecisionInstanceId of the historic decision instance events looks like a suitable candidate here.

      Limitations of Scope (Optional):

      • This will only work when an appropriate history level is set in the engine configuration

      Hints (optional):

      • By returning the rootDecisionInstanceId, we can reuse the historic decision instance search with a rootDecisionInstanceId parameter to find all involved elements.

        This is the controller panel for Smart Panels app

            [CAM-14351] Return top-level decision instance id in evaluation result

            Hi dgilmour22,

            thanks for your proposal!

            We will have a look at it as soon as possible and update the ticket with any feedback we have.

            Best,
            Tobias

            Tobias Metzke-Bernstein added a comment - Hi dgilmour22 , thanks for your proposal! We will have a look at it as soon as possible and update the ticket with any feedback we have. Best, Tobias

            Hi dgilmour22,

            thanks again for your proposal. In order to determine how we can best help you here, please provide the following:

            • A description of the results you currently receive for which API call
            • How you would like to see this information being enhanced by further data
            • How you would use this new data in follow-up API calls you currently cannot perform due to missing data

            This will help us in determining if this information is not already available elsewhere or can be retrieved already with an existing method.
            Also,

            Thanks and best,
            Tobias

            Tobias Metzke-Bernstein added a comment - Hi dgilmour22 , thanks again for your proposal. In order to determine how we can best help you here, please provide the following: A description of the results you currently receive for which API call How you would like to see this information being enhanced by further data How you would use this new data in follow-up API calls you currently cannot perform due to missing data This will help us in determining if this information is not already available elsewhere or can be retrieved already with an existing method. Also, Thanks and best, Tobias

            Doug Gilmour added a comment - - edited

            Hi @Tobias Metzke-Bernstein

            I added the details to the Description field above. Let me know if you need more info.

            Doug Gilmour added a comment - - edited Hi @Tobias Metzke-Bernstein I added the details to the Description field above. Let me know if you need more info.

            Hey dgilmour22,

            thanks again for raising this and also for the details you provided. This helped us in understanding your request a bit better.

            In general, your request is valid in the scope of the product and I think it might be a useful addition. We will consider this feature in the next planning sessions of the product. However, this does not yet mean we will work on this in the near future.

            If you would like to contribute code here in order to speed up the process, let us know and we can help you get started with a pull request in our code repository.

            Best and thanks again,
            Tobias

            Tobias Metzke-Bernstein added a comment - Hey dgilmour22 , thanks again for raising this and also for the details you provided. This helped us in understanding your request a bit better. In general, your request is valid in the scope of the product and I think it might be a useful addition. We will consider this feature in the next planning sessions of the product. However, this does not yet mean we will work on this in the near future. If you would like to contribute code here in order to speed up the process, let us know and we can help you get started with a pull request in our code repository. Best and thanks again, Tobias

            Doug Gilmour added a comment -

            I'm not much of a developer at this point to assist, but I'll poke around.

            I am a little concerned about the change in the title of this issue though. The product already facilitates the querying of all of the DMN elements that went into a Decision Instance.. The problem is that after a Decision is Evaluated, I have no idea what the evaluated instance ID is. (From the client perspective) So I can't use the existing query functionality.

            Doug Gilmour added a comment - I'm not much of a developer at this point to assist, but I'll poke around. I am a little concerned about the change in the title of this issue though. The product already facilitates the querying of all of the DMN elements that went into a Decision Instance.. The problem is that after a Decision is Evaluated, I have no idea what the evaluated instance ID is. (From the client perspective) So I can't use the existing query functionality.

            Hey dgilmour22, thanks for the feedback. I see your point and I adjusted the description and title. Let me know if that makes more sense here.

            Tobias Metzke-Bernstein added a comment - Hey dgilmour22 , thanks for the feedback. I see your point and I adjusted the description and title. Let me know if that makes more sense here.

            Doug Gilmour added a comment -

            Looks great. Thanks.

            Doug Gilmour added a comment - Looks great. Thanks.

            Doug Gilmour added a comment -

            It's too bad this one was marked as the duplicate. It was created first. 

            Doug Gilmour added a comment - It's too bad this one was marked as the duplicate. It was created first. 

              Unassigned Unassigned
              dgilmour22 Doug Gilmour
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: