admin/raven
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

case 4212

Browse Source
This commit is contained in:
John Cardinal
2022-11-07 17:51:59 +00:00
parent 7cd69d234d
commit 32a8ada907
7 changed files with 211 additions and 16 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
docs/8.0/ayanova/docs/tour-bootstrap-evaluate.md
View File

@@ -114,19 +114,25 @@ Once you have access to AyaNova and some sample data generated to play with we r
2. Take some [guided tours](tour-intro.md) to get your feet wet. A good place to start out is the [Create a Customer guided tour](tour-service-create-customer.md).
3. Work orders are at the heart of AyaNova so the [Create a work order guided tour](tour-service-wo.md) is a good next step.
4. Try out any particular feature that is important for your business. Each AyaNova form has a Help link in the menu that will take you to a help page for that form. Don't be afraid to break anything, you can always generate fresh sample data and start over.
5. What does everyone else think? Get other staff members feedback.
5. What does everyone else think? It's time to get other staff members feedback.
Once you have a fairly good idea where things are and how they work it's time to get other staff trying out AyaNova, make User accounts for all staff in each department who will be using AyaNova and have them try out the features that they would be working with day to day.
Once you have a fairly good idea where things are and how they work it's time to get other staff trying out AyaNova, make [User accounts](adm-users.md) for all staff in each department who will be using AyaNova and have them try out the features that they would be working with day to day. Use the sample Users provided for each [Role](ay-biz-admin-roles.md) as an example to refer to when setting up your own staff User accounts.
For example have the service techs try making [work orders](tour-service-wo.md), entering labour and scheduling themselves. Have the Inventory staff try out the [purchase orders](inv-purchase-orders.md) and entering [Parts](inv-parts.md) etc. Sales staff should try out the [Quoting](svc-quotes.md) system. All administrators or department heads should try out the [dashboard](home-dashboard.md) and set up some business metrics and graphs that relate to their departments.
For example have the service techs try making [work orders](tour-service-wo.md), entering labour and scheduling themselves.
Have the Inventory staff try out the [purchase orders](inv-purchase-orders.md) and entering [Parts](inv-parts.md) etc.
Sales staff should try out the [Quoting](svc-quotes.md) system.
Administrators and department heads should try out the [Dashboard](home-dashboard.md) and set up some business metrics and graph widgets that relate to their departments.
Get feedback from all users and if any questions arise that aren't covered in the manual please do not hesitate to [contact our support department](https://contact.ayanova.com/contact) as always.
It's important that all Users have a chance to try AyaNova and give their feedback and ensure their questions and concerns are answered before moving on, allow plenty of time for this process.
6. Time travel - once everyone who will be using AyaNova is familiar with their area of the program have them go back and look at it again but this time considering different time frames for their tasks.
6. Time travel - once everyone who will be using AyaNova is familiar with their area of the program have them go back and look at it again but this time considering different time frames for any required tasks and trying them out in AyaNova.
For example, what will be their day to day interaction with AyaNova, weekly, monthly, yearly. Looking forward in time like this is often helpful when evaluating business software to catch anything that might be missed during the first few looks and it gets people thinking in terms of actually using the software in production and identifying any concerns that come up early on so there are no surprises later.
For example, what will be their day to day interaction with AyaNova, weekly, monthly, yearly? Looking forward in time like this is often helpful when evaluating business software to catch anything that might be missed during the first few looks and it gets people thinking in terms of actually using the software in production and identifying any concerns that come up early on so there are no surprises later.
7. Customization - AyaNova is highly customizable in many areas and it isn't unsual at all to want to make some tweaks to more closely align AyaNova with a particular business or industry.