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-01-08 16:18:49 +00:00
parent 92db81b584
commit 0a2e81f608
23 changed files with 136 additions and 118 deletions
Download Patch File Download Diff File Expand all files Collapse all files

32
docs/8.0/ayanova/docs/acc-service-rates.md
View File

@@ -1,6 +1,7 @@
# Service rates
[UNDER CONSTRUCTION]
#b4beta
The Service rates [form](ay-start-form-overview.md) is used to edit Service rates.
@@ -26,40 +27,52 @@ Read only access
## How to access Service rates
Service rates are accessed in the following ways:
- From the `Accounting` navigation pane `Service rates` item
- By clicking on the [open record icon](ay-start-form-select-list.md#opening-selected-record) any Service rate selection list on any other form where Service rates can be selected such as the Work order, Quote and Preventive Maintenance forms
## How service rates work
Service rates are set on Work orders, Quotes and Preventive Maintenance orders to indicate a charge for service provided.
Service rates are set on Work orders, Quotes and Preventive Maintenance orders to indicate a charge for service provided.
Service rates can not be edited to change their Cost or Price once they are used on another object in order to protect the historical record. This means that you must make a new service rate if the price or cost needs to be changed.
Service rates can not be edited to change their Cost or Price once they are used on another object in order to protect the historical record. This means that you must make a new service rate if the price or cost needs to be changed.
## Service rate data table
The Service rates [data table](ay-start-form-data-tables.md) lists all the service rates available and data table [common menu options](ay-start-form-data-tables.md#common-menu-options).
## Service rate edit form
The Service Rate edit form contains all the [standard edit form](ay-start-edit-forms.md) functionality and contains the following fields:
#### Name
This is the name of the rate as it's displayed in forms and reports. A rate name must be unique from all other service rates entered.
This is the name of the rate as it's displayed in forms and reports. A rate name must be unique from all other service rates entered.
#### Account number
Optional convenience field not used by AyaNova itself.
#### Retail charge
Charge to customer per unit for this service. [Currency](ay-start-data-types.md#currency) field.
#### Cost
Internal cost per unit to provide this service. [Currency](ay-start-data-types.md#currency) field.
#### Unit charge description
This is the unit the rate is billed in for example "Hours", "Incidents" and will be displayed on reports as well as in the user interface.
#### Contract rate
#### Active
If checked this rate will only be availble to select on Work orders with a [Contract](svc-contracts.md) with matching rates selected.
#### Active
Rates that are set to Active can be selected on new Work orders and other objects that user Service rates.
Rates not set to Active will still show in historical records but can not be selected for new records; this is how you retire a rate from use.
#### Notes
@@ -80,10 +93,3 @@ Standard AyaNova object [wiki control](ay-start-form-wiki.md).
#### Attached files
Standard AyaNova object [attachments control](ay-start-form-attachments.md).

6
docs/8.0/ayanova/docs/ay-start-form-select-list.md
View File

@@ -1,5 +1,5 @@
# Select lists
#b4beta (change filter to search below and check if that breaks links, searching makes more sense in this case and is easier to understand)
## Overview
Select lists are used to select and / or filter for a value on forms. For example a Part on a Workorder form.
@@ -11,13 +11,13 @@ They are also used to open the record selected in them or a new record if no sel
## Selecting
A maximum of 100 items are returned by the server for any select list and clicking on a select list will cause it to drop down and by default fetch the first 100 records found for that type of object in the AyaNova database. For objects that there are less than 100 of this is often all that is required to select the item you need. However for larger lists a filter will be necessary.
A maximum of 100 items are returned by the server for any select list and clicking on a select list will cause it to drop down and by default fetch the first 100 records found for that type of object in the AyaNova database. For objects that there are less than 100 of this is often all that is required to select the item you need. However for larger lists searching by entering a few characters that match the item desired will be necessary.
### No selection item
Select lists have a special item represented by a single dash character `-` which indicates that no selection has been made for that item.
## Filtering
## Filtering / searching
The fastest way to select an item when there are a large number of choices is by filtering.

23
docs/8.0/ayanova/docs/ay-start-form-tags.md
View File

@@ -3,33 +3,36 @@
## OVERVIEW
Tags are a powerful feature of AyaNova that can be used to group or categorize objects for reporting, searching and selection.
Tags are short strings of text that are shared between all users and all major objects in AyaNova.
Tags are short strings of text that are shared between all users and all major objects in AyaNova.
Objects can have more than one tag and completely different object types (e.g. Parts, and Users) can have the same tag.
## WHAT ARE THEY FOR?
Tags are used for any purpose that makes sense for *your* business. AyaNova does not limit how tags are used and allows nearly everything to be tagged.
Tags are used for any purpose that makes sense for _your_ business. AyaNova does not limit how tags are used and allows nearly everything to be tagged.
By tagging related objects you can more easily select them as a whole for things like searches in [select lists](ay-start-form-select-list.md), reporting, business metrics, graphs and charts, process control etc.
Because you can use multiple tags on each object and multiple different object types can share the same tags you can use tags for several different purposes at the same time.
For example both a Customer and a Service technician could share the same tag "zone1" and you could then limit reporting to only items tagged "zone1" if that makes sense for your business.
You might use a tag to indicate the steps in a process that an object goes through, for example a Quote for a customer may require several staff members to put it together so the service manager may put all the tags of each department that must work in turn with that quote and as each one completes their part they remove their tag until it's completed.
Each department can view a list filtered by their particular tag so they can see what needs to be done.
You might use a tag to indicate the steps in a process that an object goes through, for example a Quote for a customer may require several staff members to put it together so the service manager may put all the tags of each department that must work in turn with that quote and as each one completes their part they remove their tag until it's completed. Each department can view a list filtered by their particular tag so they can see what needs to be done.
## TAG FORMAT
You can enter any text you want for a tag as long as it's less than 255 characters, lower case and has no spaces in it. Spaces are not allowed in tags and when creating a tag spaces will automatically be converted to dashes.
You can enter any text you want for a tag as long as it's less than 255 characters, lower case and has no spaces in it. Spaces are not allowed in tags and when creating a tag spaces will automatically be converted to dashes.
## SELECTING A TAG
Tags are selected on forms with the tag control.
Multiple tags can be set for each object.
Enter text into the tag control which will search the server for previously entered tags as you type text into it. If a matching tag is found it will appear in the selection list below. Click on a tag in the list to add it to the collection.
Enter text into the tag control which will search the server for previously entered tags as you type text into it. If a matching tag is found it will appear in the selection list below. Click on a tag in the list to add it to the collection.
## CREATING A TAG
If the text you type into the tag control turns up no results, the control will offer to add it as a new tag by showing an Add icon below. Click on the icon to add the tag to the collection. Once this object is saved that tag will now show up in future tag searches for all users.
If the text you type into the tag control turns up no results, the control will offer to add it as a new tag by showing an Add icon below. Click on the icon to add the tag to the collection. Once this object is saved that tag will now show up in future tag searches for all users.
## DELETING A TAG
To remove a tag from an object click on the remove icon beside it in the tag control and save the record.
To remove a tag from an object click on the remove icon beside it in the tag control and save the record.

2
docs/8.0/ayanova/docs/ay-start-user-intro.md
View File

@@ -2,7 +2,7 @@
How to use this help manual
#b4beta
#b4beta (maybe this page isn't required? links?)
## Searching

2
docs/8.0/ayanova/docs/common-log.md
View File

@@ -1,5 +1,5 @@
# LOGGING
#b4beta (why is this here, isn't this ops info? links? sb client end log instead if not in ops?)
AyaNova keeps a log of important events for troubleshooting purposes.
AyaNova logs to the file log-ayanova.txt.

2
docs/8.0/ayanova/docs/cust-contacts.md
View File

@@ -1,6 +1,8 @@
# CUSTOMER-CONTACT Placeholder
[UNDER CONSTRUCTION]
#b4beta (this is new and should be doccd)
This form is used to manage Customer type Users known as "Contacts" in AyaNova.
## LOGIN NAME

103
docs/8.0/ayanova/docs/home-notify-subscriptions.md
View File

@@ -1,107 +1,112 @@
# NOTIFICATION SUBSCRIPTIONS
AyaNova has dozens of different types of notifications that can be subscribed to for events of interest.
They can be delivered via email / SMS or directly in application or both.
This form is used to control notification subscriptions which are events that happen within AyaNova that a User may be interested in knowning about.
This form is used to control notification subscriptions.
Notifications can be delivered in multiple ways: via email / SMS or directly in application.
## Notification subscription list
The list form shows all the notifications you are currently subscribed to. You can open a subscription to edit it by clicking on it's ID value.
The list form shows all the notifications you are currently subscribed to. You can open a subscription to edit it by clicking on it's ID value.
## Notification subscription edit form
Depending on the event type selected you will see different form fields as appropriate to that event.
### Notification event
This is where you select the type of event you are subscribing to. All event types are listed below.
This is where you select the type of event you are subscribing to. All event types are listed below.
### Type
Some events are related to core AyaNova business object operations, for example when an object is created or deleted or modified. This is the field where you select the type of object you are interested in such as a Customer or Work order etc. All core AyaNova business object types are available here.
Some events are related to core AyaNova business object operations, for example when an object is created or deleted or modified. This is the field where you select the type of object you are interested in such as a Customer or Work order etc. All core AyaNova business object types are available here.
### Notify before event
For age and time based events, this is where you set a time duration of how far in advance of the event date you want to be notified. For example if you are creating subscription for when a service contract expires and you want to be notified 2 weeks in advance of the expiration date you would select 14 days here. You can select days hours and minutes as appropriate. Remember this controls when you are notified *in advance* of the actual date of the event whatever that might be.
For age and time based events, this is where you set a time duration of how far in advance of the event date you want to be notified. For example if you are creating subscription for when a service contract expires and you want to be notified 2 weeks in advance of the expiration date you would select 14 days here. You can select days hours and minutes as appropriate. Remember this controls when you are notified _in advance_ of the actual date of the event whatever that might be.
As you can subscribe to the same event more than once you can use this feature to create an escalating notification system for some events by setting a longer advance notice and having it deliver to a less immediate location, for example In application and then another identical subscription but with a shorter time frame to a more immediately noticeable location such as direct SMS or an alternate address to another user to catch critical events in case they might get missed.
### Status
Events tied to Status settings on other objects such as a Workorder status or Quote status require a selection of the desired status. In those cases a Status field is available to choose the exact status of interest.
Events tied to Status settings on other objects such as a Workorder status or Quote status require a selection of the desired status. In those cases a Status field is available to choose the exact status of interest.
### Decimal value
Some events are related to monetary or other numeric amounts or thresholds, for example a workorder total price exceeded or meter count exceeded, this field will be presented in those cases to enter the numeric amount related to the event that you want to be notified.
### Report
In the case of an event that can have a report associated with it, you can select a report to be automatically sent with the event (in the case of email delivery) or linked to (in the case of in application delivery).
### Delivery method
Currently you can choose between In application which will deliver to the [notifications](home-notifications.md) form and alert via the bell icon at the top of the AyaNova application window and email / SMS delivery via SMTP.
### Deliver to Address
If email / SMS delivery method is chosen this field is where you enter the address for delivery. If it is to your SMS / MMS device then you must set the address provided by your cellular provider for their [SMS / MMS gateway](https://www.wikihow.com/Send-a-Text-from-Email)
By default AyaNova will fill this field in with your email address set in your [User settings](home-user-settings.md) form however you can change it to any value you wish.
If email / SMS delivery method is chosen this field is where you enter the address for delivery. If it is to your SMS / MMS device then you must set the address provided by your cellular provider for their [SMS / MMS gateway](https://www.wikihow.com/Send-a-Text-from-Email)
By default AyaNova will fill this field in with your email address set in your [User settings](home-user-settings.md) form however you can change it to any value you wish.
### Tags
Here you can select one or more [Tags](ay-start-form-tags.md) (if the event is related to a taggable object) to act as a filter to include or exclude specific objects. For example, you could create a subscription to the Object Created event, select the type as Customer and the Tag as "residential". That way any Customer created and saved with the Tag "residential" will trigger a notification to you but if a Customer is created without the tag "residential" you will not be alerted.
Here you can select one or more [Tags](ay-start-form-tags.md) (if the event is related to a taggable object) to act as a filter to include or exclude specific objects. For example, you could create a subscription to the Object Created event, select the type as Customer and the Tag as "residential". That way any Customer created and saved with the Tag "residential" will trigger a notification to you but if a Customer is created without the tag "residential" you will not be alerted.
**All** the tags selected in the subscription are required to be on the object at the moment it is saved / updated / deleted in order to match the subscription requirements and trigger notification. If other tags are on the object besides the ones related to this filter they have no effect on the notification filter.
If no tags are selected then tags are not considered at all when processing notifications.
## Events are triggered when...
### Business object edited
When a new or updated AyaNova core business object is saved or deleted it triggers notification processing.
In other words if you create a new subscription, only objects saved *after* you created that subscription will trigger notifications to you.
In other words if you create a new subscription, only objects saved _after_ you created that subscription will trigger notifications to you.
In the case of time delayed notifications they are still created at the moment of saving the object but with a delayed delivery date.
For example, if you create a subscription to be notified a year after a Customer record is created, the event is created the moment the Customer is created and first saved and stored internally for a year before delivery.
(If that Customer should be deleted before the year is up then that age notification will automatically be deleted)
### Something happens at the server
When an event takes place at the server that triggers events related to server operations. For example when the system backs up automatically.
When an event takes place at the server that triggers events related to server operations. For example when the system backs up automatically.
## General notification type
The General notification type is a special case, all users are automatically subscribed to In Application delivery of general notifications meaning they will always receive critical system notifications as well as direct notifications from other users **inside AyaNova application**
There are no settings adjustable for in app General notifications, however Users can also subscribe to this same type of notification to be delivered via email / sms optionally.
## Notification event types
| EVENT | DESCRIPTION |
| ----- | ------------------------------ |
| ObjectDeleted | Deletion of core business object of selected type and tags |
| ObjectCreated | Creation of core business object of selected type and tags |
| ObjectModified | Any changes and saving of core business object of selected type and tags |
| WorkorderStatusChange | Any *change* of Workorder Status including from no status (new) to a *specific* selected status ID value |
| ContractExpiring | Customer service contract expiration |
| CSR Accepted | Customer service request accepted. (intended for Customer users) |
| CSR Rejected | Customer service request rejected. (intended for Customer users) |
| QuoteStatusChange | Any *change* of Quote Status including from no status (new) to a *specific* selected status ID value |
| ObjectAge | Any object, Age (conditional on AgeValue) after creation event of any object of selected specific type and optionally selected tags |
| ReminderImminent | A Reminder in AyaNova is about to reach it's specified date/time |
| ScheduledOnWorkorder | User is scheduled on (added to) a Work order |
| ScheduledOnWorkorderImminent | Scheduled date and time reached for workorder which User is scheduled |
| WorkorderCompletedStatusOverdue | Workorder not set to a "Completed" type Status before the selected duration from created date |
| WorkorderCompleted | Service work order is set to any status that is flagged as a "Completed" type of status. (Customer / HeadOffice or staff User notification) |
| OutsideServiceOverdue | An item sent for 3rd party service is overdue from projected repair time frame |
| OutsideServiceReceived | An item sent for 3rd party service has been received back |
| PartRequestReceived | An out of stock part requested via a Workorder has been received |
| NotifyHealthCheck | Automatic daily "ping" notification to confirm notification and Generator system is active at server |
| BackupStatus | Result of last Backup operation at server |
| CustomerServiceReminder | Scheduled service date / time is about to be reached. (Customer or HeadOffice type users only) |
| WorkorderTotalExceedsThreshold | The balance of a Work order has exceeded a threshold (the "Andy") |
| WorkorderStatusAge | A Workorder has been sitting at the selected status for longer than the selected time frame |
| UnitWarrantyExpiry | A Unit's warranty expiration date is reached |
| UnitMeterReadingMultipleExceeded | A meter reading has a difference from the last reading by the selected amount (negative OR positive to cover count *down* meters or rollover / reset meters, can tag filter by Unit tag) |
| GeneralNotification | Any general notification including direct text notifications between users (built in but provided for email alternative delivery) |
| ServerOperationsProblem | Any timely and serious issue related to internal AyaNova Server operations requiring attention |
| QuoteStatusAge | A Quote has been sitting at the selected status for longer than the selected time frame |
| CopyOfCustomerNotification | Copy of any notification sent to Customer for AyaNova User. Filterable by Customer Tag |
| WorkorderCreatedForCustomer | Customer notification sent when a service type work order is created for them (or if HeadOffice Contact user, one of their Customers) |
| EVENT | DESCRIPTION |
| -------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| ObjectDeleted | Deletion of core business object of selected type and tags |
| ObjectCreated | Creation of core business object of selected type and tags |
| ObjectModified | Any changes and saving of core business object of selected type and tags |
| WorkorderStatusChange | Any _change_ of Workorder Status including from no status (new) to a _specific_ selected status ID value |
| ContractExpiring | Customer service contract expiration |
| CSR Accepted | Customer service request accepted. (intended for Customer users) |
| CSR Rejected | Customer service request rejected. (intended for Customer users) |
| QuoteStatusChange | Any _change_ of Quote Status including from no status (new) to a _specific_ selected status ID value |
| ObjectAge | Any object, Age (conditional on AgeValue) after creation event of any object of selected specific type and optionally selected tags |
| ReminderImminent | A Reminder in AyaNova is about to reach it's specified date/time |
| ScheduledOnWorkorder | User is scheduled on (added to) a Work order |
| ScheduledOnWorkorderImminent | Scheduled date and time reached for workorder which User is scheduled |
| WorkorderCompletedStatusOverdue | Workorder not set to a "Completed" type Status before the selected duration from created date |
| WorkorderCompleted | Service work order is set to any status that is flagged as a "Completed" type of status. (Customer / HeadOffice or staff User notification) |
| OutsideServiceOverdue | An item sent for 3rd party service is overdue from projected repair time frame |
| OutsideServiceReceived | An item sent for 3rd party service has been received back |
| PartRequestReceived | An out of stock part requested via a Workorder has been received |
| NotifyHealthCheck | Automatic daily "ping" notification to confirm notification and Generator system is active at server |
| BackupStatus | Result of last Backup operation at server |
| CustomerServiceReminder | Scheduled service date / time is about to be reached. (Customer or HeadOffice type users only) |
| WorkorderTotalExceedsThreshold | The balance of a Work order has exceeded a threshold (the "Andy") |
| WorkorderStatusAge | A Workorder has been sitting at the selected status for longer than the selected time frame |
| UnitWarrantyExpiry | A Unit's warranty expiration date is reached |
| UnitMeterReadingMultipleExceeded | A meter reading has a difference from the last reading by the selected amount (negative OR positive to cover count _down_ meters or rollover / reset meters, can tag filter by Unit tag) |
| GeneralNotification | Any general notification including direct text notifications between users (built in but provided for email alternative delivery) |
| ServerOperationsProblem | Any timely and serious issue related to internal AyaNova Server operations requiring attention |
| QuoteStatusAge | A Quote has been sitting at the selected status for longer than the selected time frame |
| CopyOfCustomerNotification | Copy of any notification sent to Customer for AyaNova User. Filterable by Customer Tag |
| WorkorderCreatedForCustomer | Customer notification sent when a service type work order is created for them (or if HeadOffice Contact user, one of their Customers) |

52
docs/8.0/ayanova/docs/home-schedule.md
View File

@@ -1,9 +1,8 @@
# HOME SCHEDULE
## Overview
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:
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.
## Menu options
@@ -11,53 +10,56 @@ Work order item scheduled User records, Review and Reminder records.
The personal schedule menu provides quick access to the currently logged in User's Reminders, Reviews, Work order item scheduled user and Work order item Labor data tables for viewing or reporting
## Settings
![Settings](img/home-schedule-settings.png)
The settings dialog (access by clicking on gear icon at top) controls what is displayed in the schedule. Schedule settings are device independent and saved to the server so that any device used will take these same settings.
### First time in day view
This controls the starting hour to display in day views. Use it to hide unused hours to reduce the need to scroll down.
This controls the starting hour to display in day views. Use it to hide unused hours to reduce the need to scroll down.
### Show
This controls what types of items show in the schedule.
This controls what types of items show in the schedule.
### Work order color source
Choose where the color comes from that is displayed in the schedule:
The Schedule is technically showing Work order item scheduled user records however a Work order has several different colors associated with it. This setting controls which color to use for display in the schedule. Note that you can always click on an event to view a summary of the Work order including all the status and priority color based properties regardless of what is set here.
The Schedule is technically showing Work order item scheduled user records however a Work order has several different colors associated with it. This setting controls which color to use for display in the schedule. Note that you can always click on an event to view a summary of the Work order including all the status and priority color based properties regardless of what is set here.
## Items with no date set
The schedule shows dated items only, any Work order item scheduled user records with no date set can be viewed through the Work order item scheduled Users data table (Service -> Work orders -> Items menu item -> Scheduled Users menu item) which *will* display undated items.
The schedule shows dated items only, any Work order item scheduled user records with no date set can be viewed through the Work order item scheduled Users data table (Service -> Work orders -> Items menu item -> Scheduled Users menu item) which _will_ display undated items.
## Review events
A Review object does not have a duration of it's event associated with it as it only has a single Review Date field. For this reason all Review items will display at their Review Date in the schedule display as a 15 minute interval.
A Review object does not have a duration of it's event associated with it as it only has a single Review Date field. For this reason all Review items will display at their Review Date in the schedule display as a 15 minute interval.
## Moving around
* Today button - this button will take you to the current day in the schedule
* Previous "<" / Forward ">" buttons will move to the next or prior window of time being displayed. In Day view this will move one day, in Month view this will move one month, in Week view one week etc
* Month Year button - This button displays the current month and year and can be clicked on to switch to month view if in any other view
* Settings (Gear / Cog icon) opens the settings form
* View drop down at top right is used to switch the view between the available options
* Date (Day) number - Clicking on a date in the Calendar (i.e. clicking on the "23" for the 23rd of the month) will switch to the day view for that date if in any view other than day view
- Today button - this button will take you to the current day in the schedule
- Previous "<" / Forward ">" buttons will move to the next or prior window of time being displayed. In Day view this will move one day, in Month view this will move one month, in Week view one week etc
- Month Year button - This button displays the current month and year and can be clicked on to switch to month view if in any other view
- Settings (Gear / Cog icon) opens the settings form
- View drop down at top right is used to switch the view between the available options
- Date (Day) number - Clicking on a date in the Calendar (i.e. clicking on the "23" for the 23rd of the month) will switch to the day view for that date if in any view other than day view
## Create / modify / view events
### Devices with a mouse
* Drag and drop an existing event to a new time or day
* Extend the duration of an event: hover the mouse over the bottom, a "grip" will appear, click and drag up or down to modify the time range
* Events with a lock symbol on them are not modifiable
* Click and drag in an empty space in any Day view to create a new object in that time frame selected
* Click an event to open a quick More information display with a summary of that item
* Open the object the event represents for editing by clicking on Open or the icon at the top of the More information dialog
- Drag and drop an existing event to a new time or day
- Extend the duration of an event: hover the mouse over the bottom, a "grip" will appear, click and drag up or down to modify the time range
- Events with a lock symbol on them are not modifiable
- Click and drag in an empty space in any Day view to create a new object in that time frame selected
- Click an event to open a quick More information display with a summary of that item
- Open the object the event represents for editing by clicking on Open or the icon at the top of the More information dialog
### Non mouse devices
* Non mouse devices are not supported for drag or extend operations
* Touch an empty space in any Day view to create a new Reminder or Work order starting at the date and time touched initially
* Touch an event to open a more information dialog
* Edit / view the original object the event is displayed for from the more information dialog "Open" button
- Non mouse devices are not supported for drag or extend operations
- Touch an empty space in any Day view to create a new Reminder or Work order starting at the date and time touched initially
- Touch an event to open a more information dialog
- Edit / view the original object the event is displayed for from the more information dialog "Open" button

2
docs/8.0/ayanova/docs/inv-purchase-order-receipts.md
View File

@@ -1,3 +1,3 @@
# INV-PO-RECEIPTS Placeholder
#b4beta (is this required or part of po doc? links here?)
[UNDER CONSTRUCTION]

2
docs/8.0/ayanova/docs/inv-purchase-orders.md
View File

@@ -1,7 +1,7 @@
# INV-POS Placeholder
[UNDER CONSTRUCTION]
#b4beta not completed yet
## OVERVIEW

2
docs/8.0/ayanova/docs/ops-config-backup-pgdump-path.md
View File

@@ -1,6 +1,6 @@
# BACKUP UTILITY "pg_dump" PATH SETTING
This setting controls where AyaNova will find the PostgreSQL pg_dump utlity for automated backups.
This setting controls where AyaNova will find the PostgreSQL pg_dump utility used forautomated backups.
## Default

2
docs/8.0/ayanova/docs/ops-error-codes.md
View File

@@ -1,5 +1,5 @@
# SERVER ERROR CODES
#b4beta (clean up, remove unused error codes check if any others missing)
AyaNova will provide a server error code when an error arises.
All AyaNova server error codes start with the letter E followed by a number in the range 1000-1999.

2
docs/8.0/ayanova/docs/ops-maintenance.md
View File

@@ -1,6 +1,6 @@
# SERVER MAINTENANCE
AyaNova server should require very little ongoing maintenance, however there are a few things that need to be monitored on a regular basis.
An AyaNova server should require very little ongoing maintenance, however there are a few things that need to be monitored on a regular basis.
## Authorization Roles required

4
docs/8.0/ayanova/docs/ops-migration-from-7.md
View File

@@ -1,5 +1,3 @@
# Migrating from AyaNova 7
#b4beta
how to migrate, install plugin, ui of plugin and what to select and why, how to confirm after migration, next steps post migration etc
#b4beta (already have this page in ops-import-v7.md need to figure out which to use what links and remove one)

2
docs/8.0/ayanova/docs/ops-notification-settings.md
View File

@@ -1,5 +1,5 @@
# NOTIFICATION SETTINGS
#b4beta (consolidate all notificatin ops stuff into one page, check links)
## SMTP settings
This form is used to configure SMTP mail server settings for notification purposes.

2
docs/8.0/ayanova/docs/ops-profile.md
View File

@@ -1,5 +1,5 @@
# OPS-PROFILE Placeholder
[under construction]
primarily for tech support diagnosis in case of slowness
only keeps last half hour of stats
how to use: trigger slow operation, then go to this page right away and walk through looking for slow ness

1
docs/8.0/ayanova/docs/ops-server-state.md
View File

@@ -1,3 +1,4 @@
# OPS SERVER STATE
[UNDER CONSTRUCTION]
#b4beta

2
docs/8.0/ayanova/docs/ops-technical-changes-from-v7.md
View File

@@ -1,4 +1,4 @@
# OPERATIONS INTRO Placeholder
#b4beta (what links here, do we need it?)
- docs link here to explain what the AyaNoav server is so start with a server section and explain client server aspects briefly in overview
- Then go on to the basic sections of ops starting with installation then config and then ongoing maintenance and metrics etc

4
docs/8.0/ayanova/docs/svc-contracts.md
View File

@@ -1,5 +1,5 @@
# CONTRACTS
#b4beta
## Overview
A contract is used to automatically enforce special pricing rules and response time commitments on work orders.
@@ -8,7 +8,7 @@ A contract is used to automatically enforce special pricing rules and response t
todo: this section
todo: when make section for contract rates then go back to acc-service-rates.md and make the contract rate checkbox description link to it directly.
## Automatic contract selection rules

2
docs/8.0/ayanova/docs/svc-pms.md
View File

@@ -1,7 +1,7 @@
# SVC-PMs Placeholder
[UNDER CONSTRUCTION]
#b4beta (docs can refer to work order here for bulk of text)
### Automatic date calculations

2
docs/8.0/ayanova/docs/svc-quotes.md
View File

@@ -1,5 +1,5 @@
# SVC-QUOTES Placeholder
[UNDER CONSTRUCTION]
#b4beta (docs can refer to work order here for bulk of text)
Notes for docs:

2
docs/8.0/ayanova/docs/svc-work-order-status.md
View File

@@ -1,7 +1,7 @@
# svc-work-order-status Placeholder
[UNDER CONSTRUCTION]
#b4beta
todo: locking - locks workorder from edit (other than status for roles that are in status can remove)
todo: completed - used for notification processing
todo: select roles - who can select this status

1
docs/8.0/ayanova/docs/svc-workorders.md
View File

@@ -1,6 +1,7 @@
# SVC-WORKORDERS Placeholder
[UNDER CONSTRUCTION]
#b4beta
docs / sections required