Why Work Task Actual Work Start is Read Only

[Community Alums]

We are using the FSM Work Orders and Work Order Tasks (WOT). The 'Actual work start' [work_start] field is read-only and can be populated by clicking the 'Start Work' button. BUT our dispatched users may update this information at the end, thus having a wrong work_start value.

Read-only:
After investigating, I found that 'Start work read-only (actual onsite chg)' [c02f044be8756110f8778dfd704f5332] client script makes the work_start field read-only. This client script checks to see if 'Actual onsite arrival' [actual_onsite_arrival] has a value, then makes the work_start editable. Otherwise, it makes it read-only.

We do NOT have the 'OnSite' functionality enabled, thus the actual_onsite_arrival field is not displayed on the form.. I do not understand why they would make the work_start editability depend on a field that is not being used.

MAIN QUESTION: Am I missing anything?

Work around: 

As a workaround, I am planning to update the client script so it will check if the Onsite is enabled. Similar to 'Start work read-only (actual travel chg)' [cf0d5986df203100dca6a5f59bf2636c] client script. My plan is to check if enableOnsite is true before making the work_start field read only.

[Community Alums]

Example where it does check if the OnSite is enabled

Start work read-only (actual travel chg) [cf0d5986df203100dca6a5f59bf2636c] client script
Hide onsite fields if disabled [b2340c6228b16110f8774dcc7ba1091f] client script