Feature #19482
open
Linkable view panel for registered workflows
0%
Description
there is no way to give someone a page to a registered workflow in wb2 because there is no registered workflow specific page - and when you "run" it it just goes to a generic run page like this -- https://workbench2.pirca.arvadosapi.com/run-process
this makes it really hard to even direct someone to a workflow to run if you have to send them to the project folder that contains it.
Design sketch:
Use a layout that's similar to the workflows panel.
- Details panel (last modified, user that modified it, git details from the definition)
- Inputs panel
- Outputs panel
- Files panel displaying the collection containing the workflow text
- Get the workflow that was wrapped by looking into the wrapper workflow step and get the "run: keep:..." part that references the collection with the actual workflow
Stretch goal: render using https://github.com/rabix/cwl-svg#20094- Need to be able to navigate to it from projects list / by URL path
- Side panel (already exists)
- Button to launch the workflow ("Run" button already exists on the side panel)
- Assume the structure of the "wrapper" workflow produced by Arvados cwl runner since 2.4.4, if it is registered by an earlier version and doesn't match, just don't display things that can't be displayed.
Files
Related issues
Updated by Peter Amstutz 5 months ago
- Target version set to 2022-11-09 sprint
- Assigned To set to Peter Amstutz
- Category set to Workbench2
Updated by Peter Amstutz 5 months ago
- Target version changed from 2022-11-09 sprint to 2022-11-23 sprint
Updated by Peter Amstutz 5 months ago
- Target version changed from 2022-11-23 sprint to 2022-12-07 Sprint
Updated by Peter Amstutz 4 months ago
- Target version changed from 2022-12-07 Sprint to 2022-12-21 Sprint
Updated by Peter Amstutz 4 months ago
- Target version changed from 2022-12-21 Sprint to 2023-01-18 sprint
Updated by Peter Amstutz 4 months ago
- Target version changed from 2023-01-18 sprint to 2023-02-01 sprint
Updated by Peter Amstutz 3 months ago
- Category changed from Workbench2 to Workbench2
- Subject changed from can't give someone a link to registered wf in wb2 to Linkable view panel for registered workflows
- Project changed from Arvados Workbench 2 to Arvados
- Tracker changed from Bug to Feature
Updated by Peter Amstutz 2 months ago
- Target version changed from 2023-02-01 sprint to To be groomed
Updated by Sarah Zaranek about 2 months ago
- Related to Story #20059: Redesign Register Workflow Panel added
Updated by Peter Amstutz about 1 month ago
- Blocks Feature #20094: Render workflow with cwl-svg added
Updated by Peter Amstutz about 1 month ago
- Target version changed from To be groomed to 2023-03-01 sprint
Updated by Peter Amstutz 29 days ago
Right-justify Run button.
Add three dot action menu.
Add standard items to context menu.
Fix breadcrumbs.
Updated by Peter Amstutz 29 days ago
- Related to Bug #19932: CLI, python, CURL examples show every example code twice added
Updated by Peter Amstutz 25 days ago
19482-wf-panel @ commit:c3bc34209f7dbbc80c62d8896af043c88cb6b9cf
developer-tests-workbench2: #1111
- Adds new route for workflow panel
- Displays details, Inputs, Outputs, and contents of the collection containing the workflow
- Context menu now has basic operations on workflow record
Updated by Stephen Smith 24 days ago
Aside from a couple notes it lgtm:
- The breadcrumbs don't show the workflow you are currently viewing as the last item similar to other areas - the parent location should probably be blue / link color similar to other pages since it navigates to a different location
- There seems to be some extra padding making the details card icon in the top left out of alignment with the other cards
- Not sure if it's intentional for now but the back button after pressing run process returns to the old run process multi step form
Updated by Peter Amstutz 22 days ago
- Target version changed from 2023-03-01 sprint to Development 2023-03-15 sprint
Updated by Peter Amstutz 17 days ago
Stephen Smith wrote in #note-23:
Aside from a couple notes it lgtm:
- The breadcrumbs don't show the workflow you are currently viewing as the last item similar to other areas - the parent location should probably be blue / link color similar to other pages since it navigates to a different location
I'm confused, you should be seeing the name of the workflow, was there some way you navigated to it that didn't work?
- There seems to be some extra padding making the details card icon in the top left out of alignment with the other cards
Good catch, I copied styling from collection panel when I should have copied it from the process panel. The collection panel has the same issue and to ensure consistent styling it should be migrated to use CardHeader/CardContent instead of just Grid.
- Not sure if it's intentional for now but the back button after pressing run process returns to the old run process multi step form
I tried this and it took me back to the workflow panel? But I know navigation is a bit fussy.
Updated by Peter Amstutz 16 days ago
19482-wf-panel @ arvados-workbench2|cd89fd24a8cdf7512a4352f1fc17101b225e32c4
Registered workflow panel and Collection panel use CardHeader/CardContent for more consistent styling.
Updated by Stephen Smith 15 days ago
- File simplescreenrecorder-2023-03-10_11.25.21.crop.mp4 simplescreenrecorder-2023-03-10_11.25.21.crop.mp4 added
- File simplescreenrecorder-2023-03-10_11.29.09.mp4 simplescreenrecorder-2023-03-10_11.29.09.mp4 added
For the breadcrumbs, I started by navigating directly to the workflow url (/workflows/tordo-7fd4e-8kruxiw4pv5huh3), it works fine when I look at a collection in the same project, and the parent project shows up fine in the sidebar as well, but navigating to the workflow consistently doesn't show the item - the side panel parent project also loses the blue highlight so that might be related.
I also added a video of the wf run form back button issue, I can press the browser back button to get back to the wf panel but the form back button goes back to the workflow selector
Updated by Peter Amstutz 10 days ago
- Target version changed from Development 2023-03-15 sprint to Development 2023-03-29 Sprint
Updated by Peter Amstutz 1 day ago
Stephen Smith wrote in #note-27:
For the breadcrumbs, I started by navigating directly to the workflow url (/workflows/tordo-7fd4e-8kruxiw4pv5huh3), it works fine when I look at a collection in the same project, and the parent project shows up fine in the sidebar as well, but navigating to the workflow consistently doesn't show the item - the side panel parent project also loses the blue highlight so that might be related.
I finally figured out why I couldn't reproduce it, we're looking at exactly the same workflow but you're looking at it in the "Shared with me" tree. When I look at something else in "Shared with me" I see the same behavior. Will fix.
I also added a video of the wf run form back button issue, I can press the browser back button to get back to the wf panel but the form back button goes back to the workflow selector
Ok. The browser back button does the right thing, but that "back" button at the bottom of the page is something else entirely. I'm not entirely sure there is a sensible fix here because that button works by switching the state to "step 1" rather than "navigate back". What do you think about just leaving it as-is? The plan is to rework Workflow launching and get rid of the two-step interface entirely in favor of creating an container request and editing it in place.
Updated by Peter Amstutz about 16 hours ago
19482-wf-panel @ commit:bf2e7c937e911629122eec14c29e8f6fa9b84aa6
developer-tests-workbench2: #1168
- Fixed breadcrumbs for Workflow panel. Also fixed first-time-load breadcrumb display for collections and processes because they had similar issues.
I'm not completely happy with the existing architecture, this feels like something where the breadcrumb control be tasked with monitoring the currently item and working backwards to determine how to correctly render breadcrumbs, without requiring an explicit resource-specific "load" function. Getting this right was much trickier than it should have been.
Updated by Peter Amstutz about 11 hours ago
Don't know if it is a flaky test or I broke something, re-running here