Collibra data entry components

The following components are Collibra specific input fields where you can specify and restrict the type of data you want your users to enter.

File upload

The file upload component allows you to upload a file to the form.

Attributes: General

Attribute	Description
ID	The unique ID of the component.
Label	The label of the component.
Value	The binding for the component. Use an expression to bind the component to its value and specify where the value is saved. For example, use `{{myVariableName}}` to store the value of the component in a variable named myVariableName. Use prefixes to define the scope of the value, for example, root. for referencing the root case to store the value in or parent. to store the value in the parent work item of the current one. For example, `{{root.foo}}` stores the value in the root case using a variable named foo.
Default Value	If a Value is not set, such as on Initialization forms, then this value will be used.
Description	Adds a description to the component.
Ignored	Determines if the component should be hidden and the value excluded from any payload.
Visible	Determines whether the component is visible or hidden. You can also use this expression to only show or hide the component based on another component. For example, if this component is bound to a checkbox component, you can use this expression to show or hide this component based on the checkbox selection made by the user. This is enabled by default.
Enabled	Determines whether the component is enabled or disabled. This is enabled by default.

Attributes: Validation

Attribute	Description
Required	Used to determine if the user must enter a value for this component.
Custom validations	List of additional validations you can apply.

Attributes: Documentation

Attribute	Description
Documentation	Allows you to explain concepts of the component's use for future reference.

Asset type

The asset type component creates a drop-down list that only allows you to select existing asset types. You can restrict the selection to one item, allow multiple items, or provide a proposed list of values.

Attributes: General

Attribute	Description
ID	The unique ID of the component.
Label	The label of the component.
Value	The binding for the component. Use an expression to bind the component to its value and specify where the value is saved. For example, use `{{myVariableName}}` to store the value of the component in a variable named myVariableName. Use prefixes to define the scope of the value, for example, root. for referencing the root case to store the value in or parent. to store the value in the parent work item of the current one. For example, `{{root.foo}}` stores the value in the root case using a variable named foo.
Default Value	If a Value is not set, such as on Initialization forms, then this value will be used.
Description	Adds a description to the component.
Ignored	Determines if the component should be hidden and the value excluded from any payload.
Visible	Determines whether the component is visible or hidden. You can also use this expression to only show or hide the component based on another component. For example, if this component is bound to a checkbox component, you can use this expression to show or hide this component based on the checkbox selection made by the user. This is enabled by default.
Enabled	Determines whether the component is enabled or disabled. This is enabled by default.

Attributes: Data source

Attribute	Description
Storage	Determines how the data retrieved by the REST endpoint should be stored in the variable. You can choose for the following options: - No value -: No part of the entry will be saved in the variable. ID: Only the ID of the selected entry will be saved in the variable. Full value: The whole object will be saved in the variable. This makes it possible to display other values of the selected element within the form as well. Storing the full value could lead to the variables full of unnecessary information depending on the amount of data retrieved by the REST endpoint.

Attribute

Description

Storage

Determines how the data retrieved by the REST endpoint should be stored in the variable.

You can choose for the following options:

- No value -: No part of the entry will be saved in the variable.
ID: Only the ID of the selected entry will be saved in the variable.
Full value: The whole object will be saved in the variable. This makes it possible to display other values of the selected element within the form as well.

Storing the full value could lead to the variables full of unnecessary information depending on the amount of data retrieved by the REST endpoint.

Attributes: Filters

Attribute	Description
Exclude meta	Whether to hide or show meta asset types, such as Asset.

Attributes: More

Attribute	Description
Multi value	Determines if the user can select multiple values in this component.
Proposed values	Allows you to create a list of proposed values that are always presented at the top of the component's input list.
Proposed values only	If selected, the user can only select from the options defined in the Proposed values list.

Attributes: Validation

Attribute	Description
Required	Used to determine if the user must enter a value for this component.
Custom validations	List of additional validations you can apply.

Attributes: Documentation

Attribute	Description
Documentation	Allows you to explain concepts of the component's use for future reference.

Domain type

The domain type component creates a drop-down list that allows you to select existing domain types. You can restrict the selection to one item, allow multiple items, or provide a proposed list of values.

Attributes: General

