Unable to modify custom field in WOTask when accepted

[sk4408bc]

In FSM Work Order Task, I have a custom field called u_vehicle and it references the Asset table. I want the FSM agent to be able to edit this field when the WO is assigned to them, but this field is greyed-out/non-editable. The ACL on the Asset table will allow the Agent's role to read, so underlying field is fine, they are able to see the vehicle name, but are unable to edit the u_vehicle field. When I give them the admin role, they are able to edit it. I have checked for UI Policies, client scripts, state models, BRs but unable to pin-point what exactly is causing the field to become un-editable. Please could someone help.

[Mohammed8]

Hi @sk4408bc 

For the field agent to edit this field, you must create a Write ACL on the Work Order Task (wm_task) table for the custom field and include the wm_agent role. Without this write ACL, the field will remain greyed out for the field agent. 

If you find this useful, please mark solution accepted/helpful

Regards, Mohammed Zakir

[sk4408bc]

Hi @Mohammed8 ,

There is wm_task.*   ACLs that allow wm_agent and wm_dispatcher to write to this field.
When the WOTask is in Pending Dispatch or Assigned state, then the wm_dispatcher can edit the vehicle field(which references the u_alm_vehicle table). Now, once the Task is accepted by the Agent, then the Dispatcher can no longer edit the field. Also, from the Agent side, he cannot edit this field at all, no matter what the State of the task. ACL level on the vehicle table is the same for both Dispatcher and Agent. I am guessing there is are the State Models that makes some fields editable and others not, and I did search through a lot of them, but I am not able to find out.  For eg., skills and opened for are editable for the agent but not the other fields.
Please if someone can help me..