System Info
The system view consists of four cards with general overview of the application and the license.
License information
This card shows which license your organization has acquired and its expiration date.
Dime.Scheduler will warn the users when the license is about to expire. The first notifications will be shown as soon as fourteen days before license expiration.
License features
In accordance with the license type, this card displays the features and its limits. The license contains the following features:
- Amount of Exchange connections
- Amount of resources
- The map
- Amount of resources with gps tracking
- Amount of back office connectors
Each license type has a different threshold.
Dime.Scheduler enforces these license features according to a severity scale. When the map feature is excluded from the license and users attempt to use the map, the map will be disabled. The same is true when the amount of GPS-tracked resources violates the license.
On the other hand, when the amount of back office connectors exceeds the specified value in the license, the planning view will be disabled until the administrator. The same is true for the resources. When this happens, an overlay will show a text similar to "Invalid license. Modify the active resources" with a link. Users with the appropriate access rights need to disable the amount of active resources (by unchecking the "Do Not Show" field), or alternatively, upgrade their license.
Monitored services
As is elaborated in the static configuration section, you can decide which Windows services' uptime you want to monitor. This card will display the status of the ones you selected.
When a service is offline, the card will look like this:
Note that configuration is also enforced in the planning view. Users will only be notified when services - which are being monitored - are down. Downtime of services that are outside of the scope will not be escalated to the users.
Application version
This card shows on which version of Dime.Scheduler you are currently working on. When submitting a support ticket, always include this version number. Chances are we already solved the problem in a later version.
