Miscellaneous Settings¶

On this tab, you can configure, among other things, important directories, the server URL, the handling of item numbers, and the REST web service interface.

Directories¶

Allegra stores all but the attachments to items in a database. The attachments, the indexes for full-text search, and backup files are kept directly in the file system. For each of these file groups, you must set up a directory that can be written to and read from the servlet container. The directories must be entered as absolute path names.

TRACKPLUS_HOME

This is where Allegra stores attachments and report templates, among other things. Make sure that you have enough space available and specify the directory as an absolute path.

Backup directory: Allegra can make regular backups of its database and all other data. Such backups are stored in this directory.

Full text search index: Allegra keeps the indexes for the full-text search in the file system, in specially formatted files and directories. The indexes can become very large. Therefore, you should provide enough disk space for this purpose. Also, remember that each time you search for an item and save it, the index must be updated. Thus, it is recommended for the Allegra server to have direct broadband access to this directory.

The server URL¶

Allegra can be run behind a proxy, where the externally visible address differs from the internal address. Usually, Allegra extracts its base URL from the first access to the system after server startup.

Attention

After the initial installation, if you access the system with a web browser on the same machine, Allegra will set “localhost” as the base URL. This could cause issues for other users, which is why it is recommended that you enter the URL manually. The automatic base URL detection works well if there are no proxy servers between the application server and the user clients. If a proxy server is hiding the application server, the correct server URL must be configured.

You must not specify the context name as part of the URL, Allegra determines that itself. Example of the Allegra server URL:

https://gandalf

With this you can reach Allegra at

https://gandalf/allegra

Self-registration¶

It is possible to allow users to register themselves. Registration is always limited to certain email domain patterns, which are configured under “Allowed email pattern” in the configuration section for incoming emails.

You can define groups in which new users, including self-registered users, are automatically included. This allows you to automatically grant newly registered users permissions in the system via their group. Otherwise, these authorizations must be granted manually via role assignments.

If this function is switched on and an unknown user wants to go to any page of the system, they will first be logged in as a guest user. This is useful, for example, if you want to make documents in the Wiki view or queries available to the public without requiring users to have an account.

Item numbers¶

For each item, Allegra generates a unique and global identification number such as 4789 or 6789. When you turn on project-specific item numbering, Allegra generates instead item numbers from a project-specific prefix and a project-specific integer, such as TRA-1, TRA-2, and so on.

Collective task behavior¶

This activates the automated calculation of the start date, end date, and planned value for parents of the collective items from the values of their child items. This should be the default setting. If this is not set, the parent values remain independent of the values of subordinate items. In most cases, this is probably not what you want.

Top-down behavior¶

This allows you to support top-down planning of budgets and deadlines. The top-down values are compared with the bottom-up values and conflicts are marked. For example, if the budget was 100 Euros and the planned value entered by the responsible person was 130 Euro, this point would be marked in a conflict state.

Demo site¶

This is a switch to make installing a demo site easy. In a demo site, it is not possible to save changes to the guest user account. Normally, this should be disabled.

Note about new program version¶

This displays a message if there is a newer version of the program than the one you are currently running. The message is displayed only to system administrators.

Web service interface¶

Here you can enable the REST web service interface that is used by external software, such as the the Service Desk application. The address at which you can reach the web service is the URL of your instance, supplemented by rest. Here you have an example: https://www.trackplus.net/rest/v1/people/auth/login.

Advanced settings¶

Here you can edit the file “GeneralSettings.properties”, in which you can make further, partly system-critical settings.