Ability to push a template across "Projects" or Environments

Related products: InField

As a Learning Facilitator or template creator, I would like the ability to create a template in a sandbox environment or “project” (example, the celanese-dtr environment), and then be able to push my changes to the production environment (celanese) when I have verified that the naming convention and items follow my organization’s standards. This would allow me to control what my process experts see before the template is ready to be shared, but also prevent mistaken synthetic tags to be created in CDF and junk it up with a tag that was created by accident. Today, if I mistakenly forget to add a character like a number or letter and save the template item, then it is still permanently written into CDF PROD. 

CC: @ibrahim.alsyed @rsiddha 


Trying to understand if this request is different from the one mentioned below or can we merge/track a single one. 

 


@rsiddha  - yes, they are the same, except I think at the end where it says “SAP” @Benjamin A Onweni meant to say “CDF”.


FYI @Kristoffer Knudsen :) 


Hi @rsiddha & @Benjamin A Onweni - thanks for the feedback. 

Having an improved process around creating/editing Templates before pushing the changes to production (ready to be executed on) I very much agree with. We are trying to mitigate some of these challenges now, e.g. what you mention on synthetic tags. I don’t think we’ll solve this with separate environments, but rather with something like a “template lifecycle status”, e.g. draft → production. Will update you when we have more on this. 

 

Yes, agree that we can merge these two - @Anita Hæhre, could you do that? 


Updated idea statusNewGathering Interest
Idea merged into:

All the votes from this idea have been transferred.