Overview

In noKodr, a Workflow functions as a process builder for your application, enabling you to design and implement business automation according to your specific needs.
Workflows allow you to construct complex automation sequences by connecting various actions in a specific order or in sequence.
A Workflow can contain multiple actions, such as Push, Pop, Toaster, Show Spinner, and others.

Workflow Actions:

Workflow Actions are sub-grouped under the following categories:

Categories	Description
Logic	This category includes actions that follow set of rules and steps.
Communication	This category includes actions for communication.
Data	This category provides actions for performing CRUD (Create, Read, Update, Delete) operations.
Layout	This category includes actions for managing layouts, such as handling events and displaying screens(Modal). Note: In noKodr, a Modal is referred to as a screen.
Workflow	This category allows for the inclusion of another workflow as a sub-flow within the current workflow.
UI	UI-specific actions, such as displaying a message, spinner, or prompt, are included in this category.

Logic Actions

Logic Action	Description	Reference
Assignment	It consists of the basic operation of assigning a value to a variable. For example, `x = 10` assigns the value `10` to the variable `x`.	Click Here to Explore more
Decision	It consists of conditional statements that allow the program to execute different blocks of code based on whether a specific condition is true or false. Examples include `if`, `else if`, and `else` statements.	Click Here to Explore more
Switch	It offers an alternative way to handle multiple branching scenarios. It tests a variable for equality against a list of values and executes a corresponding block of code based on the matching value.	Click Here to Explore more
Loop	It is used to repeat a workflow multiple times until a specified condition is met. Common types of loops include `for`, `while`, and `do-while` loops.	Click Here to Explore more
Validate	It involves checking whether data meets certain requirements or constraints, such as correct data type, length, format, or range.	Click Here to Explore more
Logs	It involves recording events, messages, or data during program execution. Logs are valuable for debugging, monitoring, and analyzing software behavior.	Click Here to Explore more
Filter	It involves selecting a subset of items from a larger set based on specific criteria or conditions, such as filtering a list of numbers to include only even numbers.	Click Here to Explore more
Map	It transforms each element of a collection based on a Key value. It applies the function to each element and generates a new collection with the transformed values.	Click Here to Explore more
Code	It refers to the instructions written in a programming language that define the behavior of a software application.	Click Here to Explore more
Consume License	It refers to the process of using or activating a software license to gain access to a specific software product or service.	Click Here to Explore more
Check License	It typically involves verifying whether a user or system is authorized to access or use a software product. This may involve validating license keys, checking subscription status, or verifying user permissions.	Click Here to Explore more

Communication Actions

Communication Action	Description	Reference
Notify	It is used to alert users or relevant stakeholders about specific events, updates, or tasks within the process. These notifications can be delivered through various channels such as email, SMS, in-app messages, or push notifications. For example: A workflow management system might notify team members when a new task is assigned or when a deadline is approaching.	Click Here to Explore more
Bulk Notify	It is useful for informing a large group of recipients about the same event or update. Instead of sending individual notifications to each recipient, bulk notifications allow you to send a single message to multiple recipients simultaneously.	Click Here to Explore more
API	It is essential in workflows, enabling different software systems or services to communicate with each other. In workflow automation, APIs facilitate the integration of various tools, platforms, or applications, allowing them to exchange data and trigger actions seamlessly. For example: An e-commerce workflow might use APIs to retrieve product information from a database, process payments through a payment gateway, or update inventory levels in real time.	Click Here to Explore more
Rest API	It adheres to REST architecture principles and are commonly used to build web services that enable clients to interact with server resources using standard HTTP methods. In workflows, REST APIs can be used to access and manipulate data stored on remote servers or cloud services. For example: A workflow might use a REST API to retrieve weather information from a third-party service, fetch data from a social media platform, or perform operations on a cloud-based storage system.	Click Here to Explore more

Data Actions

Data Action	Description	Reference
Query Records	It retrieves specific data records from a database or data source based on predefined criteria or conditions. In workflows, this action is used to gather information for further processing or analysis. For example: In a marketing campaign workflow, you might query customer records to identify those who have shown interest in a specific product category but haven’t made a purchase, enabling targeted follow-up actions.	Click Here to Explore more
Create Records	It involves adding new data entries to a database or data repository. In workflows, this is typically used to capture and store information generated during the process execution. For instance, For example: In a job application workflow, new applicant profiles could be created and added to the HR database when individuals submit their resumes online.	Click Here to Explore more
Update Records	It involves modifying existing data entries in a database or data source. In workflows, this action is often used to reflect changes or updates to information over time. For example: In a customer support workflow, you might update a support ticket's status and notes as the issue is resolved and additional details are logged.	Click Here to Explore more
Delete Records	It involves removing data entries from a database or data repository. In workflows, this action is used to eliminate outdated, redundant, or unnecessary information. For example: In a subscription management workflow, expired subscriptions could be deleted from the database to keep the records up-to-date and accurate.	Click Here to Explore more

