Uploaded image for project: 'Serverless logic'
  1. Serverless logic
  2. SRVLOGIC-1

[core] New visualization of workflows in editor

    XMLWordPrintable

Details

    • False
    • None
    • False
    • 0
    • 0% 0%
    • 2022 Week 32-34 (from Aug 8), 2022 Week 38-40 (from Sept 19), 2022 Week 41-43 (from Oct 10)

    Description

      Motivation

      Current visualization of serverless workflows is insufficient. It was quickly developed in the CNCF community and doesn’t provide enough information to understand the flow, branching, parallel execution, sequences, and operation calls.

      Goal

      Design and implement new visualization of workflows

      Scenarios

      As a developer, I need to verify my written workflow against a visualization so that I can see whether it will run how I wrote it.

      As a developer, I need to see where there is a gap / missing part of my workflow so that I can “connect the dots”.

      As a developer, I need to see where the workflow branches with conditions or parallel execution and transitions to next states.

      As a developer, I need to see how the workflow communicates over events so that I can verify all events are sent in all situations.

      Expected outcomes

      A design / mockup of a new workflow visualization guidance from UI/UX team

      Read-only representation of a serverless workflows

      VS Code editor for serverless workflow updates its visualization of the workflow code

      Attachments

        Issue Links

          incorporates

          Task - Represents a small unit of work that is not end-user facing. KOGITO-7893 Stunner should now be the default workflow viewer

          • Critical - To be worked on immediately following BLOCKER issues.
          • Resolved

          Task - Represents a small unit of work that is not end-user facing. KOGITO-6981 SWF Editor - Viewer Look&Feel

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved
          is blocked by

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. KOGITO-7732 QE serverless logic tasks for second iteration of the tooling

          • Critical - To be worked on immediately following BLOCKER issues.
          • Resolved

          Task - Represents a small unit of work that is not end-user facing. KOGITO-7053 SWF Viewer - Community Documentation

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Resolved

          Task - Represents a small unit of work that is not end-user facing. KOGITO-7559 Validate new visualizations provided by UX are implemeted and used properly

          • Critical - To be worked on immediately following BLOCKER issues.
          • Resolved

          Activity

            People

              eignatow Eder Ignatowicz
              ibek1@redhat.com Ivo Bek
              Dominik Hanak Dominik Hanak
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: