Allow the ability to pull changes to global process templates to client process templates. Obviously, this has to be done carefully due to potential individual changes to client templates.
Maybe any that haven't been customized should automatically update and any that have been customized shouldn't, but you should have the option
Amethyst Bagel
•
Nov 26, 2020
The way to do this would be to create a relationship with tasks between the global and client templates. In the event a task was modified on a client level it would break the relationship; when modified on the global level it'll update everywhere else as well. When the process itself was modified (structure changed or tasks added/removed) it'll update on all linked processes.
Yellow Nucleon
•
Jul 5, 2023
Just had this similar thought. We have a use case where you have to go to another location to look up a credential in another system. It would be great if we could create the global KB item and then allow it to be visible on the client level in an updated manner.
Also, the ability to select if it should be part of an export or not for that client.
Keep company processes in sync with global process templates
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.
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.
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.
Lime Sunbeam
•
Apr 13, 2022
We Agree, this is super important to keep processes upto date.
Bronze Mist
•
Aug 28, 2023
We need a way to keep the child processes up-to-date.
Harlequin Zipper
•
Dec 23, 2021
I think it's critical to allow the refreshing of downstream templates. We're testing the use of a template to track security best practices. If we can't refresh the templates from the master, none of the older clients will have the new checklist items. There will be no way to reconcile and go back to determine who needs attention. With auditing in place as it is, the risk should be pretty low. If the checklist item changes, ask if you want the change propagated and if so, store the original item name in the audit trail. Without this, we need an option to modify the company assets and create instances of related metadata fields in those records to track these items.
Aquamarine Butter
•
Sep 27, 2023
I think this could be handled quite easily with an option to add a Process as a linked process or a free process when it's created at the company/client level. You could also default to linked, and have the linked property change if the process is edited at the client level.
Also a way to view which clients have cloned a global process template, and which are linked vs free would be a huge help in managing and updating processes.
Purple Blueberry
•
Apr 26, 2023
We have global processes that change frequently, and when we do that, we have to remove the process template from a slough of clients make changes to the Global process, then re-add the template. Dynamic updates to Global processes down to client templates is needed!!
Bronze Narwhal
•
Oct 18, 2023
I get this - We Have a few Global Process Templates that are the same for every Client. We need to make a change to the Global Process so that all the individual Client Processes reflect the change. Even If there was a way to Link a Global Process to an asset like a user Directly without having to assign the process to the Client first would help.
Log in to comment and vote
Comments19
Purple Cookie
Apr 22, 2020
Maybe any that haven't been customized should automatically update and any that have been customized shouldn't, but you should have the option
Amethyst Bagel
Nov 26, 2020
The way to do this would be to create a relationship with tasks between the global and client templates.
In the event a task was modified on a client level it would break the relationship; when modified on the global level it'll update everywhere else as well. When the process itself was modified (structure changed or tasks added/removed) it'll update on all linked processes.
Yellow Nucleon
Jul 5, 2023
Just had this similar thought. We have a use case where you have to go to another location to look up a credential in another system. It would be great if we could create the global KB item and then allow it to be visible on the client level in an updated manner.
Also, the ability to select if it should be part of an export or not for that client.
Azure Mustard
Sep 29
•Merged request
Keep company processes in sync with global process templates
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.
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.
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.
Lime Sunbeam
Apr 13, 2022
We Agree, this is super important to keep processes upto date.
Bronze Mist
Aug 28, 2023
We need a way to keep the child processes up-to-date.
Harlequin Zipper
Dec 23, 2021
I think it's critical to allow the refreshing of downstream templates. We're testing the use of a template to track security best practices. If we can't refresh the templates from the master, none of the older clients will have the new checklist items. There will be no way to reconcile and go back to determine who needs attention. With auditing in place as it is, the risk should be pretty low. If the checklist item changes, ask if you want the change propagated and if so, store the original item name in the audit trail. Without this, we need an option to modify the company assets and create instances of related metadata fields in those records to track these items.
Aquamarine Butter
Sep 27, 2023
I think this could be handled quite easily with an option to add a Process as a linked process or a free process when it's created at the company/client level. You could also default to linked, and have the linked property change if the process is edited at the client level.
Also a way to view which clients have cloned a global process template, and which are linked vs free would be a huge help in managing and updating processes.
Purple Blueberry
Apr 26, 2023
We have global processes that change frequently, and when we do that, we have to remove the process template from a slough of clients make changes to the Global process, then re-add the template. Dynamic updates to Global processes down to client templates is needed!!
Bronze Narwhal
Oct 18, 2023
I get this - We Have a few Global Process Templates that are the same for every Client. We need to make a change to the Global Process so that all the individual Client Processes reflect the change. Even If there was a way to Link a Global Process to an asset like a user Directly without having to assign the process to the Client first would help.