Attribute	Description
ID	The unique ID of the component.
Label	The label of the component.
Value	The binding for the component. Use an expression to bind the component to its value and specify where the value is saved. For example, use `{{myVariableName}}` to store the value of the component in a variable named myVariableName. Use prefixes to define the scope of the value, for example, root. for referencing the root case to store the value in or parent. to store the value in the parent work item of the current one. For example, `{{root.foo}}` stores the value in the root case using a variable named foo.
Default Value	If a Value is not set, such as on Initialization forms, then this value will be used.
Description	Adds a description to the component.
Ignored	Determines if the component should be hidden and the value excluded from any payload.
Visible	Determines whether the component is visible or hidden. You can also use this expression to only show or hide the component based on another component. For example, if this component is bound to a checkbox component, you can use this expression to show or hide this component based on the checkbox selection made by the user. This is enabled by default.
Enabled	Determines whether the component is enabled or disabled. This is enabled by default.

Attributes: Data source

Attribute	Description
Storage	Determines how the data retrieved by the REST endpoint should be stored in the variable. You can choose for the following options: - No value -: No part of the entry will be saved in the variable. ID: Only the ID of the selected entry will be saved in the variable. Full value: The whole object will be saved in the variable. This makes it possible to display other values of the selected element within the form as well. Storing the full value could lead to the variables full of unnecessary information depending on the amount of data retrieved by the REST endpoint.

Attribute

Description

Storage

Determines how the data retrieved by the REST endpoint should be stored in the variable.

You can choose for the following options:

- No value -: No part of the entry will be saved in the variable.
ID: Only the ID of the selected entry will be saved in the variable.
Full value: The whole object will be saved in the variable. This makes it possible to display other values of the selected element within the form as well.

Storing the full value could lead to the variables full of unnecessary information depending on the amount of data retrieved by the REST endpoint.

Attributes: More

Attribute	Description
Multi value	Determines if the user can select multiple values in this component.
Proposed values	Allows you to create a list of proposed values that are always presented at the top of the component's input list.
Proposed values only	If selected, the user can only select from the options defined in the Proposed values list.

Attributes: Validation

Attribute	Description
Required	Used to determine if the user must enter a value for this component.
Custom validations	List of additional validations you can apply.

Attributes: Documentation

Attribute	Description
Documentation	Allows you to explain concepts of the component's use for future reference.

Attribute type

The attribute type component creates a drop-down list that only allows you to select existing attribute types. You can restrict the selection to one item, allow multiple items, or provide a proposed list of values.

Attributes: General

Attribute	Description
ID	The unique ID of the component.
Label	The label of the component.
Value	The binding for the component. Use an expression to bind the component to its value and specify where the value is saved. For example, use `{{myVariableName}}` to store the value of the component in a variable named myVariableName. Use prefixes to define the scope of the value, for example, root. for referencing the root case to store the value in or parent. to store the value in the parent work item of the current one. For example, `{{root.foo}}` stores the value in the root case using a variable named foo.
Default Value	If a Value is not set, such as on Initialization forms, then this value will be used.
Description	Adds a description to the component.
Ignored	Determines if the component should be hidden and the value excluded from any payload.
Visible	Determines whether the component is visible or hidden. You can also use this expression to only show or hide the component based on another component. For example, if this component is bound to a checkbox component, you can use this expression to show or hide this component based on the checkbox selection made by the user. This is enabled by default.
Enabled	Determines whether the component is enabled or disabled. This is enabled by default.

Attributes: Data source

Attribute	Description
Storage	Determines how the data retrieved by the REST endpoint should be stored in the variable. You can choose for the following options: - No value -: No part of the entry will be saved in the variable. ID: Only the ID of the selected entry will be saved in the variable. Full value: The whole object will be saved in the variable. This makes it possible to display other values of the selected element within the form as well. Storing the full value could lead to the variables full of unnecessary information depending on the amount of data retrieved by the REST endpoint.

Attribute

Description

Storage

Determines how the data retrieved by the REST endpoint should be stored in the variable.

You can choose for the following options:

- No value -: No part of the entry will be saved in the variable.
ID: Only the ID of the selected entry will be saved in the variable.
Full value: The whole object will be saved in the variable. This makes it possible to display other values of the selected element within the form as well.

