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

Browse Source
This commit is contained in:
John Cardinal
2022-03-16 18:39:43 +00:00
parent 928f5da676
commit c6408cd310
1 changed files with 59 additions and 45 deletions
Download Patch File Download Diff File Expand all files Collapse all files

104
docs/8.0/ayanova/docs/beta.md
View File

@@ -1,16 +1,20 @@
# AyaNova 8 Beta testing
Over the next few weeks we will be conducting the AyaNova 8 Beta test program to ensure that the features _you_ rely on are working correctly and to catch anything missed during internal testing. We want to ensure AyaNova 8 is ready for production use and your feedback is essential.
Over the next few weeks we will be conducting the AyaNova 8 Beta test program to ensure that the features _you_ rely on are working correctly and to catch anything missed during internal testing.
AyaNova 8 expands upon AyaNova 7 however it is new and different and while many things will be familiar there is a lot of modernization and changes that may be confusing at first.
We want to ensure AyaNova 8 is ready for production use and your feedback is an essential part of this process.
AyaNova 8 expands upon AyaNova 7 however it is a completely new program and while many things will be familiar there is a lot of modernization and changes that may be confusing at first and we encourage you to make use of this manual.
## About this help manual
This help manual is still under construction in some areas as we work to complete it and those areas are marked with an Under Construction image.
This help manual is still under construction as we work to complete it and some pages are marked with an Under Construction image.
For anything new or substantially changed, we have ensured that those areas of the documentation were completed first.
Please use this manual as your first resource if you run into any issues or something seems confusing. Part of beta testing is also testing the manual and documentation; if you find anything in the manual that could be improved or is unclear please report that as you would any other issues you might come across.
Please use this manual as your first resource if you run into any issues or something seems confusing.
An important part of beta testing is also testing the documentation; if you find anything in the manual that could be improved or is unclear please report that as you would any other issues you might come across.
Remember that a few hours of trial and error can save you minutes of quickly looking at the related Help
@@ -30,61 +34,71 @@ We recommend the following order when beta testing:
4. While testing AyaNova make use of the relevant Help docs by selecting the Help menu option from any area in AyaNova to go to the specific help documentation for that feature.
5. Once you are familiar with AyaNova 8 perform a test migration from AyaNova 7. We have two separate migration guides, a technical guide for the person [performing the migration](ops-import-v7.md) and a separate guide for the business administrator [setting up AyaNova 8 business settings](ay-biz-admin-migrate-v7.md) after migration.
000000000000000000000000000000000000000000
## How to report beta issues
<-- fourth line - time frame of testing section-->
<-- not sure how to word this - the idea is to let end user know right here that there IS a time frame beta will be available til, can CERTAINLY use the word "estimated time line" as not set in stone, perhaps using the words "over the next weeks" to signify we aiming for weeks not months -->
Let us know any issues, your thoughts and impressions. Contact us via [support@ayanova.com](mailto:support@ayanova.com), we look forward to hearing from you!
<-- fifth section - Suggested order of beta testing section -->
Please be sure to mention that your message is in relation to the AyaNova 8 Beta test if it might not be clear to avoid confusion.
<-- use wording to impress this is test only, not for actual day to day, and why its to their own benefit to do so--> <-- and include link to help section -->
We suggest providing the following information when reporting an issue:
<-- sixth section - reporting issues
<--sending us details/bugs/feedback is NOT to be considered "a step" - as we want to encourage sending to us at any point, not "when done trialing"-->
- Steps to reproduce the issue so that the developers can quickly and exactly follow your steps to see and resolve
- Any screenshots, error messages, etc.
- An attached text document containing your [support information](ops-server-information.md#copy-support-information) from your beta AyaNova 8. The support information contains enough information to help our developers diagnose issues quickly and will save time all around.
Let us know any issues, your thoughts and impressions. Contact us via support@ayanova.com We look forward to hearing from you!
Please see the [server information page](ops-server-information.md) for details on how to get this information. We recommend that you gather this data from the **same browser and device** where the issue was encountered to ensure the support information also contains the local browser's error log and other details for a complete set of helpful information.
We suggest providing the following when reporting an issue: <-- maybe also identify here in what ways reporting is a benefit for them... -->
## Frequently asked questions
- include steps to reproduce the issue so that the developers can quickly and exactly follow your steps to see and resolve
- include any screenshots, error messages, etc.
- include an attachment of your "support information" from your beta AyaNova 8 <-- i encourage spelling out the EXACT steps to get this - i.e. log in as superuser (or a user assigned to the role "System Operations" or "System Operations - restricted"), move to Server operations on your navigation drawer on the left -> Server information -> ... -> Copy support information -> paste into NotePad, save and attach to your email.
-- your "support information" will include your beta version, your client browser information and error log, server configuration, server details, DB server details, and all server logs.
### Why should I beta test?
<-- seventh section - Answers to common beta testing questions -->
Beta testing ensures that the software and features you will rely on are working properly and free from defects in your _exact_ environment.
<-- recommend to have 'linked' questions listed at top of section so enduser can scan and see ALL questions, with questions restated along with actual answer further below -->
<-- these are possible common questions, main thing here is to get the end user going as well as anticipate common questions as well as update this with questions we get asked? -->
In addition it's a great way to learn about the many new features and improvements (many of which were suggested by users just like you or may even be features you suggested) in action and be ready to use them when you upgrade.
**Why should I beta test?
**Why should I test import my AyaNova 7 data?
**What features should I test?
**Can I test notifications?
**What if I need a component or feature that is not in the beta version?
**Is there someplace where I can see if an issue has already been reported? <-- link to ayanova 8 forum section specifically for this?-->
### Why should I test importing my AyaNova 7 data?
\*\*Why should I beta test?
I am not sure if there are enticing words for this or not - or if this is a question even needed to be answered. It comes up a lot in my overview search "tell the customer how it will benefit them" but can't find "good" wording.
My main thing here was to point out the benefits for THEM, for THE SERVICE COMPANY, not us. If we were to say "To identify defects and reduce flaws in the component or system" thats can be interpretated as they are providing a benefit FOR US, sure it helps them not to get a buggy program, but its so easily can be interpreated wrong.
\*\*Why should I test import my AyaNova 7 data?
Performing a test migration of your AyaNova 7 data will ensure that any specific issues related to YOUR specific data and database are resolved, as well as giving yourself an idea of how long and whats involved to migrate your 7.x data when AyaNova 8 becomes live, as well as is a great way to try out all of AyaNova 8 with a copy of your own data.
\*\*What features should I test?
We highly recommend testing every component - there may be a feature in AyaNova 7 you never used, whereas in AyaNova 8 the feature is more intuitive and easier to use.
### What features should I test?
We highly recommend testing _every_ component - there may be a feature in AyaNova 7 you never used, whereas in AyaNova 8 the feature is more intuitive and easier to use.
### Can I test notifications?
\*\*Can I test notifications?
You certainly can and should!
Test in-app notifications, email and text messaging.<-- help doc link -->
Test the client notifications too! <-- help doc link-->
Don't worry, your v8migrate will NOT result in your live customers getting accidental notifications while you are testing. <-- blah blah here with brief of whats involved to actually enable a specific customer to get notified, while at same time NOT giving impression it takes a lot of setup .... -->
\*\*What if I need a component or feature that is not in the beta version?
If there is a feature not in AyaNova 8 that you have need for, please let us know by contacting support@ayanova.com Your input can have a real impact on how it is implemented.
It's helpful if you can describe the challenge or pain point you'd like us to solve with the feature. <--- THIS is important, in as few words as possible trying to get across that just asking for a xxx field doesn't give us WHAT it actually does for the enduser ...>
While requesting a feature is not a guarantee or promise that a particular idea will get implemented and added to a future version, it does help us understand what our users would like to see added to the system and how relevant that idea is to our users. We really do appreciate any time and effort from you. Thank you! <wording? again, to get across in a few words as possible that giving us details of how would use, what would accomplish, will go a long way>
AyaNova 8 has many more notification types and a greatly simplified system for subscribing to notifications.
\*\*Is there someplace where I can see if an issue has already been reported?
<--This is NOT for beta testers to log in and submit feedback or bugs -->
<--I'm thinking EITHER ON THIS SAME HELP DOC page at the bottom, OR a specific forum page -->
<-- we can create a specific forum page to point to where you/me can update as needed with reported issues and resolutions etc i.e. identify the beta version found in, beta version resolved in, whats been fixed/addressed etc - so that someone beta testing can see if the issue has already been reported, etc -->
Test User [notification subscriptions](home-notify-subscriptions.md) [in-app notifications](home-notifications.md), email and text messaging.
Test the [Customer notifications](customer-notify-subscriptions.md) too!
We suggest testing Customer notification with sample generated data at first and setting all Customers to the [same email address](ay-evaluate.md#set-all-sample-email-addresses-to-this) to get familiar with it and ensure you aren't sending test notifications to actual Customer email addresses.
Once familiar with how it works, you can also test Customer notifications with your migrated data, however to avoid accidentally emailing test data to your customers we suggest using [Tags](ay-start-form-tags.md) on both the Customer notification subscription and the Customer to only notify Customers with a specific [notification tag](customer-notify-subscriptions.md#customer-tags) set.
For example tag the Customer notification subscription to only go to Customers with a `test-notify` Tag set on their customer record, and then select specific Customers only to test, tag them with the test tag and change their Customer record email addresses to your own test address.
In this way it's not possible to accidentally send a notification to any customer who is not tagged with the testing tag.
### What if I need a component of reature that isn't in the Beta version?
Many of the new features in AyaNova 8 were suggested by our customers.
If there is a feature not in AyaNova 8 that you have need for, please let us know by contacting [support@ayanova.com](mailto:support@ayanova.com) Your input can have a real impact on how it is implemented.
It's most helpful if you can describe the challenge or business process pain point you'd like us to solve with the feature and how it would be used.
We make better solutions when we know the overall big picture of what business problem is needed to be solved and why.
While requesting a feature is not a guarantee or promise that a particular idea will get implemented and added to a future version, it does help us understand what our users would like to see added to the system and how relevant that idea is to our users.
We really do appreciate any time and effort from you.
Thank you!
### Is there some place I can see if an issue has already been reported
Yes!
All known issues are triaged by our support team then posted on our support forum's BETA TEST page at [https://forum.ayanova.com/t/BETATBD](https://forum.ayanova.com/t/BETATBD)