How it Works
|One simple process of safe document versioning consists of these three steps: |
1) Assume you have a working document generation system. There is a "test case" made up of a complete set of input **) constituting one "version". Let's call this the "reference" version and consider it correct.
2) Apply a certain change to the generation process *), thereby producing a "new" version. Now the trouble starts. High volume commercial document production can be complex and mistakes happen. And mistakes in big runs cost big money. Unfortunately there is no way to manually check 1000s and 100.000s of pages - what you usually do is look where you most expect problems, check as many as you can and hope for the best.
3) Enter Aly: 1. Run the test case with your "reference" version, producing spool one. 2. Run the test case with your "new" version, producing spool two. 3. Let Aly proof these two spools against each other to turn your hope into certainty.
With these three steps we can safely move from one version to the next well guarded against unforeseen traps: New machines, new versions of 3rd party software and ever-changing document requirements will always arrive, but... Aly will let you sleep well all the while.
*) A non exhaustive list of factors that introduce change: New release of the formatter (or database, application program, middleware, resource library,...), new printers or servers, the OS level, changed formatting instructions, merger of your company, new client-side processes, legal requirements, new postprocessors ... and many, others!
**) A version or state of the document generating system can consist of a lot of steps relating to the many stages of data- and document preparation. This may include data, print resources, programs and definitions, depending on your setup.