Dear Workfront, the most logical thing to do is build and test in the Sandbox and then select the objects you need moved to Prod. This is an urgent need so I hope it makes it way to the top of the list.
Dear Workfront, the most logical thing to do is build and test in the Sandbox and then select the objects you need moved to Prod. This is an urgent need so I hope it makes it way to the top of the list.
Dear Workfront, the most logical thing to do is build and test in the Sandbox and then select the objects you need moved to Prod. This is an urgent need so I hope it makes it way to the top of the list.
I'd like to inform that we've started a product research to look into the possibility of allowing data and configuration transfer from Sandbox to Production. Any feedback on this topic will be extremely helpful for us to understand all the use cases and provide the best possible solution. If you're interested in sharing your experience with us, please book a feedback call from this page.
It would be extremely helpful to configure, build, and validate in Sandbox and then when approved, promote the changes to the Production instance via automation. Not only it is a timesaver but greatly reduces the negative impacts of possible human error in the rebuild and helps satisfy internal and external examinations from an audit tracking perspective.
We've been utilizing Workfront for some time and are now ready to mature our use of and leverage the automation capabilities of the tool for our enterprise change management process flow - which probably means a complete new build of processes, forms, templates, etc. This type of functionality would be extremely helpful for this type of scenario. I'm sure as we mature in our knowledge of Workfront we'll find many more.
It would be extremely helpful to configure, build, and validate in Sandbox and then when approved, promote the changes to the Production instance via automation. Not only it is a timesaver but greatly reduces the negative impacts of possible human error in the rebuild and helps satisfy internal and external examinations from an audit tracking perspective.
We've been utilizing Workfront for some time and are now ready to mature our use of and leverage the automation capabilities of the tool for our enterprise change management process flow - which probably means a complete new build of processes, forms, templates, etc. This type of functionality would be extremely helpful for this type of scenario. I'm sure as we mature in our knowledge of Workfront we'll find many more.
It would be extremely helpful to configure, build, and validate in Sandbox and then when approved, promote the changes to the Production instance via automation. Not only it is a timesaver but greatly reduces the negative impacts of possible human error in the rebuild and helps satisfy internal and external examinations from an audit tracking perspective.
We've been utilizing Workfront for some time and are now ready to mature our use of and leverage the automation capabilities of the tool for our enterprise change management process flow - which probably means a complete new build of processes, forms, templates, etc. This type of functionality would be extremely helpful for this type of scenario. I'm sure as we mature in our knowledge of Workfront we'll find many more.
The ability to select which configuration to move from Sandbox to Production (not just all or nothing), would be ideal.
Example:
Select a subset of Templates, Custom Forms, Teams & Groups, Project/Task/Issue Custom Statuses. Automated refresh of configuration for selected subset from Sandbox to Production.
Thank you for reviewing and evaluating this idea Workfront! it would be a great addition to the native application and be a huge time saver for admins!
This is still a huge need! Especially when you need to make changes to forms and reports/dashboards that are already live in the production system. The Sandbox environments are functionally useless without the ability to publish things to production.
