This commit is contained in:
2021-05-21 19:36:49 +00:00
parent 82abb4c5df
commit e10cc43ab1
3 changed files with 12 additions and 0 deletions

View File

@@ -1,3 +1,7 @@
# SERVICE RATES Placeholder
This is a placeholder page for sections that are not written yet
Notes to include in docs:
Data integrity - Service rate values are stored only in the Service rate object and linked to by objects affected by that Service rate (e.g. Work order item Labor record). If a Service rate has been selected on another object the fields affecting price calculations are not editable (Cost, Charge etc). Other fields remain editable as they would not affect past price calculations. when saving a Service rate with price affecting changes, the AyaNova server will check if any objects are found to be using this Service rate and if they are it will not save but instead report back an error with all object types using this rate. Options are to remove or switch the Service rate from the existing in-use objects to be able to edit those fields or simply make a new Service rate.

View File

@@ -1,3 +1,7 @@
# TAX CODES Placeholder
This is a placeholder page for sections that are not written yet
Notes to include in docs:
Data integrity - Tax code values are stored only in the Tax Code object and linked to by objects affected by that Tax code (e.g. Work order item labor record). If a Tax code has been selected on another object the fields affecting price calculations are not editable (percentage, tax on tax etc). Other fields remain editable as they would not affect past records tax calculations. After an edit and save the AyaNova server will check if any objects are using this Tax code and if any are found will report back all object types involved. Options are to remove or switch the Tax code from the existing in-use objects to be able to edit those fields or simply make a new Tax code.

View File

@@ -1,3 +1,7 @@
# TRAVEL RATES Placeholder
This is a placeholder page for sections that are not written yet
Notes to include in docs:
Data integrity - Travel rate values are stored only in the Travel rate object and linked to by objects affected by that Travel rate (e.g. Work order item travel record). If a Travel rate has been selected on another object the fields affecting price calculations are not editable (Cost, Charge etc). Other fields remain editable as they would not affect past price calculations. when saving a Travel rate with price affecting changes, the AyaNova server will check if any objects are found to be using this Travel rate and if they are it will not save but instead report back an error with all object types using this rate. Options are to remove or switch the Travel rate from the existing in-use objects to be able to edit those fields or simply make a new Travel rate.