This commit is contained in:
@@ -11,6 +11,8 @@ Don't be a Bertram; read these instructions before attempting installation!
|
||||
|
||||
AyaNova QBI is an *optional* product to use with AyaNova. A license for QBI must be purchased and added to your AyaNova license to use QBI.
|
||||
|
||||
You can [purchase a QBI license from our website](https://ayanova.com/).
|
||||
|
||||
### 64 Bit Windows operating system
|
||||
|
||||
AyaNova QBI requires a 64 bit version of Windows
|
||||
@@ -24,7 +26,7 @@ The following versions of QuickBooks **Desktop** edition **with latest service p
|
||||
- UK editions of QuickBooks Pro and Accountant Editions 2008 or newer
|
||||
- Australian QuickBooks QBi 2008/2009, 2009/2010, 2010/2011, 2011/2012 and QBi 2012/2013
|
||||
|
||||
QuickBooks must be installed to the same computer running QBI and must be able to open your QuickBooks company data file properly.
|
||||
QuickBooks must be installed to the same computer you want to use with QBI and must be able to open your QuickBooks company data file without issue.
|
||||
|
||||
### QBFC15 integration package installed
|
||||
|
||||
@@ -34,19 +36,46 @@ You must [download](https://ayanova.com/download/QBFC15_0Installer.exe) and run
|
||||
|
||||
QBI will not work without QBFC being installed first.
|
||||
|
||||
###
|
||||
## AyaNova User requirements
|
||||
|
||||
### Accounting role User
|
||||
|
||||
AyaNova QBI can only be used by [Users](https://www.ayanova.com/docs/adm-users/) with the [Accounting Authorization Role](https://www.ayanova.com/docs/ay-biz-admin-roles/#accounting).
|
||||
|
||||
### Single login applies
|
||||
|
||||
Be aware that AyaNova only issues a [single login token](https://www.ayanova.com/docs/ay-start-login/#login-token) at a time for the same User account, so if you were to log in to AyaNova QBI while previously logged in to AyaNova, the AyaNova session will be terminated as the new login to QBI has made the original login token expired and invalid.
|
||||
|
||||
If you need to work in both QBI and AyaNova at the same time then we recommend creating a separate User account specifically for using QBI.
|
||||
|
||||
### AyaNova object rights
|
||||
|
||||
Some of QBI's features will modify AyaNova objects and require the same User Role permissions to modify those objects as you would need to do so in AyaNova. Ensure the QBI User is granted sufficient [Roles](https://www.ayanova.com/docs/ay-biz-admin-roles/) to make the modifications necessary.
|
||||
|
||||
## AyaNova Work order status requirements
|
||||
|
||||
AyaNova QBI needs to modify Service Work orders in AyaNova when it Invoices and / or adjusts prices if that feature is used.
|
||||
|
||||
Any security rights and Roles required by AyaNova to make those modifications in the regular AyaNova User interface are also requried when doing the same modifications via QBI, there is no difference security-wise.
|
||||
|
||||
For this reason the AyaNova [Work order status](https://www.ayanova.com/docs/svc-work-order-status/) feature and it's Remove and Select Roles features if used are very relevant to using QBI.
|
||||
|
||||
### Work order status Remove and Select Roles
|
||||
|
||||
In AyaNova a work order can be set to a [Work order status](https://www.ayanova.com/docs/svc-work-order-status/) that [locks](https://www.ayanova.com/docs/svc-work-order-status/#is-a-locking-status) the work order and prevents it from being modified unless a User with sufficient Roles to [remove](https://www.ayanova.com/docs/svc-work-order-status/#who-can-remove) that status changes it to an different, unlocked status which is exactly what QBI does whenever it modifies Work orders.
|
||||
|
||||
This means that the User who logs in to QBI must have any required Roles that are set on Work order status' [Remove roles](https://www.ayanova.com/docs/svc-work-order-status/#who-can-remove) setting and also have any [Select Roles](https://www.ayanova.com/docs/svc-work-order-status/#who-can-select) required for setting the Work order to a post Invoice status if that feature is used.
|
||||
|
||||
The simplest way to accomplish this is to be sure to always add the Accounting role to any Work order Status' required Remove or Select Roles settings if that feature is used.
|
||||
|
||||
### QBI special Work Order Status
|
||||
|
||||
When QBI is installed it automatically creates it's own Work order status: `z_Accounting integration edit` for the purpose of editing Work orders.
|
||||
|
||||
This special status is a requirement for using QBI and if it's removed or modified in such a way as to prevent it working properly QBI will alert you to this on startup with instructions on how to fix this issue.
|
||||
|
||||
This special status use also means you can see at a glance in AyaNova exactly when each work order was modified by QBI by looking at the [Status change history in the Work order header](https://www.ayanova.com/docs/svc-workorders/#work-order-status).
|
||||
|
||||
|
||||
|
||||
|
||||
#################################
|
||||
|
||||
|
||||
TODO
|
||||
|
||||
Login will kick out of AyaNova can't be logged in twice to AyaNova from any location be it the ayanova web app or QBI
|
||||
if necessary make a QBI specific account, in fact we should recommend that
|
||||
Docs mention must be accoutning role user
|
||||
Docs mention that any existing work order statuses that might be set on wo to be invoiced MUST have Accounting role added to their REMOVE and ADD,
|
||||
also POSTWOSTATUS must have allow ADD accounting role
|
||||
docs mention status required for it to work don't fuck with it and if necessary how to fix it
|
||||
|
||||
Reference in New Issue
Block a user