UserDefined

WebFormIcon Description

This node can be used to add a custom Web Component to an EntityManager interface.

Runtime appearance

In the following example, a custom Web Component was added to an EntityManager node, showing a simple message.

UserDefinedDefinition UserDefinedSectionRT
UserDefined Definition UserDefined Runtime Appearance

Properties

Category Name Value
General Code Identifier for this component. Must be unique inside a Component group node.
Title Title for the component. Currently, it is shown as the corresponding tab title.
Title Attribute Defines an attribute whose value for the instance being shown will be used as the component's title. When available, this value will replace the text set in the Title property.
Title Expression Expression used to evaluate the component's title in runtime. When available, this value will replace the text set by the Title and Title Attribute properties.
Icon Icon used to identify this component. Not available if this node is a direct child of a 'Tabs' group.
GXObject Web Component that should be used to generate this component.
Advanced Condition

Condition that determines if the component is visible or not.
Check Condition In For Each

Determines if the condition will be evaluated inside a For Each command. If the condition references attributes, this property must be set to True.
Table Element Collapsible Determines if the component will be collapsible in runtime. See Collapsible property for details.
Start Collapsed Determines if the component will be collapsed by default in runtime.See Start collapsed property for details.
Component Position Position of this component relative to the previous component.

Child nodes

ArgumentsIcon Arguments

USING "ARGUMENTS" NODES:

By default, the Entity Manager passes the transaction's Primary Key to the WebComponent specified in an UserDefined node.

If the WebComponent object includes different parameters, Arguments nodes may be included to instantiate those parameters. In order to do so, an Arguments node must be added as a child of the UserDefined node, and Argument nodes must be added to that node. The amount of Argument nodes must match the amount of parameters in the WebComponent object. Each Argument node must specify a value for the corresponding parameter in its "Value" property.