Hi Chuck,



So is there anyway to block non editable fields being set using the change template?


Hi Rajesh,



I just tried a template on Eureka that attempts to set two read-only fields and two editable fields. Both read-only fields are protected by ACL (not the read-only attribute on the dictionary.) In both cases, the read-only ACL was respected.



I submit that your field is not being protected (made read-only) by an ACL, but possibly by a UI policy or client script.


Hi Chuck,



Yes, in my case the fields are made readonly using UI policy. Is it possible to restrict the change template being applied to the read only fields.


Hi Rajesh,



Thank you for confirming. The templates do not respect UI policies because they are evaluated on the client side and can be variable depending on almost any condition. The template is imported on the server side. So - short answer "no".



I know that's not the answer you were looking for, but it is an answer. If you would be so kind... please mark it as correct so that others with the same question in the future can find it quickly and that it gets removed from the Unanswered list.


If you are viewing this discussion from your "inbox", use the "mark as correct" option under actions. If you are viewing it directly from the thread use the Correct Answer link (red with a star).


Thank you


View solution in original post

Hi Rajesh,



I agree with Chuck on this one. You will have to adjust access permission via ACL instead of UI policies.