Concur best practices for making changes to existing expense audit rules for client team?
For client who has attended Expense Advanced Configuration Training, what is Concur suggestion for companies who like to ensure subsequent changes (e.g audit rules) are made without impacting existing production setup? Should the client subscribe to a permanet or long term test entity?
Re: Concur best practices for making changes to existing expense audit rules for client team?
We have a implementation environment that is basically a copy of our production environment. Any changes we make are first made in the implementation environment, tested and validated, then we make the changes in our production environment. I believe there is an additional cost to having a implementation environment available at all times. I'm not sure if they would be able to temporarily spin up a testing environment to validate some changes.