uhh? Do nor understand..
'..developing a light I can choose it a field..'? Did autocorrect chime in?
- a field can be set to be accessible or not in layout mode -> choose a different color for the field's background
- a field can be not-accessible via script/trigger -> use the same conditions for conditional formatting
You were right. Ic corrected it - what I was talking about was "layout" not "light"..
Can you give me a hint how to make a "field not-accessible via script/trigger"? Would help but is new to me.
many ways lead to Rome
- You can have a button ('Edit' or whatever named) that toggles a $$Var from 0 to 1
- have a scripttrigger 'on object enter', if $$Var is not 1 (unset), do a commit or a go-to-field[ ], means that field will be left untouched
- You can have that scripttrigger dependent on whatever other condition
- You can set the trigger on object leave with a 'revert record' scriptstep, so users can click into a field for copying, etc (might be annoying when users enter changes..)
You could have two versions of the field and use hide, to show only the one that matches the privileges that the user is logged in with, or dependant on a mode set by a field.
So yes you can. Conditional formatting, and HIDE, are the anti script (this is good btw) life is so much easier using these extensively as your UI validation and flow control.
Hope this helps,
You could use a hide condition based upon mode. For example, Get ( WindowMode ) ≠ 1 will make a field visible only in Find mode.