is READ PROTECT the main way to hide a field on the screen?

Jaymer

based on some initial choices, i create a record for the user then present it to be edited.
some fields are maintained behind the scenes and I didn't want them to be on the form showing - so a user didn't try to change them (or it even appear they could be changed)

easy to do in Magic - disable the control (its dimmed) or make it not visible
In THIS example, lets say I DO NOT set a value in "field1".

mark bailey told me to make a rule like:

if BO.field1 > 2 then
READ PROTECT LineItem.field1 FROM ALL EXCEPT System

this makes it not appear. the user doesn't even know its there (or supposed to be there). so far so good.

the User Guide says that ALL FORMS assoc. with the BO will now have that field hidden.
Well, even if I just want to have a maintenance screen for myself that shows ALL fields, that field will be empty on my "browse all fields" query.

It doesn't appear to me to be able to make a field "invisible" only on a certain form.
And in the logger, I see these rules firing constantly when they were only needed to be hidden on 1 form.
I cannot use a form separator and make it invisible under a condition. that doesn't work for my UI layout.
Whats the "aware" way to just hide a field on the screen easily?
thx
jaymer...

johntalbott

How about ....

if BO.field1 > 2 then
READ PROTECT LineItem.field1 FROM ALL EXCEPT System AND Administrator

All Except System will work if the object attributes should NEVER be accessible by a real user.

If you aren't as concerned with permissions down to object level and just want to hide/show, then I believe the "easy way" is to ... create different forms for different purposes/roles. Meaning ... one form for a normal user, one form for maintenance. Don't include the fields you want hidden on the normal user version of the form.

Jaymer

---> John Wrote: "one form for a normal user, one form for maintenance"

yes, that is a great idea I will have to remember, but won't work for this.
my fields need to be hidden based on dynamic values in the field(s).

lets say i have 10 fields.
values are positive or negative.
I want to hide the negative value fields to the user.
but the negative value is important to me (as developer) too see a score value because only positive score values display, but since the control is
READ PROTECT FROM SYSTEM then the fields are hidden ON ALL FORMS.

You're saying add "AND ADMINISTRATOR" to the HIDEs and then they will NOT be hidden from the person who logs in as an Admin user, correct?
So that person could "see behind the scenes" to view all data. That will work if I understand this correctly. Makes sense. Thx

johntalbott

Jaymer wrote
You're saying add "AND ADMINISTRATOR" to the HIDEs and then they will NOT be hidden from the person who logs in as an Admin user, correct?

Correct

customaware

For initial development I use Administrator Jaymer but once getting near completion I create a Access Level for me as the Developer called SuperAdmin.

From then on I basically have two levels of Administration.

Normal Admin for users of the system who are truly administrators of the application with only access to the stuff they should really be able to see, and
SuperAdmin (or you could called it Developer) who see literally EVERYTHING.

BLOMASKY

Or, if you have some "programs" that you want to READ PROTECT some fields, just put that in the process that calls either the query or the form.

i.e.

READ PROTECT BO.alpha .....
READ PROTECT BO.beta.....

EDIT BO USING MAIN

bruce

pureist

and what about unprotecting at runtime a previously protected field?
there is no UNPROTECT action.

customaware

If you want to do that Mat, it is easy to predicate the conditions to READ PROTECT on some other attribute the value
of which can be changed at runtime so that the condition returns FALSE.

pureist

eagles9999 wrote
If you want to do that Mat, it is easy to predicate the conditions to READ PROTECT on some other attribute the value
of which can be changed at runtime so that the condition returns FALSE.

okay, thanks.
I haven't used PROTECT, and just assumed once an attribute was protected at runtime, that because there is no UNPROTECT action, it would not be possible to make it accessible/viewable again at runtime while still in the same form