Now the next time you want to create a Process based on your own template, just start from there. And the Name and Description will be the Default Project Name and Default Project Description that you have set initially when you created the template.
The same built-in templates will still exist and cannot be removed, but your custom ones can.
Tell us what you think, how would you improve this and how do you plan to use this feature. I’ll break the ice by saying that i would like to be able to share these templates with my colleagues in the future. There, i’ve said it! What else?
What would you think of having a similar feature (or even modifying this one) to create Template based only in one workflow?
You could later the “New” Button to create a file based on this template, the same way you are doing it for Sequences, Flowchart etc…
It is typical to use automation templates to build our workflow (ex: Components, process) and it would have an even bigger impact than the current feature, used only once, during the project creation.
You could expose two types of templates creation:
Workflow templates
Project Templates
A Workflow template would be used quite many times during the project.
any way to change that path via a setting?
I want to “deploy” the template to multiple machines where studio is installed and use a shared folder as a source for the template.
my studio version is 2018.3.2 and I tried to copy a project as a template in the ProjectTemplate but unfortunately, the copied template is not show up in the studio. how to fix it?
You should see the “export as template button”, but also another way is the new project type, instead of starting from Blank Task or REFramework, you start a template, check “creating a template” documentation: Project Templates
It looks great as usual. Thank you so much for sharing. I would like to make a new template for one of my website I created a few weeks ago. Can you please help me here?