This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
I think you'll need to invent your own methods using this highly malleable tool.
It is very easy to transpose for compare.
Lacking global variables, it isn't so easy to port from one environment phase to another
I generally do a prod parallel to different output then compare to prod.
You might build input data of test cases to run.
Gallery supports versioning but private studios lack the controlled stability of production so we use yxmd files.
There's very much a heretical freestyle to it compared to tools rooted in IT dogma that is reflected in the names (private studio, artisans, gallery) which you'll encumber by forcing into a rigid project protocol. Definitely more craftsman and artist oriented than engineering oriented. We are having some success with letting uses evolve from single-user, to user team, to inter-department, to enterprise. Rules get tighter as use progresses. Protective and preventative measures are most often added after errors occur.
As per your expertise, is there a way to automate fetching the latest version from say a versioning tool like BitBucket. So that before every run it picks up the latest version from the version control tool rather than manually importing the packaged workbook into the designer before each run.