.vscode/launch.json

@@ -48,7 +48,7 @@
         "AYANOVA_DATA_PATH": "c:\\temp\\ravendata",
         "AYANOVA_USE_URLS": "http://*:7575;",
         //"AYANOVA_PERMANENTLY_ERASE_DATABASE":"true",
-        "AYANOVA_SERVER_TEST_MODE": "true",
+        "AYANOVA_SERVER_TEST_MODE": "false",
         //"AYANOVA_REPORT_RENDERING_TIMEOUT":"1",
         "AYANOVA_SERVER_TEST_MODE_SEEDLEVEL": "small",
         "AYANOVA_BACKUP_PG_DUMP_PATH": "C:\\data\\code\\postgres_14\\bin\\"

docs/8.0/ayanova/docs/home-reviews.md

@@ -58,7 +58,7 @@ The Review edit form contains the [standard edit form](ay-start-edit-forms.md) f
 
 #### Assigned to
 
-Required field to select the User who will complete the review process.  The user selected here will see the review in their `Home` -> `Reviews` data table form.
+Required field to select the User who will complete the review process. The user selected here will see the review in their `Home` -> `Reviews` data table form.
 
 #### Assigned by
 
@@ -70,7 +70,7 @@ The required "Title" of the review, this field is displayed in the schedule form
 
 #### Review date
 
-This is the required date and time the review must take place.  A review displays in the personal schedule of the assigned user at the date and time.  Reviews always display as a 15 minute long event as there is stop date and so no time period duration for a review. 
+This is the required date and time the review must take place. A review displays in the personal schedule of the assigned user at the date and time. Reviews always display as a 15 minute long event as there is stop date and so no time period duration for a review.
 
 The Review date is also used for review [notifications](home-notify-subscriptions.md).
 
@@ -86,6 +86,7 @@ Date and time a review has been completed.
 
 #### Completion notes
 
+Optional notes regarding the status of the follow up review.
 
 #### Tags
 

docs/8.0/ayanova/docs/home-schedule.md

@@ -1,9 +1,8 @@
-# HOME SCHEDULE
+# Schedule
 
-## Overview
+The personal schedule displays events connected to the currently logged in User and can also be used to create new items or modify existing ones.
 
-The personal schedule displays events tied to the currently logged in User and can also be used to create new items or modify existing ones. There are three kinds of events that can be displayed here:
-Work order item scheduled User records, Review and Reminder records.
+The events potentially displayed are [Work order](svc-workorders.md) item scheduled User records, [Review](home-reviews.md) and [Reminder](home-reminders.md) records.
 
 ## Menu options
 

docs/8.0/ayanova/docs/home-search.md

@@ -1,19 +1,40 @@
-# HOME-SEARCH Placeholder
+# Search
 
-[under construction]
+The search form is used to search the AyaNova database for objects that match the search terms entered.
 
-#b4beta
+## Authorization Roles required
 
-## Overview
+This form is available to all user however results will be limited to objects that the user has rights to view based on their assigned [roles](ay-biz-admin-roles.md).
 
-AyaNova has a search form available by selecting the Search option in the [context menu](ay-start-form-overview.md#form-context-menu)
+## How to access search
 
+- From the `Home` navigation pane `Search` item
+- By clicking on the `Search` menu item present in most AyaNova forms
 
-### Case sensitivity
+## How search works
+
+### Indexing
+
+When a business object is saved the AyaNova server indexes text and other unique fields into the search system. Indexing is the process of breaking out all the unique words in a business object and recording them in a central "dictionary" with a key that indicates the record type and id of the business object that those words were entered on so that they can be searched for and the exact business object they were entered in retrieved.
+
+In order for a word to be indexed for searching it must be 2 to 255 characters long and not be a "Stop word".
+
+### Stop words
+
+Stop words are words that are so common in each language that there is little point in indexing them for search purposes as they are not useful for uniquely identifying records. For example, in English some common stop words are `so` `to` `the` `be` `else` `did` `than` `that` `of` `only`.
+
+AyaNova keeps a list of the most common stop words for each provided [Translation](adm-translations.md) under the translation key names of "StopWords1" to "StopWords7" to break them into smaller chunks for processing. Not all languages require all stopword keys to be used, for example Spanish uses all 7 stopword slots but German requires 3.
+
+While we do not recommend it except in specific exceptional circumstances, it is possible to view the list of stop words and even add your own or remove any that need to be indexed for your business by examining and editing the "StopWords\*" keys in the translation form for the translations in use by your users.
+
+### Searching 
+
+To search for a word or phrase enter terms into the **Search** text box at the top of the form.
+
+#### Case sensitivity
 
 By default AyaNova search is case **in**-sensitive. Case insensitive searching is influenced by the [server locale settings](ops-server-locale.md)
 
-
 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
 
 Explain search phrase entry, stopwords etc
@@ -27,6 +48,4 @@ In cases where there is a identifying number on an object such as an ID or seria
 
 To save bandwidth excerpts are not automatically retrieved but only on demand when user requests for a search result
 
-
-
 There is no facility or setting to search case sensitive, it's just not an option with text indexing we have and differs from picklist which does have a server setting to control that.