A new Environment Name field exists in the server settings
There is only a single environment name per database, even when multiple servers are connected to it
Advanced Clustering still uses the server name (server ID as fallback) for the dashboard UI
The JNLP title contains both the environment name and server name (if not blank)
Currently the server name is stored as "core.". When logging in via distributed sessions, the server name may appear to not be persisted correctly. The original purpose behind the server name was to be able to name different Mirth Connect environments, not necessarily instances.
Store the environment name in the configuration table, category "core" and name "environmentName".
Currently the server name is stored as "core.". When logging in via distributed sessions, the server name may appear to not be persisted correctly. The original purpose behind the server name was to be able to name different Mirth Connect environments, not necessarily instances.
Store the environment name in the configuration table, category "core" and name "environmentName".
Imported Issue. Original Details: Jira Issue Key: MIRTH-4345 Reporter: narupley Created: 2018-12-12T11:52:48.000-0800