Each instance of Dime.Scheduler must be registered with a license key. This is a unique value which contains the properties that define the accessible features and their thresholds. The status can be consulted at any time in the system info view.
What is being licensed
Apart from a handful of additional modules, all features are shipped out of the box and free of charge with every license type. However, there are thresholds associated with every license type. For instance, you are able to work with hundreds of resources with the Enterprise subscription as opposed to the Starters license, which will only let you schedule a limited number of resources. This mechanism is also applied for the number of location-tracked resources and multi back office connectors.
There are two modules which can be added to the standard license at extra cost. These are the Exchange synchronizer and the map. These are subject to different licensing conditions as there are third party vendors involved. What these are go beyond the scope of the documentation. Please consult our sales team for additional information.
How Dime.Scheduler monitors the license
When Dime.Scheduler is installed and accessed for the first time, an error page will urge the administrator to activate the license. Dime.Scheduler will be unlocked as soon as the administrator has activated the license.
From this moment, Dime.Scheduler will monitor the application's status and assess whether the license conditions are still met. For example, when the administrator adds the 101th resource when the license caps this to an even 100, the transaction will be blocked. Even when administrators try to circumvent this through other means, Dime.Scheduler will disallow planners from using the planning view. This is an example of a severity A violation.
Other features that are marked with a severity A violation include the Exchange connected resources and back office connectors.
A severity B violation does not make Dime.Scheduler go down in lock down. Yet, it disables a certain set of features. For example, if the map is disabled in the license, it will be disabled in the planning view whereas all the other features remain enabled.
Resolving severity A license violations
To see the limitations of the current license, head over to the System Information page. To resolve severity A violations, please consult the following pages:
The idea is very simple: reduce the number of resources or connectors until the threshold is no longer exceeded.