Best Practice for making fields read only while closing any task

[prajaktanaik]

Hi All,

I need your inputs to fulfill a simple requirement using the best practice. We need to make all the fields on a form (can be incident/problem/change or incident task/problem task/change task) read-only once the state of the form is closed.

For this we have a UI policy created, where the condition is state is Closed and in UI policy actions we have given the required fields to set read-only and this works as expected.

Now, the customer is saying that as soon as he selects the state from the drop-down as Closed, fields become read-only. This I think is the expected behavior of UI policy. But the customer doesnt want it this way, they are saying that it should become read-only after we save the form, because in case if they select Closed and realize they forgot to update any field. We informed them that they can reload the form and update the field.

So I wanted to know if UI policy is a best practice or can we achieve this in any other way?

Thanks,

Prajakta

[ggg]

very good question.

you can do it in an on submit client script.

[prajaktanaik]

thanks for your reply, but is using client script a best practice? 

[Alikutty A]

Hi,

If you need to lockout fields upon closure, then go for an ACL with state condition. An ACL executes before a form is loaded and it will ensure that the fields become read only after the fields are saved to database and reloaded upon closure.

Thanks!

[ggg]

what do i select for operation in the acl?

i would select 'record' for 'type'

and

add a filter of state = 'closed' (for example)