Layout Actions

Action	Description	Reference
Emit Event	It facilitates communication between two layouts or workflows by emitting events from the source layout. This action is triggered by events such as a button click or any other user interaction. To use this feature, events must be created on the layouts. Through the `Emit Event`, you can pass output parameters to other layouts or workflows.	Click Here to Explore more
Subscribe Event	It is used to listen to an event emitted by a source layout or workflow, enabling communication between them. To subscribe to an event, you need to select the relevant layout and event. You can also assign a workflow that will fire or emit the event. Through the `Subscribe Event`, you can capture input parameters passed from the emitting event.	Click Here to Explore more
Push Modal	The `Push Modal` action opens a modal container within the application layout. This modal can contain various fields and is typically used for creating new records. The modal is created on the application layout and can be customized according to the application's requirements.	Click Here to Explore more
Push Modal and Wait	The `Push Modal and Wait` action is used to open a layout in a modal (pop-up) to perform actions such as creating or updating a record or viewing details. This action pauses the workflow's next steps until the modal is closed (via `Pop Modal`). The modal can be configured with different sizes, padding, and headers, and parameters can be passed through input fields.	Click Here to Explore more
Pop Modal	The `Pop Modal` action is used to close a modal and return to the previous layout after saving or canceling a record. This action is commonly used after operations like form submission or canceling an edit.	Click Here to Explore more
Redirect	The `Redirect` action allows users to be redirected to another layout within the application or to any external URL. This action can be configured within a workflow to navigate users based on certain conditions or events.	Click Here to Explore more
Un Subscribe Event	The `Unsubscribe Event` action is used to stop listening to a particular event. This action effectively halts any further communication or responses triggered by the previously subscribed event.	Click Here to Explore more

Workflow Action

Workflow Action	Description	Reference
Workflow	It basically allows to use workflow created earlier to use as a sub-flow, same like salesforce sub-flows.	Click Here to Explore more

UI Actions

UI Action	Description	Reference
Toaster	It displays a brief notification or message to the user, typically used to provide feedback or inform the user about the success or failure of an action. The toaster message usually appears as a pop-up in a corner of the screen and disappears automatically after a short period.	Click Here to Explore more
Show Spinner	It displays a loading spinner or indicator on the screen to inform the user that a process is ongoing. This action is commonly used during data retrieval, form submission, or other operations that may take some time to complete, signaling to the user that they should wait.	Click Here to Explore more
Hide Spinner	It removes the loading spinner or indicator from the screen, signaling that the ongoing process has completed. This action is typically paired with the `Show Spinner` action to create a smooth user experience during loading operations.	Click Here to Explore more
Prompt	It displays a dialog box that requests input or confirmation from the user. This action can be used to ask for user consent, confirm a decision, or collect specific information before proceeding with a workflow or action.	Click Here to Explore more
Component Action	It allows you to trigger specific behaviors or functions within a component. These actions are typically used to interact with or manipulate UI components, such as buttons, forms, or custom widgets, within a layout or workflow. They enable dynamic and interactive experiences within the application by responding to user input or other triggers.	Click Here to Explore more

Create Workflow Modal

Workflow Creation Field

Description

Label

A user-friendly name for the workflow, used for easy identification within the application.

Name

The unique identifier for the workflow, typically used in code or within merge text.

Type

Basically there are two types of workflows in noKodr:

Business: Business Workflows include all actions mentioned above.
Validation: Validation workflows include only Logic, Data and Communication actions. They basically work on output of earlier action in workflow as they are primarily used as sub-flows

Workflow Designer Pane:

The Workflow Designer within the noKodr application empowers users to build and customize automated workflows with ease.

The Workflow Designer features a flexible canvas where you can visually design workflows by dragging and dropping actions, conditions, and events. By configuring various parameters and linking actions, you can create powerful workflows that automate business processes directly within the UI. These workflows enhance your application's functionality by streamlining operations and improving user interactions.

Actions
Canvas
Workflow Elements
Navigation Bar
Zoom & Expand Controls
Workflow Essentials Creation

Section	Description
Actions	It contains multiple actions, such as `Push`, `Pop`, `Toaster`, `Show Spinner`, and others.
Canvas	It is the space where user can design workflows.
Workflow Elements	These are the workflow elements used to create a workflow. By default, Start and Error are two workflow elements available in the Workflow elements. Later user can add as per his need.
Navigation Bar	It is user interface element that provides a set of links or buttons to help users navigate through different sections of workflow, to track and save progress.
Zoom & Expand Controls	It allow users to zoom in, zoom out, or expand a view of workflow.
Workflow Essentials Creation	It allows to create workflow essentials namely variable, model, event as well as another workflow in runtime as per business need.

Workflows