Storing the full value could lead to the variables full of unnecessary information depending on the amount of data retrieved by the REST endpoint.

Attributes: More

Attribute	Description
Multi value	Determines if the user can select multiple values in this component.
Proposed values	Allows you to create a list of proposed values that are always presented at the top of the component's input list.
Proposed values only	If selected, the user can only select from the options defined in the Proposed values list.

Attributes: Validation

Attribute	Description
Required	Used to determine if the user must enter a value for this component.
Custom validations	List of additional validations you can apply.

Attributes: Documentation

Attribute	Description
Documentation	Allows you to explain concepts of the component's use for future reference.

Relation type

The relation type component creates a drop-down list that allows you to select existing relation types. You can restrict the selection to one item, allow multiple items, or provide a proposed list of values.

Attributes: General

Attribute	Description
ID	The unique ID of the component.
Label	The label of the component.
Value	The binding for the component. Use an expression to bind the component to its value and specify where the value is saved. For example, use `{{myVariableName}}` to store the value of the component in a variable named myVariableName. Use prefixes to define the scope of the value, for example, root. for referencing the root case to store the value in or parent. to store the value in the parent work item of the current one. For example, `{{root.foo}}` stores the value in the root case using a variable named foo.
Default Value	If a Value is not set, such as on Initialization forms, then this value will be used.
Description	Adds a description to the component.
Ignored	Determines if the component should be hidden and the value excluded from any payload.
Visible	Determines whether the component is visible or hidden. You can also use this expression to only show or hide the component based on another component. For example, if this component is bound to a checkbox component, you can use this expression to show or hide this component based on the checkbox selection made by the user. This is enabled by default.
Enabled	Determines whether the component is enabled or disabled. This is enabled by default.

Attributes: Data source

Attribute	Description
Storage	Determines how the data retrieved by the REST endpoint should be stored in the variable. You can choose for the following options: - No value -: No part of the entry will be saved in the variable. ID: Only the ID of the selected entry will be saved in the variable. Full value: The whole object will be saved in the variable. This makes it possible to display other values of the selected element within the form as well. Storing the full value could lead to the variables full of unnecessary information depending on the amount of data retrieved by the REST endpoint.

Attribute

Description

Storage

Determines how the data retrieved by the REST endpoint should be stored in the variable.

You can choose for the following options:

- No value -: No part of the entry will be saved in the variable.
ID: Only the ID of the selected entry will be saved in the variable.
Full value: The whole object will be saved in the variable. This makes it possible to display other values of the selected element within the form as well.

Storing the full value could lead to the variables full of unnecessary information depending on the amount of data retrieved by the REST endpoint.

Attributes: More

Attribute	Description
Multi value	Determines if the user can select multiple values in this component.
Proposed values	Allows you to create a list of proposed values that are always presented at the top of the component's input list.
Proposed values only	If selected, the user can only select from the options defined in the Proposed values list.

Attributes: Validation

Attribute	Description
Required	Used to determine if the user must enter a value for this component.
Custom validations	List of additional validations you can apply.

Attributes: Documentation

Attribute	Description
Documentation	Allows you to explain concepts of the component's use for future reference.

User

The user component creates a drop-down list that allows you to select existing users. You can restrict the selection to one item, allow multiple items, or provide a proposed list of values.

Attributes: General

Attribute	Description
ID	The unique ID of the component.
Label	The label of the component.
Value	The binding for the component. Use an expression to bind the component to its value and specify where the value is saved. For example, use `{{myVariableName}}` to store the value of the component in a variable named myVariableName. Use prefixes to define the scope of the value, for example, root. for referencing the root case to store the value in or parent. to store the value in the parent work item of the current one. For example, `{{root.foo}}` stores the value in the root case using a variable named foo.
Default Value	If a Value is not set, such as on Initialization forms, then this value will be used.
Description	Adds a description to the component.
Ignored	Determines if the component should be hidden and the value excluded from any payload.
Visible	Determines whether the component is visible or hidden. You can also use this expression to only show or hide the component based on another component. For example, if this component is bound to a checkbox component, you can use this expression to show or hide this component based on the checkbox selection made by the user. This is enabled by default.
Enabled	Determines whether the component is enabled or disabled. This is enabled by default.

Attributes: Data source

