So it's a hidden field?
Posted: Mon Oct 18, 2010 4:51 pm
Question:
So it's a hidden field?
Answer:
Technically, all Profound UI fields are declared as hidden fields in the DDS. The Rich UI definition is what determines what happens with these fields.
Rich Display File screens consist of widgets. Each widget has many properties. And each property can be bound to an RPG field.
For example, a textbox will have a value property bound to an RPG field. This field will dictate what is shown in the textbox and what is sent to the server when the user types into the textbox. But the textbox may also have RPG fields that control text color, font, visibility, texbox width, etc. In a way, you can think of these fields as hidden fields because they do not appear on the screen like the field bound to the value property.
So it's a hidden field?
Answer:
Technically, all Profound UI fields are declared as hidden fields in the DDS. The Rich UI definition is what determines what happens with these fields.
Rich Display File screens consist of widgets. Each widget has many properties. And each property can be bound to an RPG field.
For example, a textbox will have a value property bound to an RPG field. This field will dictate what is shown in the textbox and what is sent to the server when the user types into the textbox. But the textbox may also have RPG fields that control text color, font, visibility, texbox width, etc. In a way, you can think of these fields as hidden fields because they do not appear on the screen like the field bound to the value property.