At IDT our template system is set up to start with a master template and then snap various template fragments in as needed. Often these template fragments represent a design block, and the semiconductor industry referred to as IP blocks. These template fragments have 4 to 5 tasks and are the same for each IP block. Specifically those tasks might be
generate design schematics
hold design review
layout block
hold final block review
post block review action item cleanup
As each of these tasks has the same name in each block it is necessary to add the name of the block to the beginning of the task so that when the task shows up in the my work interface the user knows which task they are supposed to be working on. We currently manage this by a somewhat clumsy script that accesses the block through the API and renames all the subtasks based on the name of the parent task.
A far better solution would be if a template builder existed. I envision a system that allows you to build up a project in a simplified view where template segments can be snapped together and variables used to name the tasks within those segments. For example, a template segment could be developed where the tasks had a naming structure like this:
{blockName} - Generate Design Schematics
Inside the template builder, you would simply enter the name for each block and all the subtasks would be renamed as such:
Charge Pump - Generate Design Schematics
A simplified template builder view would also have the advantage of making it far easier to snap pieces of template together without the current somewhat time-consuming process of repetitively using the attached template button from within the project.
