Feature Requests

Check out this workflow. In the "prep data" step I'm determining if it's test data or "real" data, and I want to only run the downstream steps if it's "real". I set up a javascript path condition !state.test which does the trick, but I have to replicate it across all paths. Does anyone else do this, and would re-usable filter criteria be useful?

In the inspector, when I'm editing my job code, I can't run my job unless I have some input. Well, okay, fair enough, but I also find myself setting {} to my input _all the time_. I'd love it if I could just run the job and, if I haven't specified an input, for {} to be used. The hipster alternative to this issue is just to remember which input I used last for my job and just use that again. That will at least reduce the amount of times I have to type {}. But perhaps this isn't entirely safe? I don't want to accidentally re-run production data through the workflow

We regularly put out security and feature releases to our adaptors. But we don't tell anyone about it :( I'd love to see a feature where, when an adaptor is released, we email the admins/editors of any workflows which use that adaptor to say that the adaptor has changed. We could include the release notes in the email (and we will get better at writing release notes too) This obviously needs to be batched up per user and maybe rate-limited to one email per day. Perhaps we can scan at 1am or something and send out a daily report.

We are encountering challenges while testing new adaptor changes on the Lightning platform because the adapter must first be released on npm before it can be pulled into the Lightning environment. This creates a bottleneck in the development workflow, leading to delays and inefficiencies in testing and validation.

Right now when a user is building a workflow and adds a new step, after they select an Adaptor the Version defaults to "latest", which means this workflow will ALWAYS use the latest version of the adaptor. This creates problems if there is a major adaptor version release and suddenly users' workflows get auto-upgraded to the "latest" version. We should default the Version to the most specific version... but then the step should be version-locked to avoid this scenario of a mistaken auto-upgrade to an incompatible version.

Right now if testing a workflow in the Inspector view, I can see a list of 5 Inputs I've recently used... but I have no idea what these inputs are (it's almost impossible to remember the uuid names), when they were created, and what they are for. Therefore, I'm often saving test cases I like in Github with human-friendly names (e.g., patientZeroWithReferral.json)... and then re-pasting this input again whenever I need it into the Input panel (bc I can never recall the UUID it's saved under). It would be great to be able to maintain a collection of Inputs that I expect to use regularly for testing, and be able to give them my own names/labels and maybe even tags. I'd also like a view where I can see ALL Inputs I have saved for a project so that I can edit/delete these over time. Also, as I create a new Input -> there is no JSON validation or formatting to help me check what I'm inputting until I click "Create New Work Order". This Input view also has no JSON formatting/Monaco editor view: https://app.openfn.org/projects/57862287-23e6-4650-8d79-e1dd88b24b1c/dataclips/f96ec031-7cf2-41e6-81b1-57553cb48e29/show And how cool if Inputs could also eventually be integrated with Github.

When designing workflows, it's common to create several seperate but connected workflows representing business processes, and for those workflows to call each other. Right now this is done by creating a HTTP step and calling out to an endpoint at openfn. A better solution would be to create a Step, set its Type to "Trigger Workflow" (or something), and then select the workflow name from a picklist. The Step would have a special icon to look less like a regular step. The Step could have interactions, like double-clicking to open the Workflow in a new window. Or maybe even expanding the other workflow INSIDE the primary one, so you can see all the steps in one place, but the two workflows are still visually distinct

In the history page that lists work orders, I would like to see how that workflow was triggered(cron or web hook) or if it was manually triggered by a users. Sometimes I would be browsing through the history looking for the run I triggered but I wouldn't be able to tell if there are multiple work orders for that workflow(triggered by different users at a similar time)

Right now super users have to (1) create users, and then (2) go into the DB via the backend to manually change the role of these users from "admin" to "super".

As a OpenFn workflow engineer, I would like to see when my project was last synced to Github from and last synced from Github in the Sync to Github page. Currently I'm only able to see that the repo is properly configured and the branch its configured to, but i would like to see when it was last successfully synced to/from Github.