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-02-08 20:38:41 +00:00
parent 63ec2fd66f
commit 31f7423ee9
22 changed files with 222 additions and 150 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -48,7 +48,7 @@ When a work order status is no longer required it should be set to inactive by u
Work order status is a powerful feature for service process control.
Use of the [Who can select](#who-can-set) and [Who can remove](#who-can-remove) roles fields, the [Is a locking status](#is-a-locking-status) and [Is a completed status](#is-a-completed-status) fields in combination with the [notification system](home-notify-subscriptions.md) can help to ensure adherence to business processes of many kinds.
Use of the [Who can select](#who-can-select) and [Who can remove](#who-can-remove) roles fields, the [Is a locking status](#is-a-locking-status) and [Is a completed status](#is-a-completed-status) fields in combination with the [notification system](home-notify-subscriptions.md) can help to ensure adherence to business processes of many kinds.
Example process control scenarios: