Skip to main content

Keep company processes in sync with global process templates

Core Web App

There may need to be some optional controls to make this viable, but I'd love the option to sync a process I've installed from a global template into a client back with the global template. This would allow us to update a process at the global level and then filter that down to the areas in which it is used. This wouldn't necessarily need to be automatic, but the core capability would make this feature more usable long-term.

9 comments

This request was merged into another request

Comments9

  • Harlequin Zipper

    •

    Sep 22

    We currently use version numbers in process names, for example "Make Toast (v2)", so users can identify which process is assigned to a customer. This approach is cumbersome, as it relies on administrators manually updating the version number whenever a process is modified. It also increases the risk of inconsistencies when version numbers are forgotten or not updated correctly.

  • Apricot Berry

    •

    Jun 23

    yes please that saves so much time!

  • Turquoise Lake

    •

    May 17

    I really really need this. I've been contemplating scripting this outside of Hudu using the API. But this seems like it should be standard functionality.

  • Black Stream

    •

    Apr 26

    Came to say the exact same. When looking through processes within a company, it would be extremely helpful to have an indicator that the underlying GPT has changed, along with an option to update it or replace it with the new global. Would also be nice if we could archive a process without all the runs going to the museum.

    Every time I need to start a run I think of more things to add, and they end up in the local template, then the global is out of date.

  • Black Stream

    •

    Apr 25

    Any update on this? The ability to update existing company processes would make this much more usable for us.

  • Aquamarine Butter

    •

    Nov 12, 2024

    Please!!!

  • Amaranth Clock

    •

    Jan 31, 2024

    This is exactly what we need. For example if we wanted to add a step like "Setup Duo" to our onboarding - we have to then edit every template for every client which is not practical.

  • Apricot Hill

    •

    Aug 31, 2023

    Think this would make much more sense than having to recreate templates each time there is a change. It would be great if completed processes such as onboarding were also then flagged for change. Eg a new step is added to 'M365 setup' would then flag all companies with that specific step until they are updated again.

  • Plum Burrito

    •

    Jul 18, 2023

    Was coming here to add this.

    This is a great way to build out processes as you develop them, rather than having to wait for the perfect time to deploy across sites.

    One example could be onboarding. Where you add a new step like setting up GDAP, but it's also something you have to do across all current clients.

    Edit an onboarding process and be given two options

    1) Re-open process and the revised/added steps across all Companies

    2) Only apply to new companies

    Or perhaps a view where you can see the onboarding process in its current state across all companies, and you can select the companies you want to update with the latest version.