Background information
Project archive serves the purpose of storing projects on a central server, by means of which it is possible to:
- ... share it and work on it with other ETS users (not simultaneously).
- ... backup a project.
If a project is accessed by a ETS user then
- a local copy will be made
- on the server it will be locked for any other user
The location for the project archive is defined by the 'Project Archive' setting.
The default location for the project archive is the C:\Users\Public\Documents\KNX\Archive.
How to use it
For the initial use of the archive, select a project from the local project list and from the context menu click the 'Send to -> Archive'
The status line of a project in the project archive displays the following information:
| Option | Description |
|---|---|
| Name | Name of the project in the project archive (identical to the local project name) |
| Status | Status of the project with respect to editing/action in the project archive (unknown, checked in, ...) |
| User | User who last edited the project (Windows user) |
| Workstation | Workstation on which the project was edited (computer name) |
| Date | Date of the last editing/action, e.g. when the project was added to the project archive for the first time or when it was most recently checked in. |
Update  |
Updates manually the content of project archive. |
The archive functions are available via the context menu of the selected project from the 'Projects' and/or 'Archive' list:
| Option | Description |
|---|---|
| Add to Archive |
ETS adds the selected project from the local project store to the project archive. Actions in the background
|
| Delete from Archive | Deletes the project from the project archive (only if the project is checked in). |
| Check-Out |
ETS gets the project from the server and locks it for other users. Actions in the background
|
| Undo Check-Out |
The currently checked-out user releases the project back for other users. Actions in the background
|
| Force Undo Check-Out | The project is currently checked-out by another user, but will be released for other users anyway, use this with care because work of the currently checked-out user will be lost. |
| Check-In |
ETS puts the local copy on the server and releases it for other users. Actions in the background
|
| Check-In and keep Checked-Out |
ETS puts the local copy on the server first and keeps it then locked for other users, this is to synchronize the server with the local copy. Use case: Backup Actions in the background
|
| Get local copy |
ETS gets the project from the server, but it cannot be checked-in. Use case: Only view the current state of a project without having to explicitly check this project out on the local computer, thereby blocking it from editing elsewhere. Actions in the background
|
| Force Check-In |
The project on the server will be overwritten by the local version anyway, use this with care because work of the currently checked-out user will be lost. Use case: Commit changes on the project in the archive although one is not the actual editor of the project (e.g. the actual user is on holiday, or has left the company but the project should be edited further). Actions in the background
|
Please consider, currently checked out projects cannot be checked-in in a normal way if - in between at the local computer - the windows user user name/computer name have changed (the checked out project needs to be re-imported in a manual way)