You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When an inspection is marked completed by a technician it is still possible for changes to be made. This could cause communication problems as this could occur after a report has been sent to customer.
** Possible solution would be to lock DI changes if status is >=22 (Insp Complete) and require that SA to change status to 20(Inspecting) so that tech can make changes.
The text was updated successfully, but these errors were encountered:
@scaspers it sounds like we should consider changing the states to
22 = Inspection ready for service writer review
...
Some X > 22 = Inspection complete?
If at all possible I think we should see if we should add more states that tend to auto advance through them via other business process flows instead of loop backwards in the flow if that is ok as it will make writing more maintainable code thru the system easier.
Either way, lets discuss in more detail the use case and priority when you're ready.
When an inspection is marked completed by a technician it is still possible for changes to be made. This could cause communication problems as this could occur after a report has been sent to customer.
** Possible solution would be to lock DI changes if status is >=22 (Insp Complete) and require that SA to change status to 20(Inspecting) so that tech can make changes.
The text was updated successfully, but these errors were encountered: