Assigned to field is READ ONLY cannot edit.

[cpinedatx94]

I have a "Assigned to" field on my work order form that isn't able to be edited. I've checked the debugger and I can see that "WRITE" is set to false.

After navigating to ACL for it im met with a un-editable screen.

Can someone please assist me. I just need to make this field editable! Thanks

[cpinedatx94]

This is what my script condition shows. My "assignment group" also had a ACL rule on it just like this. Created by "admin" leading me to believe this is OOB. Makes no sense because how would you even assign people to the work order if its un-editable OOB. Im missing something here.

[Kieran Anson · Accepted solution]

So I installed FSM on my PDI. OOB behaviour is:

Record level write behaviour (grants access to write, but not to all fields, refer to the second part)

1. Opened by is 'me' or empty
2. User has wm_basic role can write to records unless
   1. sn_fsm.use_query_rules is true and query rules need to be respected
      1. Need to have either wm_qualifier, wm_dispatcher, wm_agent
      2. FSM territory planning needs to be enabled

Field level behaviour (need to pass record level write ACL in order to do the following)

1. Users with wm_task_initiator can amend the assigned_to field when the wm_order is in draft
2. User needs to have wm_agent, wm_approver_user, wm_qualifier, or wm_dispatch
   1. and state of Draft, Qualified, Assigned, Work In Progress
   2. and the script sn_sm.SMConfiguration() checks whether the wm_order itself is a workable task, or a lifecycle driver to which child tasks should be created. (OOB wm_order should be a parental task).

So that's why you can't edit it. The wm_order isn't intended to be assigned unless you've modified the sm_config record for field_service to allow assignment to an individual. Instead it's meant to be assigned to a group and individual sub-tasks assigned to users

[Bert_c1]

It comes with the "Field Service Management" ("com.snc.work_management") plugin/app. the ACL script is:

(current.state == 1 || current.state == 10 || current.state == 16 || current.state == 18) && (new sn_sm.SMConfiguration().isEnabled(current, 'request_driven', false));

I can't find any script include that defines the SMConfiguration class. I do see one named "SMConfigUtil" that contains a 'isEnabled' function using the 3 parameters.  Seems a Support Case may be needed. Try making the ACL in-active and test.