[DMP 2024] UX Redesign for History Page
name: OpenFn
about: C4GT Issue: UX Redesign for the OpenFn
title: "Improved UX for the History page"
labels: UX Design,OpenFn,History
assignees: ''
Description
OpenFn is an open source platform for data and workflow automation which provides users with the two different types of interface: The CLI and Lightning -- a web based platform that provides a GUI/Canvas for users to design their workflows, write job expressions and run work orders.
The History page is crucial to the user experience on the web platform (Lightning) which allows users to inspect, debug and reprocess work orders. This technically provides auditing and recoverability functionalities across workflows and their respective work orders. Through the history page, a user can do the following:
- Filter work orders by name, status, work order received time and work order last activity time
- Search through previously run work orders based by name, id or a log output
- Inspect or retry a run
What are we looking to fix here:
Filtering:
We want an interface that accommodates multi-step and cascaded filtering between workflows and jobs, status and reasons, and relevant timestamps (work order received and last activity). For the timestamp filters, we want to filter events that happened before, since or between a time window.
Managing multiple runs associated with a work order:
A single work order can have multiple runs. (Each run has many “steps”.) If the first attempt to refer a patient from System A to System B fails, it can be said that the first run “failed” and the work order is in a failed state. An admin can inspect and retry that work order, which will then create a new run that is linked to the existing work order, and if it succeeds the work order will enter the “success” state. We want users to be able to :
- retry a work order that has been previously executed
- retry a run from a specific step in a work order
Image of a previously run work order and an associated step
Reference: Most CI/CD pipeline platform offer a great UX for retrying a specific work order or retrying from a step in the work order and we would love to take some lessons from such platforms.
Current Design of the History Page
Expected Outcome
A high fidelity design of a history page user interface and experience that makes it easier for to audit, inspect and retry failed jobs from specific steps in a previously attempted workflow.
Acceptance Criteria
- [ ] Users should be able to filter work order history by their workflow, run state (failed, success, lost...) and time.
- [ ] Easier navigation for for users between inspecting jobs and retrying failed jobs
- [ ] Responsive design
Product Name
Product Name: OpenFn
Project Name
Project Name: UX Redesign for History Page
Organization Name:
Open Function Group
Domain
Other
Tech Skills Needed:
Figma
Mentor(s)
Complexity
High
Category
UI/UX/Design
Hey @christad92 was interested in this project.
should we only make the design or also we need to code it?