We have a new template to share 
This one is designed to show you how to auto-generate entities based on standard ‘template’ entities.
It demonstrates an example of how to ensure that a Project always starts with a default set of Tasks,
but the principles can be generalised to many other scenarios.
Let us know what you think of it, and feel free to share any use cases you have, so that other people can learn from your great ideas 
Thanks for this – it’s a very useful demo 
.
This is really great. Using the Smart Folders achieves something I was trying to achieve using list view and self referencing tasks in a much clearer and more elegant way
hey @Chr1sG I’m about to set up a template for one of our own repeating projects, but it will only ever have one format which is 1 Course > 4 Units per course > 5 Lessons per unit. Also 10 Tasks Per course:
Do you think it would be overkill to try to adapt this template for this (since this template deals with multiple scenarios while I only need one)?
If you’re absolutely certain that things won’t change in the future, you could just use basic automations to set up your projects, i.e. an automation that runs when a course is created that has 4 actions, each one creating a new unit, and then an automation that runs when a unit is created that has 5 actions, each one creating a new lesson, plus an automation for creating the tasks for each course…
This will probably take you less time than setting up a more generic solution, so the only reason to use the generic version is if there’s a chance that things might change in the future.
Thanks Chris - that’s what I’ve gone for. The structure is certainly not likely to change any time soon!
@Chr1sG sorry to revive this topic
As I understand it, the current template basically adds new tasks when new Projects are created and linked to Categories through a lookup field in the task template. This works great if you want to automatically add the tasks to all newly created projects.
However, I am wondering how I might be able to add the tasks from the template to existing Projects (or selectively apply/add tasks) through a button (i.e. something like “Add Common Tasks”).
Since fibery doesn’t have a “For Each” action in the UI, I am wondering if a script the only way to accomplish this?
Actually, the automations in the template will run any time a Project is linked to a Category. So if a Project is created in a given Category, then the automation will run, but also, if a Project is created without a defined Category, when you do choose the Category for the Project, the automation will run.
Also, if you change the Category, the automation will run, so if there are Task templates in the new Category that weren’t in the old one, you will get new Tasks for these items.
That makes sense. The only challenge is that I already have all the categories assigned. It wouldn’t be too hard to do it again but I am also thinking it would be helpful (in my particular case) to add the tasks selectively so that is why I was hoping to use a button action.
I’m not sure I get the case here. A Project is already linked to a Category, but you want to unlink/re-link so that the automation will run again? Does the Project not already have the appropriate Tasks required for that Category?
Apologies for not providing the context. Our use case is that we recently had the idea of adding milestones (as entities) to projects. The milestones are based on the Project Type which is already assigned to the existing Projects. That is why we were thinking a button action is more appropriate. We are also wanting to try this out on a few projects before making it standard so thought it might be more helpful to add it selectively for now before making it automatic for all new projects.
Here’s what you could do:
Create a many:many relation between Projects and Task Templates
Duplicate the existing automation in the Task Template db, but with trigger on a new linked Project (for this field you just created):
Create a button automation in the Project db that links it to the Task Templates for its Category:
Thanks again for this solution. This is a very interesting approach. I ended up going the script route because I ended up with a few more requirements. Using graphQL api made it less painful than before 