Attribute	Description
Storage	Determines how the data retrieved by the REST endpoint should be stored in the variable. You can choose for the following options: - No value -: No part of the entry will be saved in the variable. ID: Only the ID of the selected entry will be saved in the variable. Full value: The whole object will be saved in the variable. This makes it possible to display other values of the selected element within the form as well. Storing the full value could lead to the variables full of unnecessary information depending on the amount of data retrieved by the REST endpoint.

Attribute

Description

Storage

Determines how the data retrieved by the REST endpoint should be stored in the variable.

You can choose for the following options:

- No value -: No part of the entry will be saved in the variable.
ID: Only the ID of the selected entry will be saved in the variable.
Full value: The whole object will be saved in the variable. This makes it possible to display other values of the selected element within the form as well.

Storing the full value could lead to the variables full of unnecessary information depending on the amount of data retrieved by the REST endpoint.

Attributes: More

Attribute	Description
Multi value	Determines if the user can select multiple values in this component.
Proposed values	Allows you to create a list of proposed values that are always presented at the top of the component's input list.
Proposed values only	If selected, the user can only select from the options defined in the Proposed values list.

Attributes: Validation

Attribute	Description
Required	Used to determine if the user must enter a value for this component.
Custom validations	List of additional validations you can apply.

Attributes: Documentation

Attribute	Description
Documentation	Allows you to explain concepts of the component's use for future reference.

Group

The group component creates a drop-down list that allows you to select existing groups. You can restrict the selection to one item, allow multiple items, or provide a proposed list of values.

Attributes: General

Attribute	Description
ID	The unique ID of the component.
Label	The label of the component.
Value	The binding for the component. Use an expression to bind the component to its value and specify where the value is saved. For example, use `{{myVariableName}}` to store the value of the component in a variable named myVariableName. Use prefixes to define the scope of the value, for example, root. for referencing the root case to store the value in or parent. to store the value in the parent work item of the current one. For example, `{{root.foo}}` stores the value in the root case using a variable named foo.
Default Value	If a Value is not set, such as on Initialization forms, then this value will be used.
Description	Adds a description to the component.
Ignored	Determines if the component should be hidden and the value excluded from any payload.
Visible	Determines whether the component is visible or hidden. You can also use this expression to only show or hide the component based on another component. For example, if this component is bound to a checkbox component, you can use this expression to show or hide this component based on the checkbox selection made by the user. This is enabled by default.
Enabled	Determines whether the component is enabled or disabled. This is enabled by default.

Attributes: Data source

Attribute	Description
Storage	Determines how the data retrieved by the REST endpoint should be stored in the variable. You can choose for the following options: - No value -: No part of the entry will be saved in the variable. ID: Only the ID of the selected entry will be saved in the variable. Full value: The whole object will be saved in the variable. This makes it possible to display other values of the selected element within the form as well. Storing the full value could lead to the variables full of unnecessary information depending on the amount of data retrieved by the REST endpoint.

Attribute

Description

Storage

Determines how the data retrieved by the REST endpoint should be stored in the variable.

You can choose for the following options:

- No value -: No part of the entry will be saved in the variable.
ID: Only the ID of the selected entry will be saved in the variable.
Full value: The whole object will be saved in the variable. This makes it possible to display other values of the selected element within the form as well.

Storing the full value could lead to the variables full of unnecessary information depending on the amount of data retrieved by the REST endpoint.

Attributes: More

Attribute	Description
Multi value	Determines if the user can select multiple values in this component.
Proposed values	Allows you to create a list of proposed values that are always presented at the top of the component's input list.
Proposed values only	If selected, the user can only select from the options defined in the Proposed values list.

Attributes: Validation

Attribute	Description
Required	Used to determine if the user must enter a value for this component.
Custom validations	List of additional validations you can apply.

Attributes: Documentation

Attribute	Description
Documentation	Allows you to explain concepts of the component's use for future reference.

Role

The role component creates a drop-down list that allows you to select existing roles. You can restrict the selection to one item, allow multiple items, or provide a proposed list of values.

Attributes: General

