Do you implement Change Control?

Thank you for the article and for the promotion of safe development practices.

As someone just becoming a OneStream administrator, please let me ask some questions to better understand. And tell me if these questions don't even make sense for OneStream.

I'm used to working with systems in a Dev / Test / Production setup for larger system changes. But I've also been involved with PowerBI and Access and Excel where it's easy to make an update to a report, test it, make a backup of what I'm about to change in Production, copy the new item to Production, and return to the backup report if someone discovers a problem in production.

• If I want to make a change to a report in OneStream, can I make the change in Dev/Test, then copy the new or updated object, and then paste that object into the Production instance? Or do I have to make the change in Dev/Test and then re-do the change in Production? And do you usually make a backup copy of the item that you're changing before pasting the new version in production and have those artifacts sitting around, no longer used?
• In other words, let's say that I'm asked to change a report to display some subaccounts for a total. What is the best practice to make the change, test it, and move it to production?
• And what if it's a change that has a broader effect, like adding a location or a new product that affects several reports and security profiles. What's the best practice to test the change and then move the change to production?