2023 became 2024...can you believe it?
This commit is contained in:
@@ -47,7 +47,7 @@ Service rates Cost and Price fields are **locked** to prevent editing once they
|
|||||||
|
|
||||||
### Retiring
|
### Retiring
|
||||||
|
|
||||||
When a rate is retired it should be set to inactive by un-checking it's Active checkbox and a new rate created to take it's place. Rate names must be unique so for example if a rate changes yearly then the old rate might be called "In-shop service 2023" and the new rate called "In shop service 2024" to ensure names are unique and recognized by users.
|
When a rate is retired it should be set to inactive by un-checking it's Active checkbox and a new rate created to take it's place. Rate names must be unique so for example if a rate changes yearly then the old rate might be called "In-shop service 2024" and the new rate called "In shop service 2025" to ensure names are unique and recognized by users.
|
||||||
|
|
||||||
### Contract service rates
|
### Contract service rates
|
||||||
|
|
||||||
|
|||||||
@@ -46,7 +46,7 @@ Travel rates Cost and Price fields are **locked** to prevent editing once they a
|
|||||||
|
|
||||||
### Retiring
|
### Retiring
|
||||||
|
|
||||||
When a rate is retired it should be set to inactive by un-checking it's Active checkbox and a new rate created to take it's place. Rate names must be unique so for example if a rate changes yearly then the old rate might be called "In-shop travel 2022" and the new rate called "In shop travel 2023" to ensure names are unique and recognized by users.
|
When a rate is retired it should be set to inactive by un-checking it's Active checkbox and a new rate created to take it's place. Rate names must be unique so for example if a rate changes yearly then the old rate might be called "In-shop travel 2023" and the new rate called "In shop travel 2024" to ensure names are unique and recognized by users.
|
||||||
|
|
||||||
### Contract travel rates
|
### Contract travel rates
|
||||||
|
|
||||||
|
|||||||
@@ -6,11 +6,17 @@ If you are viewing this page from your local copy of AyaNova be advised that it
|
|||||||
|
|
||||||
See the [upgrade instructions](ops-upgrade.md) section of this manual for details.
|
See the [upgrade instructions](ops-upgrade.md) section of this manual for details.
|
||||||
|
|
||||||
## 2023
|
## 2024
|
||||||
|
|
||||||
|
|
||||||
### AyaNova 8.1.1
|
### AyaNova 8.1.1
|
||||||
IN PROGRESS
|
|
||||||
|
Released XXXXX
|
||||||
|
|
||||||
|
**Fixed**
|
||||||
|
|
||||||
|
- App: Fixed issue where some users were seeing an error when dropping file attachments on to a record. (This error did not affect the functionatlity of attaching files)
|
||||||
|
|
||||||
|
## 2023
|
||||||
|
|
||||||
### AyaNova 8.1.0
|
### AyaNova 8.1.0
|
||||||
|
|
||||||
|
|||||||
@@ -7,7 +7,7 @@ theme:
|
|||||||
site_name: AyaNova manual
|
site_name: AyaNova manual
|
||||||
site_dir: "../../../server/AyaNova/wwwroot/docs"
|
site_dir: "../../../server/AyaNova/wwwroot/docs"
|
||||||
strict: true
|
strict: true
|
||||||
copyright: Copyright © 2023 Ground Zero Tech-Works Inc. REV-2023-11-22
|
copyright: Copyright © 2024 Ground Zero Tech-Works Inc. REV-2024-01-25
|
||||||
extra:
|
extra:
|
||||||
generator: false
|
generator: false
|
||||||
# Extensions
|
# Extensions
|
||||||
|
|||||||
Reference in New Issue
Block a user