Overview

The File component in noKodr allows users to upload and store various types of files directly within Salesforce objects. This functionality supports a wide range of file formats, including images, PDFs, Word documents, videos, XML files, and JSON data.

For example, In a Salesforce application for project management, the File component might be used to attach project-related documents, such as project plans (PDFs), design drafts (images), and meeting notes (Word documents) to the corresponding project records. This ensures that all project-related files are readily available and linked to the relevant records, facilitating better organization and collaboration.

Note: Here, users can upload one multiple files at a time.

Attributes:

Attributes are the options available for each component, allowing you to customize its appearance and functionality. They help you tailor the look and behavior of your components to fit your needs.

Basic:

Attribute Name	Description
Component Size	This allows users to modify the size of a specific component according to the grid size of layout. This feature allows for flexible customization, enabling users to resize components to fit their specific needs within the defined grid structure. For example, If the layout grid size is 3 then layout is divided into 3 sections then you can changes the components size between 1 to 3.
Label	Here, you can choose the label name from various source types, including static values, variables, or models. Reference: Label source Type
Object Name	Here, users can select the object from a list of available options.
Parent Id	Here, users can add the parent ID from various source types. Reference: Source Type
File Name	Here, users can manually enter a file name and also choose from various source types. Reference: Source Type
Storage Profile	Here, users can select the storage profile, choosing between a private profile or a public profile.
Accepts	Here, users can multi-select files in various formats, including PDF, TXT, DOC, DOCX, PPT, PPTX, XL, XLS, JPG, JPEG, PNG, GIF, SVG, MP3, WAV, MP4, AVI, ZIP, TAR, CSV, XML, JSON, HTML, and HTM.
Max Size (kb)	Here, users can set the maximum file size (in KB) for uploads.
No Versioning	If the "No Versioning" checkbox is marked as true, you cannot create additional versions of the file.
Can Update	If the "Can Update" checkbox is marked as true, you can update the uploaded file.
Can Delete	If the "Can Delete" checkbox is marked as true, you can delete the uploaded file.

Base UI:

Attribute Name	Description
Padding Location	"Padding Location" typically refers to the configuration of spacing around elements
Padding Size	"Padding Size" refers to the amount of space added inside an element, between the element's content and its border or edge.
Margin Location	"Margin Location" refers to the spacing around the outside edge of an element
Margin Size	"Margin Size" refers to the amount of space around the outside edges of an element,
Style	It is used to apply custom styles to section, such as color, font, size, and more. It allows you to define the appearance of a component by specifying CSS properties directly within the attribute.
Classes	It is used to apply SLDS classes to section, if needed.

UI State:

Attribute Name

Description

Visibility Type

It determines whether a component is visible on the layout. It offers the following visibility types:

Always: The component will always be visible.
Conditional: The component's visibility is determined based on specific criteria, which can make it either visible or hidden as needed.
You can explore more about Visibility Type here.

Reference: Conditional Visibility

Label Source Type:

Label Source Type Attribute	Description
Model (Salesforce Object)	From this source, users can select a Model (Salesforce Object) field to be displayed . Reference: Models
Variable	Here, users can select the label name from variables such as Is Disabled, Is Read only, or Is Visible. For more details Reference: Variables
Merge Field Expression	Merge Field Expression displays the value selected from the chosen value source.
Message Body	Inside the message body, user also can add the values manually.

Conditional Visibility Type:

Attributes Name	Description
Destination Type	Users can select the destination type where the visibility criteria must be applied. Reference: Destination Type
Operator	Here, users can select different operators to add filters. Reference: Filter Operator.
Source Type	Here, you can select the source type from various sources.
Value	Here user can select the value from different Source Type. Reference: Merge Text

Destination Type

Destination Type	Description
Model	From this source, users can select a Model field to be displayed as the destination type.
Variable	Here, users can select the destination type from variables such as Record ID, Is Disabled, Is Read only, or Is Visible.
User	Here, you can choose the label from user fields such as First Name, Last Name, Email, Name, Phone, or Session ID.
Record	It enables to choose record fields as destination type.
Device	It enables user to decide whether the action will be visible on the specific device type or not. Devices supported: Mobile Desktop Tablet

Conditional Disability Type:

Attributes Name	Description
Destination Type	Users can select the destination type from various sources. Reference: Destination Type
Operator	Here, users can select different operators to add filters. Reference: Filter Operator.
Source Type	Here, you can select the source type from various sources. Reference: Available Sources.
Value	Here user can select the value from different Source Type. Reference: Merge Text

Conditional Read Only:

Attribute Name

Description

Read Only Type

It specifies whether a component can be edited by users. It offers the following options:

Never: The component will always be editable at any time.
Always: The component will never be editable.
Conditional: The component's editability is determined based on specific criteria, which can make it either editable or read only as needed.

Add Condition & Group Condition

Condition	Description
Add Condition	The Add Condition feature allows users to define multiple criteria that must be met for a validation rule to trigger. This feature is used to create complex logic by combining different conditions that Salesforce evaluates before allowing a record to be saved.
Add Group Condition	The Add Group Condition feature allows users to group multiple conditions together, creating complex logic that involves different sets of criteria. This feature is particularly useful when combining conditions that should be evaluated as a unit (logical OR within a group) or when nesting conditions for more advanced logic.

Filter Operator:

Note: Before using the filter criteria, it's important to understand which filter operators are supported for each field type

Filters Attributes:

Filter Operators

Operator	Supported Field Types	Description
Equal	Number, Currency, Date, Text, Boolean, Picklist	The equal operator is used to compare two values or expressions. It is used to compare numbers, strings, Boolean values, variables, objects, etc. The result is TRUE if the expressions are equal otherwise it’s FALSE
Contains	Text, Picklist	The contains operator returns TRUE if the value on the left contains the value on the right, and otherwise FALSE
Starts With	Text, Picklist	It returns TRUE if a string or number starts with the specified character otherwise it returns FALSE.
Ends With	Text, Picklist	It returns TRUE if a string or number ends with the specified character otherwise it returns FALSE
In	Text, Picklist	IN operator allows you to easily test if the expression matches any value in the list of values. Determines whether the value of an expression is equal to any of several values in a specified list.

Events:

Events are essentially the automation of invoking the component's actions.
Here, we have onload event, query, upload, download, delete actions are available for this components.

Icon Events	Description
onload	This event action is triggered when the File component is loaded.
upload	This event action is triggered when the File is uploaded.
download	This event action is triggered when the File is downloaded.
delete	This event action is triggered when the File is deleted.

Below here is the onload event workflow action.

Note: Similarly you can create event action for query, upload, download, delete.

on load Event:

In the image below, you can select the created workflows.

Note: "You need to create a workflow for selecting from this list.

For more information about Workflow check this out.

Reference: Workflow

onload Events:

We have an onload event that runs when the component is loaded

For example, when a form is loaded, you can choose fields to be prepopulated by mapping field values using input mapping at the time the form component is loaded.

Input Mapping

Input Mapping: "Whenever an event is triggered and you want to pass data to destinations such as models, variables, or components, you can use input mapping to achieve that.

Files