Doing a software catalog redesign at work and digging into the fulfillment logic to see 140+ legacy workflows that I have to convert into a reusable Flow thats updated to use new technology and honestly my brain hurts more than it should. Hasn't been touched in like 6 years other…
Commit
d29c6ec
I’d start by grouping those workflows by trigger, approvals, and side effects, then capture a few real input/output examples from each group. That gives you something concrete to compare when the reusable Flow takes over. Are most of the 140 different, or copies with small…
Different for the most part. Based on downloadable it has a fulfillment workflow and a few others that handle approvals and reclamation. It’s a mess of steps and checks. Going to be a rough load to work through
That sounds like a fun project. I am working on something similar, but the existing workflows are all over the place, including different sytems, departments and technologies. A lot of these workflows still include manual and paper-based processes.
We're now building a workflow engine from scratch, because existing solutions either don't have the features we need, or they are ludicrously expensive.
commit d29c6ec