3.0400.2 - Environments

Conquest III version 3.0400.2 provides these improvements:

•      Environments are set up in the Conquest Management Console as:

•      A Registered Conquest III Instance with the option to mark the instance for Production. Only one instance can be Production

•      A Registered Database Connection with the option to mark the database as Production. Only one database can be Production:

•      In the Connection Details Form:

•      Click Test Connection, to make sure it works

•      Click Register database

•      In the Registration Form:

•      If the database is for your Production Data, tick the Production Checkbox

•      Click Register

•      Click Save

•      All Conquest Database Connections need to be registered, to synchronise with the licences set in the Conquest Services Portal

•      The final, mandatory step in changing or setting the Registrations of an Environment, is to launch a Conquest III client session on it. Simply Login then Logout, to synchronise the Conquest III Instance with Conquest Services

•      Environment feedback is given to Conquest III Users with a Message Flag on the right-hand side of the Conquest III Header, to inform them, when they are not in the Production Environment, for whatever reason:

•      When there is no Message Flag displayed, Users are working in the Production instance of Conquest III, on the Production Database. All such sessions consume a licence, as allocated to the User:

•      The Non-Production Data Flag means Users are in the Production instance of Conquest III but with a non-Production Database. Sessions do not consume a licence, provided that the database is Registered:

•      The Non-Production Conquest Flag means Users are in a non-Production instance of Conquest III, with a non-Production Database. Sessions do not consume a licence provided that the database is Registered:

•      Last but not least, the Non-Production Conquest on Production Data Flag means Users are in a non-Production instance of Conquest III, on the Production Database. This combination would be most unusual. All sessions consume a licence:

•      Using an unregistered Database Connection ALWAYS consumes a licence per client session. If you have obsolete Database Connections, it is best to remove them

•      On loss of Internet Access, the Production Conquest III Environment will continue to operate on a cached copy of Licences

•      Accounts and Permissions Form:

•      The Services Account details are now correct

•      Administrators can now modify another Administrator’s Services Account details but not those of an IT Administrator