Uploaded image for project: 'FlightPath'
  1. FlightPath
  2. FLPATH-1012

Workflow timeline

XMLWordPrintable

    • Workflow timeline
    • False
    • Hide

      None

      Show
      None
    • False
    • To Do
    • 0% To Do, 0% In Progress, 100% Done

      Create a new Timeline component using React Flow lib that depicts the non linear nature of serverless workflows to replace the current Timeline.

       

      The component should take the workflow and execution data recovered from SonataFlow in order to present a Top-Down workflow based only on the executed states. This way it shall be possible to visualize the executed branches of the workflow from the timeline perspective.

      The timeline must follow the original design of the workflow. It means that in case of loops or execution overlap, states executed multiple times, additional nodes won't be rendered to represent those nodes executed multiple times. A badge with the number of executions shall be added instead to indicate the number of executions/instances of that state. 

      There is no need to include the Start and End nodes in the timeline.
      Only executed states shall be included in the timeline, any other information shall be part of the state such as timestamp, success/error, icons, etc.

       

      User profiles:

      Note: For the initial implementation of the component only the "Execution" profile should be considered. The "Developer" profile is the next step and it makes sense only if it is possible to recover detailed and relevant data about the workflow execution from SonataFlow from the developer / authoring perspective. 

      Execution

      User that just runs workflows.

      This user needs only basic information about the execution of the workflow:

      • Executed States
      • Status Success/Fail
      • Timestamp

      Developer/Authoring

      This user needs more information about the execution of the workflow for analysis and troubleshoting.
      We should provide as much information as possible about the execution of the workflow.

      Currenttly there are restrictions about the information that could be provided by SonataFlow about individual states and it's execution context.
      It is something that must be discussed in the future to provide relevant data from the developer / authoring perspective.

            brotman@redhat.com Bat-Zion Rotman
            jkilzi@redhat.com Jonathan Kilzi
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: