From 15730c267981e42c8c2654ddcbaedb492db8ba22 Mon Sep 17 00:00:00 2001 From: John Cardinal Date: Wed, 9 Feb 2022 15:33:22 +0000 Subject: [PATCH] --- docs/8.0/ayanova/docs/ay-start-changes-from-v7.md | 12 ++++++++---- docs/8.0/ayanova/docs/ay-start-form-wiki.md | 4 ++-- docs/8.0/ayanova/docs/svc-units.md | 2 +- docs/8.0/ayanova/docs/svc-workorders.md | 6 +++--- 4 files changed, 14 insertions(+), 10 deletions(-) diff --git a/docs/8.0/ayanova/docs/ay-start-changes-from-v7.md b/docs/8.0/ayanova/docs/ay-start-changes-from-v7.md index 4de9a89e..62502b35 100644 --- a/docs/8.0/ayanova/docs/ay-start-changes-from-v7.md +++ b/docs/8.0/ayanova/docs/ay-start-changes-from-v7.md @@ -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. diff --git a/docs/8.0/ayanova/docs/ay-start-form-wiki.md b/docs/8.0/ayanova/docs/ay-start-form-wiki.md index e8dbd9aa..14f92c2c 100644 --- a/docs/8.0/ayanova/docs/ay-start-form-wiki.md +++ b/docs/8.0/ayanova/docs/ay-start-form-wiki.md @@ -1,6 +1,6 @@ # Wiki -Wiki is a feature that allows AyaNova users to freely create and edit rich documentation for most AyaNova business objects. There is no specific way to use the wiki feature it can be used for anything that makes sense for that object. +Wiki is a feature that allows AyaNova users to freely create and edit rich documentation for most AyaNova business objects. There is no specific way to use the wiki feature it can be used for anything that is useful to your business. Wikis support URL hyperlinks, can embed images, offer rich formatting options and are indexed and searchable via the [Search](home-search.md) feature. @@ -117,7 +117,7 @@ A more detailed Markdown guide is available here: [www.markdownguide.org](https: ![Image](https://www.ayanova.com/images/AyaNovaIcon256.png) # Emojis - + Emoji characters are supported: 😀⚽🏒🍕🚗☀❤😎
diff --git a/docs/8.0/ayanova/docs/svc-units.md b/docs/8.0/ayanova/docs/svc-units.md index 7cff4b22..4f483b5c 100644 --- a/docs/8.0/ayanova/docs/svc-units.md +++ b/docs/8.0/ayanova/docs/svc-units.md @@ -2,4 +2,4 @@ ![THIS PAGE UNDER CONSTRUCTION](img/underconstruction.svg) -#b4beta + diff --git a/docs/8.0/ayanova/docs/svc-workorders.md b/docs/8.0/ayanova/docs/svc-workorders.md index dd353176..cea4c510 100644 --- a/docs/8.0/ayanova/docs/svc-workorders.md +++ b/docs/8.0/ayanova/docs/svc-workorders.md @@ -421,7 +421,7 @@ Until the work order is saved the items are not actually deleted. #### Realize suggested part quantities -This menu option will appear if this work order item was migrated from an older version of AyaNova where parts were not removed from inventory until they were flagged as Used in service. That system of inventory is incompatible with AyaNova 8 so any migrated work order item part records that had parts on them that were _not_ flagged as Used in service had their quantities migrated as "Suggested quantities" instead. In V8 clicking on realize suggested part quantities will consume those parts from inventory and move the quantity to the normal quantity field. +This menu option will appear if this work order item has suggested quantities entered. Clicking on realize suggested part quantities will consume those parts from inventory and move the quantity to the normal quantity field. ### Units @@ -747,9 +747,9 @@ If you request the part, a work order item [part request](#part-requests) record ![Work order item part requests](img/svc-wo-part-requests.png) -#### Suggested quantity (legacy) +#### Suggested quantity -This field will only display when a work order has been migrated from version 7 of AyaNova and contains parts not yet consumed in inventory. +This field is provided for entering quantities without affecting inventory for planning purposes. As with most AyaNova form fields it can be removed from the form if not required by [form customization](ay-customize.md). #### Description