Updating and removing
An added template stays tied to its installation. Under Settings › Templates › Installed you update, edit and remove it. Everything here runs only when you trigger it: there is no automatic update. Before every step TrakState takes a restore point (see Backup & restore).
Update
Section titled “Update”If a newer version exists, the row shows Update available. Check update opens the plan, which compares three states: the inserted version, your state today and the new version. For each object:
| You | New version | Result |
|---|---|---|
| unchanged | unchanged | nothing |
| unchanged | changed | is updated |
| changed | unchanged | your version stays |
| changed | changed | conflict — you choose |
| — | new | is added |
| unchanged | dropped | is removed; a record type with data stays and loses its badge |
| changed | dropped | stays and belongs to you |
| deleted by you | any | is not created again |
Only a real conflict asks for a decision: Keep my version (default) or Take the new version. The latter discards your change; it is kept in the restore point. If the new version drops a field whose column holds data, you must confirm the removal together with the row count. If a field type changes incompatibly, the update is blocked, with an explanation. The Class column states this per row: harmless, checked, destructive or blocked.
Boards are reconciled per widget. Say you changed widget B on the board and added a widget D, and the new version changes widget C and brings a widget E. After the update: A stays, B stays in your version, C is brought to the new version, D stays (it is yours), E is added at the first free spot. The board’s row unfolds for this. Only if both sides changed the same widget do you choose — and then only for that widget.
New options of the new version are asked in the plan; existing values stay. For a package the parts are updated one by one, in a single plan. Afterwards the new version is the baseline: what you changed still shows as changed. A paid template only updates if the new version is covered by your purchase (see Buying and unlocking).
If a new package version brings no newer part — only a new description, new pictures or a change note — the plan says so. The update then takes over only the package version and its texts; it needs no restore point. Until the list has been read again, a row just updated shows being updated.
Editing an installation
Section titled “Editing an installation”Edit changes the options of an installation, such as the shift model or a target value. It is an update to the same version with different values and follows the same rules. Namespace and menu place cannot be changed this way.
Removing
Section titled “Removing”Remove first shows a plan:
- Will be removed (unchanged): tags, scripts, roles, boards and menu entries you did not touch.
- Changed by you: per object you choose Keep, then it belongs to you (default) or Remove anyway.
- Used by your own objects: a tag that one of your own boards or scripts reads stays; the plan names who needs it.
- Not touched: objects you only linked while adding, and your own.
- Recorded data: the plan names every record type with its number of rows. The default is Keep data: the record types stay with all rows and are yours afterwards. Delete data downloads a CSV first, and to confirm you type the namespace.
For a package the plan names every part that goes with it. A part you had added on its own before the package took it over is marked; Detach and keep makes it stand on its own again, and it stays.
If another template depends on this one, removal is blocked until that one is removed; the dialog names it. Installed plugins and a purchase stay: the template can be added again at any time. Thanks to the restore point even a wrong removal can be undone.