licensing system change, all internal active, no more scheduleable resources / tech licensing
This commit is contained in:
@@ -118,25 +118,9 @@ After this time AyaNova will not be updateable and technical support will no lon
|
||||
|
||||
This section shows the options selected for the current license including licensed user count and other optional additions.
|
||||
|
||||
##### ServiceTechs licensed option
|
||||
|
||||
**Perpetual licenses only**
|
||||
|
||||
In order to provide fair pricing that scales with the size of a company self installed "Perpetual" AyaNova is licensed by service technician (scheduleable user) count.
|
||||
|
||||
Service technician and sub-contractor type Users also known as "scheduleable users" in AyaNova are Users that have their "User Type" field set to "Service user" or "Sub-contractor user" in their their [User record ](adm-users.md). Users set to this type are scheduleable and trackable for service in AyaNova and selectable on work orders, quotes and preventive maintenance orders.
|
||||
|
||||
Only scheduleable users that are set to Active in their [User record ](adm-users.md) will require a Scheduleable User / service technician license from the total count available as licensed.
|
||||
|
||||
Scheduleable Users only appear in the [schedule form](svc-schedule.md) if they are Active, de-activating a User means their work order scheduled items will not be displayed in the Service -> Schedule form so be sure to re-assign any open scheduled work order items for them to another Active User to ensure it doesn't get lost. You can not see their work order items in the graphical schedule form but you can still see them in the Work order data tables so click through to the Scheduled Users list, filter by the inactive Tech to confirm and re-assign any unfinished work still under their name before de-activating them.
|
||||
|
||||
With a Perpetual license type, non scheduleable users such as administrators or office staff and inactive Scheduleable users will _not_ consume a license and we encourage you to make as many non scheduleable Users as you need to ensure every user has their own unique account in AyaNova.
|
||||
|
||||
##### ActiveInternalUsers licensed option
|
||||
|
||||
**Subscription licenses only**
|
||||
|
||||
When AyaNova is used as a subscription service, every User that can login consumes resources so licensing is affected by any User type who is able to login to AyaNova.
|
||||
Users who can login to AyaNova consume a license.
|
||||
|
||||
There are two types of Users who can login to AyaNova, internal staff Users and external Customer Contact Users.
|
||||
|
||||
@@ -158,9 +142,6 @@ As a convenience, below the license information is a separate section showing th
|
||||
|
||||
This is the current version of AyaNova in use and the build type.
|
||||
|
||||
##### Active scheduleable Users
|
||||
|
||||
Displays the number of Active scheduleable type users currently consuming a license **if** the current license type and AyaNova build is `Perpetual`.
|
||||
|
||||
##### Active internal Users
|
||||
|
||||
@@ -211,31 +192,13 @@ These items are kept as this feature is typically used when people are evaluatin
|
||||
|
||||
## Downgrading a license
|
||||
|
||||
**Perpetual type licenses**
|
||||
|
||||
If a replacement license is installed that has fewer service technicians that the prior license and the administrator has not disabled the extra service techncians first, AyaNova will automatically disable any excess service techs / scheduleable Users by setting their `Active` property to false in order to remain with the purchased license count.
|
||||
|
||||
AyaNova tries to do this in the least disruptive way possible by favoring disabling in this order:
|
||||
|
||||
1. disable subcontractors first over in-house service techs
|
||||
2. users that have no login records (have never logged in to AyaNova)
|
||||
3. oldest last login (users who haven't logged in for the longest time)
|
||||
|
||||
This attempts to not disable current active service technicians.
|
||||
|
||||
We recommend the administrator disable the excess service techs before downgrading the license to avoid any potential disruption.
|
||||
|
||||
If a tech was automatically disabled to remain within the licensed limit that shouldn't be, you can set another tech inactive and then set the de-activated tech back to active so they can continue working.
|
||||
|
||||
**Subscription licenses**
|
||||
|
||||
AyaNova will _not_ autoamtically deactivate excess Users of any kind and license installation will fail if you have not manually disabled excess Users before attempting to install the license.
|
||||
AyaNova will _not_ automatically deactivate excess Users of any kind and license installation will fail if you have not manually disabled excess Users before attempting to install the license.
|
||||
|
||||
## User count exceeded
|
||||
|
||||
If you receive an error message stating that the Server is locked due to exceeding licensed limit this means that AyaNova has found there to be more Active Users than the license permits.
|
||||
|
||||
This is typically a sign that the database has been directly edited outside of AyaNova and needs to be fixed by restoring from backup made _before_ the editing took place or, if it is absolutely _certain_ this was the only change made, setting Scheduleable User's to Active=false to match the _Licensed_ Active Schedulable user count.
|
||||
This is typically a sign that the database has been directly edited outside of AyaNova and needs to be fixed by restoring from backup made _before_ the editing took place or, if it is absolutely _certain_ this was the only change made, setting excess User's to Active=false to match the _Licensed_ Active User count.
|
||||
|
||||
Directly editing the database circumvents the many checks and balances for ensuring data integrity and can lead to breaking AyaNova completely or worse: problems that are not noticed for some time resulting in data damaged beyond reasonable repair requiring restarting with a new empty database.
|
||||
|
||||
|
||||
@@ -86,7 +86,7 @@ A Service User is scheduleable for service and is appropriate for any staff User
|
||||
|
||||
##### Non-Service user
|
||||
|
||||
This type of User does _not_ consume an AyaNova license, is not scheduleable for service and is appropriate for any staff User that isn't directly performing service for the company that needs to be tracked. All users of AyaNova should have their own login account, two or more Users are not able to be logged in at the same time under the same User account.
|
||||
This type of User is not scheduleable for service and is appropriate for any staff User that isn't directly performing service for the company that needs to be tracked. All users of AyaNova must have their own login account, two or more Users are not able to be logged in at the same time under the same User account.
|
||||
|
||||
##### Subcontractor
|
||||
|
||||
|
||||
Reference in New Issue
Block a user