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
2021-07-29 20:23:27 +00:00
parent c76e1cad3b
commit b22769a585
5 changed files with 137 additions and 56 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -4,7 +4,11 @@
Notes for docs:
All selectable dates are advanced relatively based on the next service date calculation:
Next service date is calcualted as the repeat interval selected on PM then if exclude days are set the next service date is checked to ensure it doesn't fall on an excluded day of week. If it does fall on an excluded day then 1 day is added and it's checked against excluded days and this continues until it hits a non excluded day of week.
This Next service date calculated has the previous service date subtracted giving the total time span difference between the current generate date and the next generate date.
PM Scheduled user dates are set to empty in generated work order regardless of setting in PM to prevent blocking due to "Allow schedule conflicts" set to false, and also AyaNova can't guess what the scheduled date should be so this way a PM scheduled users collection is useful to have a crew of workers established but exact dates still need to be set after generation.
That time span is then added to all the current dates (such as scheduled user start date etc) in the PM as well as the Next service date and the PM is saved ready for the next time it will go through the process again.
If an date is left empty it will not be affected by this process so for example if you do not want a scheduled user date to be set or modified leave it blank in the PM.