Upload template and all referenced templates from the Publishing Client to Document Builder

As part of the review process, we strive to be transparent about our intentions with each enhancement suggestion. The IBM Engineering team has carefully reviewed this idea, and based on our understanding, it does not fit our near-term plans. Although we are closing this request, it will be kept in IBM's ideas repository.  We value your feedback and thank you for allowing us to partner with you in developing our products.

Thank you for your feedback but it seems my previous comment was not clear enough. Let me provide more details.

PUB Studio's primary and secondary template relationship is different compared to the PUB DB report with its templates. In PUB DB, you need to create a report with primary and secondary templates. Once this is completed, you have references set, and no need to modify them going forward. After this, when there are updates to one or more templates, you can push updates to each template from PUB Studio to the PUB DB. Templates in PUB DB will be updated and the PUB DB report will be dynamically updated to include the latest template. There is no need to update the report and template references. 
In summary, you do need to create an initial report and set up a template structure but after this, you can update each template individually from PUB Studio when there are template changes.

I hope this clarifies the process today. In the future, we plan to add template versioning and probably we will need to add a flag if the PUB DB report should take the latest template version of the one specified in a report.

Hi thank you for feedback. Having versioned templates does make this a little more complicated however the time we lose doing development on our local machine and getting the approx 21 sub templates manually uploaded and then updating all the references on parent template and then uploading the parent template is incredibly time consuming and PUB Client often has errors re-adding the templates which means we need to remove and re-add them to get it to work.

One of our key issues is we need to deploy our parent and 21 child templates on 4 different servers. The files themselves are all CM controlled (outside of the Pub Server) and the development occurs locally. Is it feasible that if local development of the templates uses dynamic referencing of children that when the parent template is uploaded there is an option to

a) all the dynamically linked children are actually embedded physically in the one template of the server? This would have a massive running performance increase (as the child templates don't need to load each time) and still allow us to do development on small sub templates and deploy to the server for a production environment.

b) upload all children and tag a version against it and auto link it back to parent. (this would be ideal) We run different versions of the template in parallel. eg we support Build 2 of publishing templates at the same time as build 3 and Build 4 for example so they each are their own base object and not incremental version of each other.. The server version control will be great for bug fixes on main deployment so looking forward to that.

Happy to explore these options further and hope what I have written makes sense.

Thank you for submitting idea. IBM Engineering Publishing team review board evaluated this request and determined it will need additional feedback to evaluate this request.

Currently, PUB Studio allows updating individual PUB DB templates. In order to use PUB templates with PUB DB, user needs to create report specifying which templates to include, replicating primary/secondary templates relationship established for PUB Studio. If this process would change, then when uploading updated primary template, reference templates would be uploaded too even they might have not changed. Therefore, this is not desired, nor valuable. In addition, we plan to provide PUB DB asset versioning in the future and if non-changed templates would update its version, this could lead to the misleading behaviour. Therefore, PUB team feels the current implementation is sufficient and we would like to hear your feedback before making decision on this idea.