Having a Sandbox, for development and testing new Workspaces and updates on existing workspaces, is a great benefit. It reduces errors in the productive system during testing. If it is not working, you can delete it or leave it. Go to the next solution and test it until it fits perfect.
However, there is one big concern.
All changes in prod. System must be implemented twice. Once in Sandbox and then, the second time, if it goes live.
You must transfer all changes manually.
This is a possible source of errors. If something is missing, the behaviour in prod. System is not as it should be.
Then you have to go and check, where is the problem. All changes must me checked manually.
A transfer, of a list with all changes from a specific change or from a workspace with all related changes would be helpful. It reduces manual tasks and documentation.
Also, a tool to transfer the current state from prod. System to Sandbox would help. Push and update only one Workspace on demand as Admin User, before a change start, would reduce conflicts. There are less gaps between prod. System and Sandbox. The solution is more robust.
I would like to have a tool that could:
- Make a comparison between Sandbox and prod. System</li>
- Ability to push actual state from a Workspace to Sandbox</li>
- Ability to push changes from Sandbox to Workspace to prod. System</li>
- Create all related scripts as a .js file from the Workspace for documentation and safe local for history
This would increase the security of customizations and make the developer's work easier.
I hope many others agree.
