3.4. Logo management

3.4. Logo management

Document templates included with the DynamicTemplate solution may use logo management. Logo management allows the appropriate logo to be inserted into the document template based on the user’s area (e.g. department, business unit or seniority etc.). 

Any invalid characters in derived values are ignored when deriving the relevant files, such as '<', '>', '\', '/', '|' or '*'. 

Logos that will be used by DynamicTemplate must be stored in the resources system folder (section 3.1.4. Resources ). An area specific set of subfolders must be created for each department in the organisation. Logos will be found as described below: 

First the logo is searched for at: [ResourcePath]\[ResourceTagPath], where ResourcePath and ResourceTagPath are read from Setup.xml. 

If no logo is found, the search is repeated at: [ResourcePath]

3.4.1. Example of finding a logo

Using the paths defined in the example in Figure 105, ResourcePath from Setup.xml has the following value:

W:\DynamicTemplate\Resources\ 

This path must be combined with the ResourceTagPath , which, in the example in Figure 109, are defined as ’Company’ and ’Department’. These are ’tag’ names from the ActiveDirectoryDefinitions.xml file, and will be represented in the templates’ dialog boxes as text entry fields named ’Company’ and ’Department’. 

So, the user’s entry (or the automatically completed data) will become the actual values that will complete the file path to the desired logo folder. 

For example, an entry of ‘Dania Software’ in the ’Company’ field and ’Development’ in the ’Department’ field would give a complete file path of:

W:\DynamicTemplate\Resources\Dania Software\Development

3.4.2. Rules for logo search

Searches will follow the rule set below:

1. The first logo found that matches the formats listed in section 3.1.4. Resources will be used.
2. The area specific logo folder will be searched first, e.g., W:\dynamictemplate\Resources\dania software\Development.
3. If no logo is found in the area specific folder, the search will be repeated one level higher. Taking the path above as a starting point, the next path to be searched would be: W:\dynamictemplate\Resources\dania software (which is still an area specific folder).
4. If no logo is found, the search will continue to move up through the folder levels until it reaches the root resources folder (i.e., the path given in ResourcePath, described in section 3.1.4. Resources). A standard logo must exist in the root resources folder.
5. If an area specific folder is not found, the search will begin one level up in the folder hierarchy.
6. Any invalid characters in derived values will be ignored when the relevant files are derived, e.g.’<’, ’>’ or ’*’.

Logos are inserted with their dimensions preserved, i.e., they are not scaled to fit the templates before being inserted.