Own templates

What you built in one tenant, you can file as a template yourself — to add it again to the same tenant or to carry it to other installations. Typical case: a company with several TrakState installations that builds its templates once and rolls them out everywhere. Everything lives under Settings › Templates › Own.

File as template

File as template opens a selection of your tenant’s objects: menu folders, boards, record types, tags, scripts, roles.

• What a chosen part needs comes along automatically — for example the list behind a field or the right for a menu entry. Each shows “automatic: …”.
• What another template you added created, such as its list, is not copied but becomes a dependency on that template. The selection says so on the row at once; ticked, it is copied after all.
• What lies outside the selection becomes an option (“Ask when adding”), or you take it along.
• A common prefix is recognised as the namespace and replaced in the template, also in script source. What cannot be rewritten appears under Please check. What prevents saving is listed under Cannot be saved yet — for example a field name containing a dot.
• You give a name, version and description. If you pick an existing own template under New version of, TrakState suggests the version number from the difference; if something is dropped, the major version rises.

Save as own template files it under Own. There you add it like any other — with namespace, options and origin (see Templates and the store).

Handing it on as a file

Download as file produces a .tstpl file. It is not signed; the publisher inside is your company name.

Import from file

On the other installation choose Import from file and the .tstpl. Before importing, TrakState shows what the file holds:

• Not signed, from file — and the publisher as a mere statement in the file.
• All scripts the template brings, with their count. Read them before you confirm Import.
• Whether the file is already known: newer, the same or older than the one here.

Only a tenant administrator may import unsigned files. A template may do nothing you could not do by hand yourself.

Afterwards it sits under Own (source File). A newer file with the same id counts as a new version: under Installed, Check update then appears for every installation, with the same reconciliation as any update (see Updating and removing).

For the public catalogue the operator takes over an own template; that is not part of this page.