|
|
|
|
@@ -23,9 +23,11 @@ Clients have been renamed to Customers
|
|
|
|
|
|
|
|
|
|
### Client User's and Contacts
|
|
|
|
|
|
|
|
|
|
Customers in AyaNova 8 now have unlimited Contacts as a seperate collection of User type objects so you optionally allow them to login to use the Customer interface and subscribe to Customer specific notifications etc.
|
|
|
|
|
Customers in AyaNova 8 now have unlimited Contacts as a seperate collection of User type objects so you can optionally allow them to login to use the Customer interface and subscribe to Customer specific notifications.
|
|
|
|
|
|
|
|
|
|
Migrating from AyaNova 7 will result in a Customer Contact type User being created for each v7 Customer or HeadOffice type User account and in addition a Contact will be created in v8 if the v7 Client has a name set in the "Contact" text field with the Client phone and email numbers being re-used for the contact created this way. The Contact notes text field in v7 that is intended for listing extra contacts will be migrated to the v8 general Customer Notes field as there is no way to safely migrate that freehand text field as additional Contact type users in v8.
|
|
|
|
|
Migrating from AyaNova 7 will result in a Customer Contact type User being created for each v7 Customer or HeadOffice type User account and in addition a Contact will be created in v8 if the v7 Client has a name set in the "Contact" text field with the Client phone and email numbers being re-used for the contact created this way.
|
|
|
|
|
|
|
|
|
|
The Contact notes text field in v7 that is intended for listing extra contacts will be migrated to the v8 general Customer Notes field as there is no practical way to migrate that text field as additional Contact type users in v8.
|
|
|
|
|
|
|
|
|
|
As with all User / Contact accounts created in v8 no login is possible by those users until the administrator allows it and assigns a password so there is no security risk of Contact users logging in that previously could not.
|
|
|
|
|
|
|
|
|
|
@@ -35,13 +37,15 @@ The AyaNova 8 inventory system is completely new and works differently than the
|
|
|
|
|
|
|
|
|
|
It is both more flexible as it allows for easily changing values after the fact but more strict in that it has a far more strict control over inventory values than AyaNova 7 allowed.
|
|
|
|
|
|
|
|
|
|
V8 inventory is "live" and affected instantly when a PO or Work Order are saved with any _changes_ of the Received or consumed quantity (respectively) for a part. This means that when you receive 10 parts on a PO they will be available for use immediately on work orders etc. If the PO is then edited to change the 10 to a 5, the inventory is immediately updated to remove the 5 that are now not received.
|
|
|
|
|
V8 inventory is "live" and affected instantly when a PO or Work Order are saved with any _changes_ of the Received or consumed quantity for a part. This means that when you receive 10 parts on a PO they will be available for use immediately on work orders etc. If the PO is then edited to change the 10 to a 5, the inventory is immediately updated to remove the 5 that are now not received.
|
|
|
|
|
|
|
|
|
|
There is no longer a "Used in service" checkbox in Work orders, they consume inventory immediately upon entry and save.
|
|
|
|
|
|
|
|
|
|
If a work order consumes a quantity of 5 for a part and is saved that amount is _immediately_ removed from inventory. If the work order is subsequently edited to change the 5 to a 3 then a quantity of 2 is immediately returned to inventory upon saving the changed work order.
|
|
|
|
|
|
|
|
|
|
All inventory changes are tracked in a blockchain inside your AyaNova database and this block chain can be viewed in the Inventory transactions data table. Inventory transactions are required for any change of inventory and the inventory transaction blockchain is the only repository for inventory quantities in AyaNova.
|
|
|
|
|
All inventory changes are tracked in a blockchain inside your AyaNova database and this block chain can be viewed in the Inventory transactions data table.
|
|
|
|
|
|
|
|
|
|
Inventory transactions are required for any change of inventory and the inventory transaction blockchain is the only repository for inventory quantities in AyaNova.
|
|
|
|
|
|
|
|
|
|
AyaNova 8 does not permit negative on hand inventory values to exist, every part consumed must have a quantity of on-hand inventory to back it up or it's not allowed to be saved.
|
|
|
|
|
|
|
|
|
|
|
