09-11-2018, 11:15 AM
Hi
We're using the SQL DB way of connecting. In some very rare cases, like a Disaster Recovery Plan test or an actual Disaster, the DB is unavailable.
When it's foreseen downtime, you can start the application in advance and select "Switch to Offline Mode". Would it be possible to have this cached (preferably encrypted & possibly but not necessarily read-only) local DB/xml/... file created proactively? This could be an option, if you prefer not to create this file by default, if you would prefer it not have an influence on application startup time for example..
An alternative we prefer to avoid, is people creating an unmanaged local connections file. At this moment we're kind of forced to leave the option enabled so people can work in case of DB downtime. But we're reluctant to pass on the license file to 300+ users for them to be able to use the local file option beyond the 30 day trial period...
At startup the application would thus detect that the DB is unavailable and give you the option to work offline. An initial startup to a live DB is obviously a prerequisite to be able to build the tree.
Currently the application simply times out and says: Connection could not be established. A connection to your current environment could not be established. Please select another one.
Thanks in advance
We're using the SQL DB way of connecting. In some very rare cases, like a Disaster Recovery Plan test or an actual Disaster, the DB is unavailable.
When it's foreseen downtime, you can start the application in advance and select "Switch to Offline Mode". Would it be possible to have this cached (preferably encrypted & possibly but not necessarily read-only) local DB/xml/... file created proactively? This could be an option, if you prefer not to create this file by default, if you would prefer it not have an influence on application startup time for example..
An alternative we prefer to avoid, is people creating an unmanaged local connections file. At this moment we're kind of forced to leave the option enabled so people can work in case of DB downtime. But we're reluctant to pass on the license file to 300+ users for them to be able to use the local file option beyond the 30 day trial period...
At startup the application would thus detect that the DB is unavailable and give you the option to work offline. An initial startup to a live DB is obviously a prerequisite to be able to build the tree.
Currently the application simply times out and says: Connection could not be established. A connection to your current environment could not be established. Please select another one.
Thanks in advance