Attribute	Description
ID	The unique ID of the component.
Label	The label of the component.
Value	The binding for the component. Use an expression to bind the component to its value and specify where the value is saved. For example, use `{{myVariableName}}` to store the value of the component in a variable named myVariableName. Use prefixes to define the scope of the value, for example, root. for referencing the root case to store the value in or parent. to store the value in the parent work item of the current one. For example, `{{root.foo}}` stores the value in the root case using a variable named foo.
Default Value	If a Value is not set, such as on Initialization forms, then this value will be used.
Description	Adds a description to the component.
Ignored	Determines if the component should be hidden and the value excluded from any payload.
Visible	Determines whether the component is visible or hidden. You can also use this expression to only show or hide the component based on another component. For example, if this component is bound to a checkbox component, you can use this expression to show or hide this component based on the checkbox selection made by the user. This is enabled by default.
Enabled	Determines whether the component is enabled or disabled. This is enabled by default.

Attributes: Data source

Attribute	Description
Storage	Determines how the data retrieved by the REST endpoint should be stored in the variable. You can choose for the following options: - No value -: No part of the entry will be saved in the variable. ID: Only the ID of the selected entry will be saved in the variable. Full value: The whole object will be saved in the variable. This makes it possible to display other values of the selected element within the form as well. Storing the full value could lead to the variables full of unnecessary information depending on the amount of data retrieved by the REST endpoint.

Attribute

Description

Storage

Determines how the data retrieved by the REST endpoint should be stored in the variable.

You can choose for the following options:

- No value -: No part of the entry will be saved in the variable.
ID: Only the ID of the selected entry will be saved in the variable.
Full value: The whole object will be saved in the variable. This makes it possible to display other values of the selected element within the form as well.

Storing the full value could lead to the variables full of unnecessary information depending on the amount of data retrieved by the REST endpoint.

Attributes: More

Attribute	Description
Multi value	Determines if the user can select multiple values in this component.
Proposed values	Allows you to create a list of proposed values that are always presented at the top of the component's input list.
Proposed values only	If selected, the user can only select from the options defined in the Proposed values list.

Attributes: Validation

Attribute	Description
Required	Used to determine if the user must enter a value for this component.
Custom validations	List of additional validations you can apply.

Attributes: Documentation

Attribute	Description
Documentation	Allows you to explain concepts of the component's use for future reference.

Asset

The asset component creates a drop-down list that only allows you to select existing assets. You can restrict the selection to one item, allow multiple items, provide a proposed list of values, or restrict the selection to assets in certain domains, communities, of certain types, or with certain statuses.

Attributes: General

Attribute	Description
ID	The unique ID of the component.
Label	The label of the component.
Value	The binding for the component. Use an expression to bind the component to its value and specify where the value is saved. For example, use `{{myVariableName}}` to store the value of the component in a variable named myVariableName. Use prefixes to define the scope of the value, for example, root. for referencing the root case to store the value in or parent. to store the value in the parent work item of the current one. For example, `{{root.foo}}` stores the value in the root case using a variable named foo.
Default Value	If a Value is not set, such as on Initialization forms, then this value will be used.
Description	Adds a description to the component.
Ignored	Determines if the component should be hidden and the value excluded from any payload.
Visible	Determines whether the component is visible or hidden. You can also use this expression to only show or hide the component based on another component. For example, if this component is bound to a checkbox component, you can use this expression to show or hide this component based on the checkbox selection made by the user. This is enabled by default.
Enabled	Determines whether the component is enabled or disabled. This is enabled by default.

Attributes: Data source

Attribute	Description
Storage	Determines how the data retrieved by the REST endpoint should be stored in the variable. You can choose for the following options: - No value -: No part of the entry will be saved in the variable. ID: Only the ID of the selected entry will be saved in the variable. Full value: The whole object will be saved in the variable. This makes it possible to display other values of the selected element within the form as well. Storing the full value could lead to the variables full of unnecessary information depending on the amount of data retrieved by the REST endpoint.

Attribute

Description

Storage

Determines how the data retrieved by the REST endpoint should be stored in the variable.

You can choose for the following options:

- No value -: No part of the entry will be saved in the variable.
ID: Only the ID of the selected entry will be saved in the variable.
Full value: The whole object will be saved in the variable. This makes it possible to display other values of the selected element within the form as well.

Storing the full value could lead to the variables full of unnecessary information depending on the amount of data retrieved by the REST endpoint.

