Page History
...
This is like a constructor value, set only once when the component is added.
Security
| Anchor | ||||
|---|---|---|---|---|
|
Components can be protected using two special security types: visible and protected.
For example. when a component is made readonly from the server the component will make the its UI non-editable. However, a malicious client could still send json messages to the server and update data; that is what this properties avoid server-side.
Similarly, when a form or component is marked invisible, its data should not be sent to the client since it may contain sensitive data.
More information about how these properties work with containers can be found here.
Protecting properties
| Anchor | ||||
|---|---|---|---|---|
|
Protecting properties (of type protected)are used to protect an entire component or specific properties or handlers.
...
Protecting properties themselves can never be modified from the client.
Visibility properties
| Anchor | ||||
|---|---|---|---|---|
|
Visibility properties (of type visible) are similar to protecting properties. They are protecting the component and also hide the data from the client if the component is not visible.
...
Visibility properties themselves can never be modified from the client.
...
Enabled properties
| Anchor | ||||
|---|---|---|---|---|
|
Similarly to properties of type visible , the properties of type enabled are also protecting properties, so they can never be modified from the client.
...
It is important to use type enabled if we want the value from the parent container (i.e. form, portal) to be pushed to the component. For instance if a portal is disabled, then all the components from the portal which have a property of type enabled will also be disabled.
Container security
| Anchor | ||||
|---|---|---|---|---|
|
Protecting and visibility properties on containers will protect the container and also components inside the comtainercontainer
For example forms are containers and the visibility of a form will protect the components inside it as well. So only when server side makes a form visible or a web component (container) from the browser asks that it wants to make a form visible (via servoyApi.formWillShow, provided it does have access itself to that form) that form will be accessible to the browser. Container-like web components can only make forms visible if they have those forms referenced in their (sub)properties (so basically server-side gave them access to be able to make those forms visible).
Readonly/Findmode
| Anchor | ||||
|---|---|---|---|---|
|
Servoy has 2 special controller/foundset based properties where a component also can be notified for.
...
Overview
Content Tools
Activity