Variables

Introduction

Variables are a set of tokens used to identify a value in the current context. They can be used in scenarios such as configuring block data scopes, field default values, linkage rules, and workflows.

Currently Supported Variables

Current User

Represents the data of the currently logged-in user.

Current Role

Represents the role identifier (role name) of the currently logged-in user.

Current Form

The values of the current form, used only in form blocks. Use cases include:

• Linkage rules for the current form
• Default values for form fields (only effective when adding new data)
• Data scope settings for association fields
• Field value assignment configuration for submit actions

Linkage rules for the current form

Default values for form fields (add form only)

<!--  -->

Data scope settings for association fields

Used to dynamically filter the options of a downstream field based on an upstream field, ensuring accurate data entry.

Example:

1. The user selects a value for the Owner field.
2. The system automatically filters the options for the Account field based on the selected Owner's userName.

<!--  --> <!-- #### Field value assignment configuration for submit actions  --> <!-- ### Current Object Currently used only for field configuration in sub-forms and sub-tables within a form block, representing the value of each item: - Default value for sub-fields - Data scope for sub-association fields #### Default value for sub-fields  #### Data scope for sub-association fields  --> <!-- ### Parent Object Similar to "Current Object", it represents the parent object of the current object. Supported in NocoBase v1.3.34-beta and above. -->

Current Record

A record refers to a row in a collection, where each row represents a single record. The "Current Record" variable is available in the linkage rules for row actions of display-type blocks.

Example: Disable the delete button for documents that are "Paid".

Current Popup Record

Popup actions play a very important role in NocoBase interface configuration.

• Popup for row actions: Each popup has a "Current Popup Record" variable, representing the current row record.
• Popup for association fields: Each popup has a "Current Popup Record" variable, representing the currently clicked association record.

Blocks within a popup can use the "Current Popup Record" variable. Related use cases include:

• Configuring the data scope of a block
• Configuring the data scope of an association field
• Configuring default values for fields (in a form for adding new data)
• Configuring linkage rules for actions

<!-- #### Configuring the data scope of a block  #### Configuring the data scope of an association field  #### Configuring default values for fields (in a form for adding new data)  #### Configuring linkage rules for actions  <!-- #### Field value assignment configuration for form submit actions  --> <!-- ### Selected Table Records Currently used only for the default value of form fields in the Add record action of a table block #### Default value of form fields for the Add record action --> <!-- ### Parent Record (Deprecated) Used only in association blocks, representing the source record of the association data. :::warning "Parent Record" is deprecated. It is recommended to use the equivalent "Current Popup Record" instead. ::: <!-- ### Date Variables Date variables are dynamically parsable date placeholders that can be used in the system to set data scopes for blocks, data scopes for association fields, date conditions in action linkage rules, and default values for date fields. The parsing method of date variables varies depending on the use case: in assignment scenarios (such as setting default values), they are parsed into specific moments in time; in filtering scenarios (such as data scope conditions), they are parsed into time period ranges to support more flexible filtering. #### Filtering Scenarios Related use cases include: - Setting date field conditions for block data scopes - Setting date field conditions for association field data scopes - Setting date field conditions for action linkage rules  Related variables include: - Current time - Yesterday - Today - Tomorrow - Last week - This week - Next week - Last month - This month - Next month - Last quarter - This quarter - Next quarter - Last year - This year - Next year - Last 7 days - Next 7 days - Last 30 days - Next 30 days - Last 90 days - Next 90 days #### Assignment Scenarios In assignment scenarios, the same date variable is automatically parsed into different formats based on the type of the target field. For example, when using Today to assign a value to different types of date fields: - For Timestamp fields and DateTime with timezone fields, the variable is parsed into a complete UTC time string, such as 2024-04-20T16:00:00.000Z, which includes timezone information and is suitable for cross-timezone synchronization needs. - For DateTime without timezone fields, the variable is parsed into a local time format string, such as 2025-04-21 00:00:00, without timezone information, which is more suitable for local business logic processing. - For DateOnly fields, the variable is parsed into a pure date string, such as 2025-04-21, containing only the year, month, and day, with no time part. The system intelligently parses the variable based on the field type to ensure the correct format during assignment, avoiding data errors or exceptions caused by type mismatches.  Related use cases include: - Setting default values for date fields in form blocks - Setting the value attribute for date fields in linkage rules - Assigning values to date fields in submit buttons Related variables include: - Now - Yesterday - Today - Tomorrow -->

URL Query Parameters

This variable represents the query parameters in the current page URL. It is only available when a query string exists in the page URL. It is more convenient to use it with the Link action.

API token

The value of this variable is a string, which is a credential for accessing the NocoBase API. It can be used to verify the user's identity.

Current Device Type

Example: Do not display the "Print template" action on non-desktop devices.