-
Notifications
You must be signed in to change notification settings - Fork 11
Admin Dashboard Features
The Admin Dashboard is currently in a half-working state.
It successfully accomplishes several very difficult tasks, including:
- Parsing a
WfSpec
and displaying it on the screen - Parsing a
WfRun
and displaying it, and also highlighting the nodes that have already been run. - Displaying a
TaskRun
node inside aWfRun
. This is very well-done and also tricky.- Displaying multiple
TaskAttempts
- Displaying the status/output of each attempt
- Displaying stacktraces/errors/failures
- Displaying multiple
- Displaying a
UserTaskRun
inside aWfRun
.- Audit log
- Output/results
- Ownership
- Fields
- On the
WfSpec
page, aTask
node only shows the variables of theTaskDef
but doesn't yet show theVariableAssignment
s (which is how the parameters to theTaskRun
are assigned from theWfRun
variables)
- The
WfRun
search does not have all possible values for theLHStatus
enum, for example it is missingEXCEPTION
. - The
TaskRun
search does not mirror theTaskStatus
enum. - For all searches, the calendar is incredibly hard to use, unintuitive, and often buggy.
- Ability to search for a
WfRun
by the value of itsVariable
s, using eitherrpc SearchWfRun
orrpc SearchVariable
- Clicking on a
TaskRun
orUserTaskRun
from the search bar correctly navigates to the rightWfRun
, but it does not highlight the right node.
- We should display
VariableMutation
s on the Edges.
- Failure Handlers should be displayed on every
Node
type, not justExternalEvent
s. - For a
NodeRun
that has aFailure
, there should be an icon on thatNodeRun
to indicate that there was a failure- It should be
yellow
if theFailure
has been handled - It should be
red
if theFailure
was not handled, and the wholeNodeRun
failed.
- It should be
- The icon to represent that a
Node
has aFailureHandler
shouldn't be a warning light. It should maybe be an overlapping circle, like a BPMN Boundary Event. - For a
NodeRun
that has aFailure
with a Handler, clicking on theFailure
in the sidebar should take us to theFailureHandler
ThreadRun
.
The WaitForThreads
NodeRun should show the status of all of the child ThreadRun
s that we are waiting for. Additionally, we should now handle the new feature of a "per-child" FailureHandler, which handles the failure of a child individually. This didn't exist until after the 0.7.2
release, so this is a new node.
PR #696 introduced the concept of WorkflowEvent
, in which a Node
can throw a WorkflowEvent
. When you click on a WORKFLOW_EVENT
NodeRun
, you should be able to see the content of the WorkflowEvent
that was thrown.
User Tasks have the concept of "Reminder Tasks" which allow engineering teams to schedule tasks to be executed upon certain lifeccyle hooks. These lifecycle hooks are not shown in the current user task sidepanel, nor are the TaskRun
s that are scheduled.