Document Templates
Each application context, on the display page of a particular element, has its own ID code as a search key in the database. Whenever the merging of a template with a page is requested, the first thing considered is this key for retrieving all other data. For this reason, each template has a "preferred path" given by the first context that was inserted into the template. If the template has, as its first field, the customer's company name, every time it is used on the contacts page, the merge is done directly with the current customer. If, for example, the template has the product as the main element, it is shown in a list that allows selection because there are no keys on the customer page to search for the product in the database.
Therefore, it is important to:
- Do not remove the tags unless accompanied by their relevant data, including the opening and closing tags.
If contexts not linked to the main one are necessary (e.g., if we insert the operator into the template defined for contacts, a selection will be requested from a list because it has no links to the customer).
Contexts not directly linked to the main one, which need to be selected from a list, must be placed OUTSIDE the closing tag of the main context.
In other words, following the scheme below:
The operator name will not be requested at merge time because the system does not know who to associate the information with. The correct arrangement of the fields is as follows