This commit is contained in:
@@ -1,8 +1,6 @@
|
||||
# Service rates
|
||||
|
||||
The Service rates [form](ay-start-form-overview.md) is used to edit Service rates.
|
||||
|
||||
Service rates are used to indicate charges for providing service on [Work orders](svc-workorders.md).
|
||||
The Service rates [form](ay-start-form-overview.md) is used to edit Service rates which are used to indicate charges for providing service on [Work orders](svc-workorders.md), [Quotes](svc-quotes.md) and [Preventive Maintenance](svc-pms.md) orders.
|
||||
|
||||
## Authorization Roles required
|
||||
|
||||
|
||||
@@ -2,6 +2,8 @@
|
||||
|
||||
The license form is used to view the AyaNova license and perform license related activities.
|
||||
|
||||
The AyaNova license is stored inside the database so as long as you have a backup of the database you have the license backed up as well.
|
||||
|
||||
## Authorization Roles required
|
||||
|
||||
This form is available to User's with the following [roles](ay-biz-admin-roles.md):
|
||||
@@ -22,7 +24,9 @@ From the `Administration` navigation pane select `License` navigation item.
|
||||
|
||||
### license display
|
||||
|
||||
The license form displays the details of the current AyaNova license in effect:
|
||||
If the server can't find a license in the database then links are shown to begin a trial evaluation, fetch a license key, purchase a license and a link to how to restore the database.
|
||||
|
||||
If the database is licensed, the license form displays the details of the current AyaNova license in effect:
|
||||
|
||||
#### Licensed to
|
||||
|
||||
@@ -81,23 +85,13 @@ 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 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.
|
||||
|
||||
# Key release
|
||||
|
||||
(docs note, this subsection name is linked from Client help adm-license.vue so keep in sync)
|
||||
|
||||
User starts AyaNova, no key found this is one of the options in UI License form under using a previously purchased key with an empty database
|
||||
|
||||
1. can just fetch if it's not fetched yet
|
||||
2. was this being used before and want to start fresh? How to request the key be freed, implications etc
|
||||
3. was this being used before and want to use existing data? Link to restore page in docs
|
||||
|
||||
# User count exceeded
|
||||
## User count exceeded
|
||||
|
||||
If you receive an error message stating that the Server is locked due to exceeding licensed active scheduleable User limit this means that AyaNova has found there to be more Active Scheduleable 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.
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
Modifying the data outside of AyaNova itself should never be attempted unless directed by AyaNova technical support personnel.
|
||||
|
||||
|
||||
@@ -1,7 +1,47 @@
|
||||
# ADM-REPORT-TEMPLATES Placeholder
|
||||
# Report templates
|
||||
|
||||
#b4beta (consolidate this page away, it seems redundent and we can't list every 100 report here pointlessly)
|
||||
Report templates used to generate .pdf report documents from business object data.
|
||||
|
||||
AyaNova report templates are listed here.
|
||||
AyaNova features a built in [report editor](ay-report.md) where existing reports can be customized or completely new ones created.
|
||||
|
||||
You can edit report templates in the [Report template editor](ay-report-edit.md)
|
||||
## Authorization Roles required
|
||||
|
||||
This form is available to User's with the following [roles](ay-biz-admin-roles.md):
|
||||
|
||||
Full access
|
||||
|
||||
- Business administration
|
||||
|
||||
- Business administration - restricted
|
||||
|
||||
Read only access
|
||||
|
||||
- none
|
||||
|
||||
## How to access report templates
|
||||
|
||||
From the `Administration` navigation pane select `Report Templates` navigation item.
|
||||
|
||||
## How report templates work
|
||||
|
||||
Reports are tied to business object types so when a user clicks on the Report menu option within the form for a particular type of business object all reports available for that type of object will be listed.
|
||||
Since reports can be restricted to only users with specific [roles](ay-biz-admin-roles.md), all reports may not be available to all users.
|
||||
|
||||
Reports are available to both lists of a type of object (for example Customers list) and single edit forms for that same type of object (for example the Customer edit form). Stock reports are designed to work with both lists and single objects.
|
||||
|
||||
When a report is selected the AyaNova server will use the report template in conjunction with the object type and records selected to render the report into a .pdf file at the server and send back a link to the AyaNova web app which will trigger it to open the .pdf file in a new browser window. This means you must enable opening popup's in your web browser for your AyaNova server. Normally this will be a prompt in the browser the first time you attempt to view a report.
|
||||
|
||||
If the browser was told *not* to allow the AyaNova server 'site' to open popups then it will need to be re-enabled in the browser by editing the site specific settings to allow popups in order to use the report rendering feature.
|
||||
|
||||
|
||||
## How to modify report templates
|
||||
|
||||
If you have the required authorization role, when you select the `Report` menu option there will be additional buttons allow editing of existing reports or creating completely new reports in the [Report template editor](ay-report-edit.md).
|
||||
|
||||
## Report rendering speed
|
||||
|
||||
Report rendering is the most resource heavy operation that the AyaNova server must do.
|
||||
|
||||
The number of records selected to report and the amount of memory, disk speed and available CPU% at the server directly relates to how long the reports can take to render. You can speed up rendering lengthy reports with a large number of records by breaking them down into smaller chunks. For example, reporting on a month at a time rather than a whole year at a time of records by [filtering](ay-start-form-data-tables.md#filtering-columns) the data table being reported.
|
||||
|
||||
If report rendering speed is a recurring issue, we have [report rendering performance tips](ops-config-report-rendering-timeout.md) specifically for the I.T. system operator responsible for AyaNova server maintenance.
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
# REPORT RENDERING TIMEOUT SETTING
|
||||
# Report rendering timeout setting
|
||||
|
||||
The report rendering timeout value controls how many minutes AyaNova will wait for a report or Export Data operation to complete rendering.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user