Attributes: Filters

Attribute	Description
Asset type IDs	Determines which assets are allowed as input for the component based on the asset types specified here. Only assets of the specified types are available.
Type inheritance	Determines if the selected values in Asset type IDs should include descendant types.
Status IDs	Determines which assets are allowed as input for the component based on the statuses specified here. Only assets with the specified statuses are available.
Community IDs	Determines which assets are allowed as input for the component based on the communities specified here. Only assets contained in the specified communities are available.
Domain IDs	Determines which assets are allowed as input for the component based on the domains specified here. Only assets contained in the specified domains are available.
Exclude meta	Whether to hide or show assets from meta domains, such as issues.

Attributes: More

Attribute	Description
Default from resource	Determines whether the property's default value is the current resource.
Multi value	Determines if the user can select multiple values in this component.
Proposed values	Allows you to create a list of proposed values that are always presented at the top of the component's input list.
Proposed values only	If selected, the user can only select from the options defined in the Proposed values list.

Attributes: Validation

Attribute	Description
Required	Used to determine if the user must enter a value for this component.
Custom validations	List of additional validations you can apply.

Attributes: Documentation

Attribute	Description
Documentation	Allows you to explain concepts of the component's use for future reference.

Domain

The domain component creates a drop-down list that allows you to select existing domains. You can restrict the selection to one item, allow multiple items, or provide a proposed list of values.

Attributes: General

Attribute	Description
ID	The unique ID of the component.
Label	The label of the component.
Value	The binding for the component. Use an expression to bind the component to its value and specify where the value is saved. For example, use `{{myVariableName}}` to store the value of the component in a variable named myVariableName. Use prefixes to define the scope of the value, for example, root. for referencing the root case to store the value in or parent. to store the value in the parent work item of the current one. For example, `{{root.foo}}` stores the value in the root case using a variable named foo.
Default Value	If a Value is not set, such as on Initialization forms, then this value will be used.
Description	Adds a description to the component.
Ignored	Determines if the component should be hidden and the value excluded from any payload.
Visible	Determines whether the component is visible or hidden. You can also use this expression to only show or hide the component based on another component. For example, if this component is bound to a checkbox component, you can use this expression to show or hide this component based on the checkbox selection made by the user. This is enabled by default.
Enabled	Determines whether the component is enabled or disabled. This is enabled by default.

Attributes: Data source

Attribute	Description
Storage	Determines how the data retrieved by the REST endpoint should be stored in the variable. You can choose for the following options: - No value -: No part of the entry will be saved in the variable. ID: Only the ID of the selected entry will be saved in the variable. Full value: The whole object will be saved in the variable. This makes it possible to display other values of the selected element within the form as well. Storing the full value could lead to the variables full of unnecessary information depending on the amount of data retrieved by the REST endpoint.

Attribute

Description

Storage

Determines how the data retrieved by the REST endpoint should be stored in the variable.

You can choose for the following options:

- No value -: No part of the entry will be saved in the variable.
ID: Only the ID of the selected entry will be saved in the variable.
Full value: The whole object will be saved in the variable. This makes it possible to display other values of the selected element within the form as well.

Storing the full value could lead to the variables full of unnecessary information depending on the amount of data retrieved by the REST endpoint.

Attributes: Filters

Attribute	Description
Community ID	Determines which domains are allowed as input for the component based on the communities specified here. Only domains contained in the specified communities are available.
Domain type ID	Determines the type of domains that are allowed as input for the component based on the domain type specified here. Only domains of the specified type are available.

Attributes: More

Attribute	Description
Default from resource	Determines whether the property's default value is the current resource.
Multi value	Determines if the user can select multiple values in this component.
Proposed values	Allows you to create a list of proposed values that are always presented at the top of the component's input list.
Proposed values only	If selected, the user can only select from the options defined in the Proposed values list.

Attributes: Validation

Attribute	Description
Required	Used to determine if the user must enter a value for this component.
Custom validations	List of additional validations you can apply.

Attributes: Documentation

Attribute	Description
Documentation	Allows you to explain concepts of the component's use for future reference.

Community

The community component creates a drop-down list that allows you to select existing communities. You can restrict the selection to one item, allow multiple items, or provide a proposed list of values.

