---
title: "Create Record"
slug: "parser-create-record-prelude"
tags: ["Record"]
updated: 2024-10-23T09:02:36Z
published: 2024-10-23T09:02:36Z
canonical: "help.symphonysummitai.com/parser-create-record-prelude"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://help.symphonysummitai.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Create Record

## Prerequisite

Create User Defined Keys (UDKs) in select them as Keys under actions. To configure, refer to [Parse Content](https://help.symphonysummitai.com/summit-platform/docs/notification-parse-content).

## Configure Create Record

In the **Actions** stepper **Create Record** is used to create a Record from an email by mapping the appropriate fields of the transaction Table to the User Defined Keys(UDK) or System Defined Keys(SDK). A Record will be created based on the selected **Module** and selected **Table.**

The configuration fields present in the Create Record are as follows:

1. [Module](/summit-platform/docs/parser-create-record-prelude#module)
2. [Table](/summit-platform/docs/parser-create-record-prelude#table)
3. [Map Fields](/summit-platform/docs/parser-create-record-prelude#map-fields)
4. [Set Values](/summit-platform/docs/parser-create-record-prelude#set-values)
5. [Other Actions](/summit-platform/docs/parser-create-record-prelude#other-actions)

## Module

The system will parse the email and create a Record in the selected Module. Those Modules applicable to the selected Tenant will be displayed in the dropdown list.

Select **Module** from the dropdown list.

![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/notfication%20parser%20Module.png?sv=2026-02-06&spr=https&st=2026-10-31T13%3A38%3A10Z&se=2026-10-31T14%3A38%3A10Z&sr=c&sp=r&sig=QF4%2Fc%2F%2BJxO8OD%2FBpILBk3SQ5GbpEuC2227X%2FKuWmrI0%3D)

Figure: Notification Parser - Actions - Create Record

## Table

The **Table** dropdown will display all the Transaction Tables related to the selected **Module**. Only based on the selected **Table,** Field and Value can be configured for UDK or SDK in the next steps of the Create Record configuration.

> [!NOTE]
> Note
> 
> Click on the info icon to view the tooltip. Upon performing this action, the following message is displayed.
> 
> *Select the appropriate Table to create the record and define the Values for the Fields of the table*.

Select **Table** from the dropdown list, this will be used to obtain Field details while mapping to UDK/SDK and setting values against them.

![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/create record - Notification Parser Actions.png?sv=2026-02-06&spr=https&st=2026-10-31T13%3A38%3A10Z&se=2026-10-31T14%3A38%3A10Z&sr=c&sp=r&sig=QF4%2Fc%2F%2BJxO8OD%2FBpILBk3SQ5GbpEuC2227X%2FKuWmrI0%3D)

## Map Fields

Further, upon selecting Module and Table, Fields have to be mapped. Hence, Map Fields that are present under the **Create Record** are used in mapping the Field to the configured UDK or the (SDK).

**Example of mapping fields to UDK or SDK**

Let’s consider that, IT support team mailbox parser has a requirement to consider all emails from the registered users. If the email contains alert details such as Priority, Urgency, Impact, etc.., then the parser should map Fields to UDKs. Thereby, setting values against these UDKs, a Record is created reflecting the values against these fields, which fulfills the requirement. To achieve this, the Application Designer configures a Parser to run on an IT support Mailbox for all incoming emails with the following configuration:

1. The selected Module is **Incident** and the selected Table is **Manage Incidents** (The reason for selecting this Table is that, it fulfills the required fields for mapping).
2. There are certain Fields that are mandatory to be mapped according to the selected Table, these fields will be displayed with * an asterisk sign.

![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/map fields(4).png?sv=2026-02-06&spr=https&st=2026-10-31T13%3A38%3A10Z&se=2026-10-31T14%3A38%3A10Z&sr=c&sp=r&sig=QF4%2Fc%2F%2BJxO8OD%2FBpILBk3SQ5GbpEuC2227X%2FKuWmrI0%3D)
3. The application Designer must have defined those keys in the **Parse Content** stepper to map them here. Based on the selected Table these values differ.

![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/udk.png?sv=2026-02-06&spr=https&st=2026-10-31T13%3A38%3A10Z&se=2026-10-31T14%3A38%3A10Z&sr=c&sp=r&sig=QF4%2Fc%2F%2BJxO8OD%2FBpILBk3SQ5GbpEuC2227X%2FKuWmrI0%3D)
4. Now, let’s map all the Field values to their respective UDKs.

![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/field keys.png?sv=2026-02-06&spr=https&st=2026-10-31T13%3A38%3A10Z&se=2026-10-31T14%3A38%3A10Z&sr=c&sp=r&sig=QF4%2Fc%2F%2BJxO8OD%2FBpILBk3SQ5GbpEuC2227X%2FKuWmrI0%3D)
5. Having configured the mapping, let’s set the value against all the UDKs so that these values are assigned to the fields in the Record.
6. As part of Other Actions, select if the email should be considered as an attachment.

![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/other actions.png?sv=2026-02-06&spr=https&st=2026-10-31T13%3A38%3A10Z&se=2026-10-31T14%3A38%3A10Z&sr=c&sp=r&sig=QF4%2Fc%2F%2BJxO8OD%2FBpILBk3SQ5GbpEuC2227X%2FKuWmrI0%3D)

Upon configuring these, a record is be created successfully.

To map Field to Keys, perform the following steps:

1. Select **Field** from the dropdown list to map to the UDK. The values are displayed based on the selected Transaction Table.

![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/field notification parser(1).png?sv=2026-02-06&spr=https&st=2026-10-31T13%3A38%3A10Z&se=2026-10-31T14%3A38%3A10Z&sr=c&sp=r&sig=QF4%2Fc%2F%2BJxO8OD%2FBpILBk3SQ5GbpEuC2227X%2FKuWmrI0%3D)

> [!NOTE]
> Note
> 
> Based on the selected Table certain Fields are mandatory to Map. The Record will not be created if the values for these fields are not defined in the **Map Field** / **Set Values** section or if the default value is not set.
> 
> **A few examples of tables with the mandatory fields**
> 
> The following figure displays the mandatory Fields using * the (asterisk) sign for the **Cancel Incident** Table. If this Table is selected then the Mandatory value that is, **Cancellation Reason** must be selected as a Field.
> 
> ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/map fields - cancel incident table.png?sv=2026-02-06&spr=https&st=2026-10-31T13%3A38%3A10Z&se=2026-10-31T14%3A38%3A10Z&sr=c&sp=r&sig=QF4%2Fc%2F%2BJxO8OD%2FBpILBk3SQ5GbpEuC2227X%2FKuWmrI0%3D)
> 
> 
> 
> Similarly, in the following Table **Close Incident**, **Closure Reason** Field must be selected.
> 
> ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/close Incident - table.png?sv=2026-02-06&spr=https&st=2026-10-31T13%3A38%3A10Z&se=2026-10-31T14%3A38%3A10Z&sr=c&sp=r&sig=QF4%2Fc%2F%2BJxO8OD%2FBpILBk3SQ5GbpEuC2227X%2FKuWmrI0%3D)
2. Select **Key** from the Keys dropdown list. The dropdown will display all the SDKs and the UDKs. Either of them is selected and mapped as a Key for the selected **Field**. This Key will be used as a reference while setting values against them.

****User Defined Keys****

All the **User Defined Keys** (UDK) will be grouped under the UDK in the dropdown list.

![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/udk actions.png?sv=2026-02-06&spr=https&st=2026-10-31T13%3A38%3A10Z&se=2026-10-31T14%3A38%3A10Z&sr=c&sp=r&sig=QF4%2Fc%2F%2BJxO8OD%2FBpILBk3SQ5GbpEuC2227X%2FKuWmrI0%3D)

Figure: Actions - Map Field Keys The UDKs listed in the dropdown are the configured from the previous stepper **Parse Content**.

![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/user defined keys -free form.png?sv=2026-02-06&spr=https&st=2026-10-31T13%3A38%3A10Z&se=2026-10-31T14%3A38%3A10Z&sr=c&sp=r&sig=QF4%2Fc%2F%2BJxO8OD%2FBpILBk3SQ5GbpEuC2227X%2FKuWmrI0%3D)

Figure: Parse Content - User Defined Keys

****System Defined Keys****

All the default System Defined Keys (SDK) will be grouped under the SDK in the dropdown list.

Following are the default System Defined Keys for which certain configurations can be set:

  - **To Mail**: The system will consider the incoming mail to address, **To Mail** ID as the value for the **Field**.
  - **From Mail**: The system will consider the incoming mail to address, **From Mail** ID as the value for the **Field**.
  - **Subject**: The entire **Subject** from the incoming mail is considered as the **Field** value.
  - **Body**: The entire **Body** of the incoming mail is considered as the **Field** value.
  - **Attachment**: This option is used to map and parse the attachment of the incoming mail to the New Record.

There are pre-defined extensions allowed within the system, where the parser will parse with these extensions based on the selected attachment. User will not be able to restrict allowed extensions in Parser . All the extensions (33 extensions) that are supported in current application will be getting attached in Mail to Ticket. Following are the allowed extensions:

| 3gp | m4v/MP4 | docx | png | html | pdf |
| --- | --- | --- | --- | --- | --- |
| ppt | mp3 | ogg | eml | ogv | odt |
| wav | mp4/M4V | m4a | pptx | xlsx | msg |
| jpeg | zip | xls | pps | gif | doc |
| wmv | ppsx | txt | avi | mpg | jpg |
| webp | json | sql |  |

> [!NOTE]
> Note
> 
> All the .msg attachments will parse emails to ticket as .eml or .msg attachments.
  - **CC Email**: The **CC Email** functionality is to extract all the recipients in the emails and capture them in the created ticket. Provided they meet the following conditions:

Following are the edge case scenarios to be considered when CC Email is selected as Key:

**Edge Case Scenario 1: Requestor adds more users in the CC Field on the Reply Email**

Let’s consider the requestor adding more users to CC and To Recipients. When the Requestor replies to the original email by adding more CC users in the CC Field then these users are captured in the ticket.

    1. When the Requestor adds other users in the **Cc** or **To** Recipient fields on the original email, then these users are captured in the ticket.

![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/Req adds more Cc users.png?sv=2026-02-06&spr=https&st=2026-10-31T13%3A38%3A10Z&se=2026-10-31T14%3A38%3A10Z&sr=c&sp=r&sig=QF4%2Fc%2F%2BJxO8OD%2FBpILBk3SQ5GbpEuC2227X%2FKuWmrI0%3D)
    2. Added users are captured on the Ticket in respective **CC** and **To recipient** fields.

![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/to and cc in Incident(2).png?sv=2026-02-06&spr=https&st=2026-10-31T13%3A38%3A10Z&se=2026-10-31T14%3A38%3A10Z&sr=c&sp=r&sig=QF4%2Fc%2F%2BJxO8OD%2FBpILBk3SQ5GbpEuC2227X%2FKuWmrI0%3D)

**Edge Case Scenario 2: CC’ed user adds more users in the CC Field on the Reply Email**

Let’s consider the CC’ed user adding more users to CC and To Recipients.

When the CC’ed user replies to the original email by adding more users in the Cc Field then these users are not captured in the ticket.

    1. The Cc’ed user replies to the original email and adds more users in the **Cc** Field.

![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/cc user reply email(1).png?sv=2026-02-06&spr=https&st=2026-10-31T13%3A38%3A10Z&se=2026-10-31T14%3A38%3A10Z&sr=c&sp=r&sig=QF4%2Fc%2F%2BJxO8OD%2FBpILBk3SQ5GbpEuC2227X%2FKuWmrI0%3D)
    2. These additional Cc’ed users are not captured in the ticket.

![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/to and cc in Incident(6).png?sv=2026-02-06&spr=https&st=2026-10-31T13%3A38%3A10Z&se=2026-10-31T14%3A38%3A10Z&sr=c&sp=r&sig=QF4%2Fc%2F%2BJxO8OD%2FBpILBk3SQ5GbpEuC2227X%2FKuWmrI0%3D)

**Edge Case Scenario 3: CC’ed user forwards the original email to other users and these are not captured**

If the Cc’ed user forwards the original email by adding more users in the Cc and To Recipient Field, then they are not captured in the ticket.

    1. The Cc’ed user forwards the original email to other users.

![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/fw outlook message.png?sv=2026-02-06&spr=https&st=2026-10-31T13%3A38%3A10Z&se=2026-10-31T14%3A38%3A10Z&sr=c&sp=r&sig=QF4%2Fc%2F%2BJxO8OD%2FBpILBk3SQ5GbpEuC2227X%2FKuWmrI0%3D)
    2. These users added by the CC’ed user are not captured in the ticket.

![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/to and cc in Incident(5).png?sv=2026-02-06&spr=https&st=2026-10-31T13%3A38%3A10Z&se=2026-10-31T14%3A38%3A10Z&sr=c&sp=r&sig=QF4%2Fc%2F%2BJxO8OD%2FBpILBk3SQ5GbpEuC2227X%2FKuWmrI0%3D)

> [!NOTE]
> Note
> 
> The above use cases apply to both the **CC** and **To Recipients** fields.
    - All the **CC** Recipients must be registered users**.**
    - **Mailbox ID** should not be considered.

**Functionality of CC Email**

      1. Consider the following Email sent to the recipients mentioned in the **To** and **Cc** fields.

![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/Email(3).png?sv=2026-02-06&spr=https&st=2026-10-31T13%3A38%3A10Z&se=2026-10-31T14%3A38%3A10Z&sr=c&sp=r&sig=QF4%2Fc%2F%2BJxO8OD%2FBpILBk3SQ5GbpEuC2227X%2FKuWmrI0%3D)
      2. This Email is converted to a Ticket, only the **To** and **Cc** users are captured in the Ticket.

![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/to and cc in Incident.png?sv=2026-02-06&spr=https&st=2026-10-31T13%3A38%3A10Z&se=2026-10-31T14%3A38%3A10Z&sr=c&sp=r&sig=QF4%2Fc%2F%2BJxO8OD%2FBpILBk3SQ5GbpEuC2227X%2FKuWmrI0%3D)

**Requestor replies to the Email**

      1. When the Requestor replies to the same mail then the updated message is captured on the Messages tab in the Ticket.

![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/email re.png?sv=2026-02-06&spr=https&st=2026-10-31T13%3A38%3A10Z&se=2026-10-31T14%3A38%3A10Z&sr=c&sp=r&sig=QF4%2Fc%2F%2BJxO8OD%2FBpILBk3SQ5GbpEuC2227X%2FKuWmrI0%3D)
      2. Following is the figure that displays the update details in the Messages tab.

![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/updated message by to user.png?sv=2026-02-06&spr=https&st=2026-10-31T13%3A38%3A10Z&se=2026-10-31T14%3A38%3A10Z&sr=c&sp=r&sig=QF4%2Fc%2F%2BJxO8OD%2FBpILBk3SQ5GbpEuC2227X%2FKuWmrI0%3D)

**Cc’ed user or To user replies to Email**

      1. When the **Cc'ed** user or the **To** user replies to the Email then the update is captured in the ticket under the Messages tab. To achieve this, Cc'ed and To users should be added as eligible users under the **Update Record** tab.

![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/update record(14).png?sv=2026-02-06&spr=https&st=2026-10-31T13%3A38%3A10Z&se=2026-10-31T14%3A38%3A10Z&sr=c&sp=r&sig=QF4%2Fc%2F%2BJxO8OD%2FBpILBk3SQ5GbpEuC2227X%2FKuWmrI0%3D)
      2. Cc’ed user replies to the original Email.

![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/cc user reply.png?sv=2026-02-06&spr=https&st=2026-10-31T13%3A38%3A10Z&se=2026-10-31T14%3A38%3A10Z&sr=c&sp=r&sig=QF4%2Fc%2F%2BJxO8OD%2FBpILBk3SQ5GbpEuC2227X%2FKuWmrI0%3D)
      3. The update is captured in the ticket.

![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/updated message by CC user.png?sv=2026-02-06&spr=https&st=2026-10-31T13%3A38%3A10Z&se=2026-10-31T14%3A38%3A10Z&sr=c&sp=r&sig=QF4%2Fc%2F%2BJxO8OD%2FBpILBk3SQ5GbpEuC2227X%2FKuWmrI0%3D)
    1. You must first configure the **CC/To Recipient** Field on the **Form Designer** to utilize CC Email functionality.

![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/cc and to recipient on form.png?sv=2026-02-06&spr=https&st=2026-10-31T13%3A38%3A10Z&se=2026-10-31T14%3A38%3A10Z&sr=c&sp=r&sig=QF4%2Fc%2F%2BJxO8OD%2FBpILBk3SQ5GbpEuC2227X%2FKuWmrI0%3D)

Figure: CC and To Recipient fields in the Form Designer
    2. This will allow you to map the **CC** Field to the **CC Email** Key on the **Create Record** section of the Notification Parser. As the selected Table has a configured CC Field in the Form.

![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/map field to key (cc).png?sv=2026-02-06&spr=https&st=2026-10-31T13%3A38%3A10Z&se=2026-10-31T14%3A38%3A10Z&sr=c&sp=r&sig=QF4%2Fc%2F%2BJxO8OD%2FBpILBk3SQ5GbpEuC2227X%2FKuWmrI0%3D)

Figure: Create Record- CC Recipient to CC Email
    3. Thereby, upon capturing these recipients it is further used in sending Out Of Box(OOB) notifications using Business Rule Designer (BRD).

![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/brd(2).png?sv=2026-02-06&spr=https&st=2026-10-31T13%3A38%3A10Z&se=2026-10-31T14%3A38%3A10Z&sr=c&sp=r&sig=QF4%2Fc%2F%2BJxO8OD%2FBpILBk3SQ5GbpEuC2227X%2FKuWmrI0%3D)

Figure: configuration of CC Recipient in the BRD

After mapping the first **Field** to **Key**, an option to add a new Field Key set is displayed along with an option to delete the existing Field Key.

![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/add and del field key.png?sv=2026-02-06&spr=https&st=2026-10-31T13%3A38%3A10Z&se=2026-10-31T14%3A38%3A10Z&sr=c&sp=r&sig=QF4%2Fc%2F%2BJxO8OD%2FBpILBk3SQ5GbpEuC2227X%2FKuWmrI0%3D)

Figure: Create Record - Map Fields

| Icon | Description |
| --- | --- |
| ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/add icon(2).png?sv=2026-02-06&spr=https&st=2026-10-31T13%3A38%3A10Z&se=2026-10-31T14%3A38%3A10Z&sr=c&sp=r&sig=QF4%2Fc%2F%2BJxO8OD%2FBpILBk3SQ5GbpEuC2227X%2FKuWmrI0%3D) | Click the Add icon to insert a new Field Key set. |
| ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/delete icon..png?sv=2026-02-06&spr=https&st=2026-10-31T13%3A38%3A10Z&se=2026-10-31T14%3A38%3A10Z&sr=c&sp=r&sig=QF4%2Fc%2F%2BJxO8OD%2FBpILBk3SQ5GbpEuC2227X%2FKuWmrI0%3D) | Click the Delete icon to delete the configured Field Key. |

## Set Values

Define values against the mapped Field to the Keys. The values selected here against the fields will be auto-captured in the created record.

To define values, Expand **Set Values** and click **+ Add Filter Set.**

There are two parts under the Set Values section such as:

- [Conditions](/summit-platform/docs/createrecord#conditions)
- [Values](/summit-platform/docs/createrecord#values)

### Conditions

Multiple conditions can be created and grouped as one. Single or a Group of conditions can be mapped to a Field and Value. This feature will eliminate the use of creating multiple parsers to map different conditions to different fields and values.

The Condition part will have three columns such as:

- **User Defined Keys**, that is dropdown containing defined UDKs and default SDKs.
- **Operator** that acts as a logical connection between UDK and Value, based on the selected UDK field operator list is populated.
- **Values** as Textbox for mapping the desired values from the email.

Apart from these the conditions can be defined using AND/OR operators and multiple conditions are added using the + add icon and conditions can be deleted by clicking the – delete icon.

![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/conditions - set value.png?sv=2026-02-06&spr=https&st=2026-10-31T13%3A38%3A10Z&se=2026-10-31T14%3A38%3A10Z&sr=c&sp=r&sig=QF4%2Fc%2F%2BJxO8OD%2FBpILBk3SQ5GbpEuC2227X%2FKuWmrI0%3D)Figure: Create Record - Set Values

### Values

Values are another part of the Set Value section. Values will have two columns Fields and Value with the option to add multiple rows of the same.

- [Field](/summit-platform/docs/createrecord#field)
- [Value](/summit-platform/docs/createrecord#value)

#### Field

The dropdown will display all the Fields available for the selected Table.

#### Value

The dropdown will display all the values configured for the selected Field as per the table. The selected values will be displayed in their respective Fields once the record is created.

Example: If the field is selected as Impact, then the values displayed in the dropdown will be Low, Medium, and High. If High is selected as the Value. The impact field in the record details page will display High as its value when the record gets created.

![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/value - set value.png?sv=2026-02-06&spr=https&st=2026-10-31T13%3A38%3A10Z&se=2026-10-31T14%3A38%3A10Z&sr=c&sp=r&sig=QF4%2Fc%2F%2BJxO8OD%2FBpILBk3SQ5GbpEuC2227X%2FKuWmrI0%3D)Figure: Actions - Set Values

Upon adding Condition and Value, click **Add Record**. Added condition is represented using an **ID**, click the ID hyperlink to edit the configuration of Set Value. Clicking the delete icon will delete the action.

![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/added condition and value.png?sv=2026-02-06&spr=https&st=2026-10-31T13%3A38%3A10Z&se=2026-10-31T14%3A38%3A10Z&sr=c&sp=r&sig=QF4%2Fc%2F%2BJxO8OD%2FBpILBk3SQ5GbpEuC2227X%2FKuWmrI0%3D)Figure: Create Record - Set Values

## Other Actions

The Other Actions is a sub-section present under the Create Record option.

An option to select the entire mail as an attachment with a **Yes** or **No** option is displayed.

![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/other Actions - consider the email as attachment.png?sv=2026-02-06&spr=https&st=2026-10-31T13%3A38%3A10Z&se=2026-10-31T14%3A38%3A10Z&sr=c&sp=r&sig=QF4%2Fc%2F%2BJxO8OD%2FBpILBk3SQ5GbpEuC2227X%2FKuWmrI0%3D)Figure: Other Actions

Tenant is a platform component that is created inside the Sub Domain to leverage the independent functionality of a department along with data privacy.

An interface or tool used to create, manage, and edit business rules within a system