Ability to move from Sandbox to Production

This would be a great feature!

But - great power comes great responsibilities

I could see this being a nightmare for large instances unless there was someway to "stop services" at the Admin level as to not over-write production data (unless that is part of the intent)

Honestly working in production with the needed team/group safeguards is typically enough to test/rollout.

BUT options are good.

Surprised, and bummed, to find out this is not already a standard feature. We need the ability to test new forms/worklows/functionality in Sandbox and then once approved, push live in our Production instance. Seems odd that the system forces us to try and remember everything that we did and have duplicate our efforts! How soon can we get this on the roadmap??

This would be a great help as most of our forms/reports etc originate in the Sandbox and it is a very manual process of recreating in the PROD environment once testing is complete

Why would you move from Sandbox and not "Preview"?

Noting that this is idea is Not Planned, I invite you to consider our Packages solution, which enables you to efficiently select a set of related Workfront objects and/or data from one environment, save them, and then deploy them to another environment.

https://store.atappstore.com/product/packages/

Regards,

Doug

I fail to understand what the point of a sandbox is without the ability to move to production.

Would like the ability to modify and preview custom form changes in the Preview environment, and then be able to push them to Production once validated. Currently, it requires having to do the work twice. Thank you!

I agree with Rudy. Double work is bad enough but leaving room for oversights and errors is another... which then requires a second round of validation and testing after rebuilding in production.

I agree with Rudy. Double work is bad enough but leaving room for oversights and errors is another... which then requires a second round of validation and testing after rebuilding in production.

I agree with Rudy. Double work is bad enough but leaving room for oversights and errors is another... which then requires a second round of validation and testing after rebuilding in production.