Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Display executed sequence flows in Cockpit history #2553

Open
ThorbenLindhauer opened this issue Nov 11, 2020 · 0 comments
Open

Display executed sequence flows in Cockpit history #2553

ThorbenLindhauer opened this issue Nov 11, 2020 · 0 comments
Labels
scope:cockpit Changes to the Cockpit webapp. type:feature Issues that add a new user feature to the project.

Comments

@ThorbenLindhauer
Copy link
Member

ThorbenLindhauer commented Nov 11, 2020

This issue was imported from JIRA:

Field Value
JIRA Link CAM-12737
Reporter NYBzR2x
What is this name? This pseudonym name was generated based on the user name in JIRA to protect the personal data of our JIRA users. You can use this identifier to search for issues by the same reporter.
Has restricted visibility comments true

User Story (Required on creation):

When reviewing process instances in Cockpit's history view, I want executed sequence flows highlighted so that I can understand the execution path of the process instance fast.

Functional Requirements (Required before implementation):

  • Sequence flows that have been executed are marked in the process diagram (optional: with a badge that indicates how often they have been executed)

Technical Requirements (Required before implementation):

  • The information which sequence flows have been executed is stored in history
  • This is done with minimal overhead, e.g. having one extra history row per executed sequence flow would inflate the size of history databases significantly.

Limitations of Scope (Optional):

  • The history view on the process definition page does not display sequence flows (assuming that this become useless quickly as soon as all flows have been taken at least once)

Hints (Optional):

  • An idea to keep the additionally stored history data minimal could be to store the sequene flow that was executed to enter an activity along as an attribute of the corresponding history activity instance (needs clarification with how the result will look like in case of async continuations)

Links:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
scope:cockpit Changes to the Cockpit webapp. type:feature Issues that add a new user feature to the project.
Projects
None yet
Development

No branches or pull requests

1 participant