Attributes: General

Attribute	Description
ID	The unique ID of the component.
Label	The label of the component.
Value	The binding for the component. Use an expression to bind the component to its value and specify where the value is saved. For example, use `{{myVariableName}}` to store the value of the component in a variable named myVariableName. Use prefixes to define the scope of the value, for example, root. for referencing the root case to store the value in or parent. to store the value in the parent work item of the current one. For example, `{{root.foo}}` stores the value in the root case using a variable named foo.
Default Value	If a Value is not set, such as on Initialization forms, then this value will be used.
Description	Adds a description to the component.
Ignored	Determines if the component should be hidden and the value excluded from any payload.
Visible	Determines whether the component is visible or hidden. You can also use this expression to only show or hide the component based on another component. For example, if this component is bound to a checkbox component, you can use this expression to show or hide this component based on the checkbox selection made by the user. This is enabled by default.
Enabled	Determines whether the component is enabled or disabled. This is enabled by default.

Attributes: Data source

Attribute

Description

Storage

Determines how the data retrieved by the REST endpoint should be stored in the variable.

You can choose for the following options:

- No value -: No part of the entry will be saved in the variable.
ID: Only the ID of the selected entry will be saved in the variable.
Full value: The whole object will be saved in the variable. This makes it possible to display other values of the selected element within the form as well.

Storing the full value could lead to the variables full of unnecessary information depending on the amount of data retrieved by the REST endpoint.

Attributes: More

Attribute	Description
Default from resource	Determines whether the property's default value is the current resource.
Multi value	Determines if the user can select multiple values in this component.
Proposed values	Allows you to create a list of proposed values that are always presented at the top of the component's input list.
Proposed values only	If selected, the user can only select from the options defined in the Proposed values list.

Attributes: Validation

Attribute	Description
Required	Used to determine if the user must enter a value for this component.
Custom validations	List of additional validations you can apply.

Attributes: Documentation

Attribute	Description
Documentation	Allows you to explain concepts of the component's use for future reference.

Role in community

The role in community component creates a drop-down list that allows you to select existing roles in communities. You can restrict the selection to one item, allow multiple items, or provide a proposed list of values.

This component is deprecated. We recommend you use a Subform container instead.

Attributes: General

Attribute	Description
ID	The unique ID of the component.
Label	The label of the component.
Value	The binding for the component. Use an expression to bind the component to its value and specify where the value is saved. For example, use `{{myVariableName}}` to store the value of the component in a variable named myVariableName. Use prefixes to define the scope of the value, for example, root. for referencing the root case to store the value in or parent. to store the value in the parent work item of the current one. For example, `{{root.foo}}` stores the value in the root case using a variable named foo.
Default Value	If a Value is not set, such as on Initialization forms, then this value will be used.
Description	Adds a description to the component.
Ignored	Determines if the component should be hidden and the value excluded from any payload.
Visible	Determines whether the component is visible or hidden. You can also use this expression to only show or hide the component based on another component. For example, if this component is bound to a checkbox component, you can use this expression to show or hide this component based on the checkbox selection made by the user. This is enabled by default.
Enabled	Determines whether the component is enabled or disabled. This is enabled by default.

Attributes: Data source

Attribute

Description

Storage

Determines how the data retrieved by the REST endpoint should be stored in the variable.

You can choose for the following options:

- No value -: No part of the entry will be saved in the variable.
ID: Only the ID of the selected entry will be saved in the variable.
Full value: The whole object will be saved in the variable. This makes it possible to display other values of the selected element within the form as well.

Storing the full value could lead to the variables full of unnecessary information depending on the amount of data retrieved by the REST endpoint.

Attributes: More

Attribute	Description
Default from resource	Determines whether the property's default value is the current resource.
Multi value	Determines if the user can select multiple values in this component.
Proposed values	Allows you to create a list of proposed values that are always presented at the top of the component's input list.
Proposed values only	If selected, the user can only select from the options defined in the Proposed values list.

Attributes: Validation

Attribute	Description
Required	Used to determine if the user must enter a value for this component.
Custom validations	List of additional validations you can apply.

Attributes: Documentation

Attribute	Description
Documentation	Allows you to explain concepts of the component's use for future reference.