Your business never stops changing, which means your planning model doesn’t, either. Whether you’re managing changing territories for sales teams, introducing new product lines into your supply chain operations, or building a new entity into your budgeting process, it’s crucial that the entire business has confidence in the changes being made in Pigment.
This confidence is precisely what Test & Deploy is designed to offer.
When you manage Applications with Test & Deploy, you create a Development workspace where you can experiment with changes to your model without affecting day to day activities in Production (your main workspace) - giving you confidence that you’re making the most effective adjustments. When you’re happy with your changes, you can deploy them to your Production environment at a time that suits you - ensuring your business stays running smoothly.
.gif)
How does Test & Deploy work?
When you have Test & Deploy enabled, additional workspaces are created alongside your existing Production workspace. These are typically referred to as DEV and TEST. Using two additional workspaces means you can work more efficiently with a subset of your data in the Development workspace, and by distinguishing between production and non-production activities enables separation of duties and access to production data only where it is necessary.
Completed structural changes may then be deployed to the Test workspace, where you can test the effects of these changes in a workspace containing sanitised test data for complete confidence that your calculations are still operating as expected.
When you have completed testing, you can view a summary of the changes that will be made and deploy these changes directly to your Production workspace for them to take effect for your users at a time that’s convenient for you, ensuring no interruptions to day to day operations.
You can also see a record of deployments and the number of changes made within affected Applications in Pigment for your records.
{{BLOG-POST-BANNER}}
What’s included in Test & Deploy?
Changes in scope for Test & Deploy include anything that impacts your model structure; for example Application settings, Block structures or formulas. You can choose whether to include data in Dimension lists for greater flexibility.
Note that user access permissions and data integrations are not replicated in DEV or TEST workspaces; these remain independent so you can customise your workspaces inline with the requirements of your business.
When would I use Test & Deploy?
Once Test & Deploy is enabled for an Application and this Application is ‘managed’ by the Test & Deploy process, any structural changes to the Application need to be made in Development and deployed through the Test & Deploy process before they can take effect in the Production workspace.
Examples of changes that benefit from being managed through Test & Deploy include:
- Adding new financial periods to your model in preparation for a new financial year
- Amending a formula to calculate more efficiently, or to improve readability
Where can I find more information?
Full documentation for how to use Test & Deploy can be found in the Knowledge Base here.
Test & Deploy is available for customers on the Enterprise plan: please contact your Customer Success Manager for more information.
