Overview

In noKodr, Events are used to facilitate communication between different layouts. Users can create multiple events tailored to specific scenarios, allowing one layout to trigger actions or send data to another layout. This feature enables seamless interaction and coordination between layouts, enhancing the overall functionality of the application.

Note: You may encounter precreated events within the system. These prebuilt events are locked, meaning they cannot be modified or deleted. They are provided as reference points to assist you in creating new events. You can use these precreated events as templates, making necessary modifications to fit your requirements.

Key Features of Events

Triggering Actions: Events can be set to trigger actions like updating fields, displaying messages, or navigating between layouts when a specific user action occurs, such as a button click or form submission.
Workflow Integration: Events can be integrated with workflows to automate complex processes, like sending notifications, updating records, or executing logic based on user input or system changes.
Inter-Component Communication: Events enable different layouts to communicate and react to each other, such as updating one component based on changes in another.

Event Config

Field name	Description
Label	A user-friendly name for the variable, used for easy identification within the application.
Name	The unique identifier for the variable, typically used in code or within merge text.
Event Variables	By clicking on the '+' button in noKodr, you can pass values or data through events into another layout. Reference: Event Variable Config

Event Variable Config

Field Name	Description
Label	A user-friendly name for the variable, used for easy identification within the application.
Name	The unique identifier for the variable, it typically used in code or within merge text.
Field Type	Specifies the type of data the variable will hold (e.g., text, number, date,etc). Reference: Field Types
Default Value	The initial value assigned to the variable, applied if no other value is provided.
Required	Checkbox that determines if the variable must be filled before proceeding.
Is Array	Checkbox that indicates whether the variable can store multiple values (an array) instead of just one.

For example,

Use Case: Automatically Updating a Related Layout

Scenario: Suppose you have two layouts in noKodr - a Customer Details layout and an Order Summary layout. When a user updates the customer's shipping address in the Customer Details layout, you want the Order Summary layout to automatically refresh and display the updated shipping address.

Solution:

Create an Event: Set up an event in the Customer Details layout that triggers when the shipping address field is updated.
Pass Data: Use the + button to pass the updated shipping address data through the event to the Order Summary layout.
Update the Layout: The event triggers the Order Summary layout to refresh, ensuring that the new shipping address is displayed without requiring manual updates.

This use case demonstrates how events in noKodr can be used to synchronize data between layouts, improving workflow efficiency and ensuring consistency across different parts of the application.