Currently, any changes developed within the Pimberly sandbox, such as updates to workflows, decision tables, or rules, must be manually recreated in the live environment. This duplication introduces unnecessary risk and inefficiency, as it relies on system owners to precisely replicate configurations or design/test the solution in the live system, running the risk of fault. Without a structured handover process, this can lead to inconsistencies, missed logic, and potential disruption to live operations.
To improve this, it would be highly beneficial if Pimberly introduced a built-in deployment mechanism that allows system owners to design, test, and document changes entirely within sandbox. A dedicated section could track configuration changes, enable UAT and internal sign-off, and allow approved changes to be safely pushed to the live environment, ideally with rollback options for config states (excluding product data). This would greatly reduce manual effort, improve governance, and lower the risk of production issues from configuration errors.
Comments
Please sign in to leave a comment.
Agree. I think that from Pimberly's perspective they may want to mitigate any risk for their customers. I would have to think this could be done rather easily. Then simply build in a confirm/cancel message box stating the user understands any possible risks when migrating. And to your point, have a quick way to revert to the last version of whatever it is. One revision to fall back on I think would be a good compromise and allow customers to have a quick fallback for any "Oh, Shi*" moments!
I agree!!