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

UX for instance details page

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • orchestrator-ui
    • None

      Please consider:

      • Add a "Business Key" property to the details. This property may or may not be present (related to FLPATH-795).
      • The "Assessment Results" card may or may not be present. Should we simply hide the card or adapt the UI if it is not shown?
      • When the status is "Error", how/where should we show the error message?
      • Add a simple timeline to the page (see the attached videos). Context: The timeline shows states that have been executed. This is useful when workflows do not run as expected. Examples: i) visualize which state threw an error; ii) visualize which path the workflow took.
      • Add "Variables" to the page (see the attached videos). Context: Besides the input variables, other variables can be created during the workflow execution. It could be important for users to see the values of such variables.
      • Add "Timers" to the page (see the attached videos). Context: Workflows can define timeouts in states. If a particular state is not executed within the defined timeout, the workflow can take a different path. So, it could be important for users to know how much time a state has.

              nirfarkas Nir Farkas
              jkilzi@redhat.com Jonathan Kilzi
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: