4- Once we passed the limit to request changes the Template will go live in the Next Release. 3- We will accept simple changes until 7 days before the first INT deploy. 2-The issues that we found testing it and the estimation related to them. The Site Collections are aligned - The user doesn't modify the Template meanwhile the support team is working on it - If the changes are planed with time Missing Features Issues Estimation: Duplicated Columns Hidden Features 1-The complex of the data inside the Space and its estimation. 6- Also we should contemplate the current release dates to provide the user the go live Date Save Templates with Content Some Issues are: New Process: 1- URLs that are inherited Some items to take in care to know in which Release the Template will go live: Templates Creation Process Columns Duplicated that couldn't be removed Current Process: Advantages and Disadvantages Features that couldn't be enable Content Type Duplicated that couldn't be removed 1- The user creates a New Space 2- During some time it's modified according to the project needs 3- As the space results useful for a whole company or area the user decides to ask for saving it as Template 4-The Collaborate Team takes care of this process, but during it we usually face some issues Duplicated Content Type This Process will be easier if.
Transcript: 1- The user creates a New Space 2- During some time it's modified according to the project needs 3- As the space results useful for a whole company or area the user decides to ask for saving it as Template 4-The Collaborate Team takes care of this process 5- The new process covers the Analysis of the Space that we should save as Template and the Estimation to finish it.
0 kommentar(er)
