Creating a NEW Transaction, Subledger, or Global
Template by making a Copy
Sometimes additional template requirements call for a field content that includes substantially all the fields already used in another template plus, possibly, a few new ones. In such an event, copy the existing template:
When using the Save As... or Save To... option with a Transactions template, you are creating a new Extra table with the name based on the Save As... or Save To... operation, containing all the same fields as those contained in the Transaction template from which it was copied. Be sure to stipulate the Triggers, in the Inspector, for the copied template.
Before deciding whether to create a new Transaction Template as a copy as opposed to the cloning process, consider your reporting requirements.
you have a "Revenue" template and one of the Extra fields is the "Product Code".
The "Revenue" template is triggered upon the Amount field becoming negative and the GL Account fitting into a specific range. You wish to track "reasons for revenue reversals". Here are your options.
The cloning option is usually preferred, if the Product Code is to be retrieved in a report. With the clone option the Product code is stored only in the "Revenue Extra table"; however, with a Copied Template, Product Codes with positive Amounts are stored in the "RevAdj Extra table" and Product Codes with negative Amounts are stored in the "Revenue Extra table", making the retrieval unnecessarily cumbersome.
When using the Save As... or Save To... option with a Subledgers or Global template, you are creating a new table with the name based on the Save As... or Save To... operation, containing all the same fields as those contained in the original template from which it was copied. However, after modifications are made, including additions of new fields and deletion of old (copied) fields, and the template is again saved, the new database table will be modified to fit the new design.
If the originating Template had one or more Procedures attached to it, these Procedures will be copied automatically as part of the Save As ... or Save To ... processes. After the Workspace is modified some of its Procedures may become invalidated (the "checkmarks" in the Open Procedure window will be "broken") and will have to be revisited.
Cloning a Transaction, Subledger, or Global Template
Templates, together with their Procedures, if any, can be thought of as input devices which capture data and direct them to the applicable database table(s). Every template designed using the "New/Save", "Save As", or Save To options creates, during the Save process, the underlying database table associated therewith.
The exception to this rule is every template created as a Clone of an existing template. Cloned templates, when saved, do not create any database table; rather, they are targeted as acceptable input devices to the database table(s) associated with the original template from which the clone was produced. The cloned version of templates and their origins are easily identified in the Open Template window:
The purpose of the Clone feature is to have the ability to create multiple input devices, possibly with different Procedures, feeding data into the same database table. Whether or not to have cloned templates is up to the Configurator and the internal user-group. A couple of reasons could be:
Table of Contents
Global Template - Topics of Interes
Subledger Template - Topics of Interest
Transaction Template - Topics of Interest