/
Common Attributes

Common Attributes

Owned by Content Writers
Mar 20, 2025

Merge Text

Merge text is a key feature of the noKodr application, allowing users to display and use the field values. Depending on the data type, users can perform mathematical operations on these fields.

For example, if you want to display a calculated total price based on the quantity and unit price entered by the user on a sales order form, and you wish to dynamically showcase this on the UI without saving the record in the database, you can achieve this using the UI fields in noKodr.

After selecting merge text, you can see several options such as:

Merge text popup.png
Merge Text

Attribute Name

Description

Attribute Name

Description

Source Type

In this option, you can select various sources from which you want to display values.

Value

The available options will change depending on the selected source type. For example, if you choose "Static" as the source, you can provide a fixed static value.

Merge Field Expression

The selected field from the source will be displayed in a merge format. For instance, the first name field from the contact model will appear as: {model:contact.FirstName}.

Message Body

In this option, You can add multiple values to form your final UI merge text.

For example, merge fields include {model:contact.FirstName},{model:contact.LastName} will eventually display the contact's first name and last name next to each other.

Filter

This section allows to add filter conditions to retrieve specific set of values such as records. This includes some attributes which needs to be added and those are as follows.

Filters.png
Filters

Attribute Name

Description

Attribute Name

Description

Destination Type

This option allows users to select the destination type, specifying the value that needs to be compared in a condition.

For example, If the destination type is set to "Account Name," you can compare the account name against different values. For instance, you can set a condition to show or fetch records whenever the account name is "Enzigma."

Destination Fields

This option changes based on the selected destination type. If "Fields" is selected as the destination type, only object fields will be displayed. Conversely, if "User" is selected, fields related to the current logged-in user will be shown for comparison.

Operator

This displays a list of operators that can be used to add conditions or compare two values.

Source Type

This option allows users to select the source type, specifying from which source the values need to be compared in the condition.

Value

This option changes based on the selected source type. For example, if "Current User" is selected as the source type, fields related to the logged-in user will be displayed for comparison.

For example, To filter account records with the matching name "Enzigma"

  • Destination Type Selected: Field

  • Destination Field: Account Name

  • Operator: Equals

  • Value Source Type: Static

  • Value Provided: "Enzigma"

Destination Type

In noKodr, the Destination Type refers to the entity whose value you want to use for further processing or comparison when filtering records. Various destination types are available to provide flexibility in defining conditions and workflows.

Destination Types and Their Usage

  1. User

    • Description: Allows selection of user-related field values for comparison or sending further for processing.

    • Example: Compare the current logged-in user's role to filter records that match specific criteria (e.g., show records only for users with the "Admin" role).

  2. Instance

    • Description: Enables selection of instance details such as name, ID, or other metadata for comparison or processing.

    • Example: Filter records based on instance names like "Production" or "Development."

  3. Field

    • Description: Allows selection of object field values for comparison or sending further for processing.

    • Example: Compare the "Account Name" field with a specific value (e.g., “Enzigma") to fetch matching records.

  4. Static

    • Description: Provides steady, predefined static text values for comparison or processing.

    • Example: Use a static value like "Active" to filter records where the status equals "Active."

  5. Variable

    • Description: Enables the use of variable values for comparison or processing, offering dynamic flexibility.

    • Example: Compare a runtime variable like current_date to filter records created on that date.

  6. Model

    • Description: Allows selection of model data for comparison or processing, commonly used in layout designing.

    • Example: Use model data like "Product Specifications" to dynamically filter products based on attributes such as size or color.

Source Type

In noKodr, the Source Type refers to the origin or entity from which values are retrieved for further processing or comparison when filtering records. This feature provides flexibility in defining conditions and workflows by allowing users to select different sources based on their requirements.

Available Source Types and Their Usage

  1. Current User

    • Description: Fetches values from the currently logged-in user's fields.

    • Example: Compare the logged-in user's role (e.g., "Admin") to filter records accessible only to admins.

  2. Static Value

    • Description: Uses a fixed, predefined value for comparison.

    • Example: Use a static value like "Active" to filter records where the status equals "Active."

  3. Variable

    • Description: Retrieves dynamic values stored in variables during runtime.

    • Example: Compare a runtime variable like current_date to filter records created on that date.

  4. Model Data

    • Description: Fetches data from models, which can represent complex relationships or layouts. Commonly used in layout designing.

    • Example: Use model data such as "Product Specifications" to dynamically filter products based on attributes like size or color.

  5. Local Storage

    • Description: Retrieves data stored in the browser's local storage, allowing access to larger amounts of persistent client-side data.

    • Example: Use a value stored in local storage (e.g., user preferences) to filter records based on user-selected themes.

  6. Cookies

    • Description: Accesses small pieces of data stored in cookies, which can be sent with HTTP requests.

    • Example: Compare a session identifier stored in cookies to manage user sessions and filter records accordingly.

  7. NULL

    • Description: Represents a null value to compare against in conditions.

    • Example: Use this source type to filter records where a specific field is null, such as checking if an optional field has not been filled out.

  8. Blank

    • Description: Represents an empty or blank value that can be used for comparison.

    • Example: Filter records where a specific field is blank, such as checking if a description field has not been provided.

For example, To filter account records created on the current date:

  • Destination Type: Field

  • Field Selected: Created Date

  • Operator: Equals

  • Value Source Type: Variable

  • Value Provided: current_date - Stores current date

 

Related content