Nected Docs
Try Nected For Free
  • 5 min QuickStart Guide
  • Getting Started
    • Introduction
    • Core Concepts
    • Use Cases
    • Tech Architecture
    • FAQs
  • INTEGRATIONS
    • Overview
    • Integrations Libraries
      • PostGres
      • MySQL
      • Oracle
      • MS SQL Server
      • Snowflake
      • MongoDB
      • RedShift
      • REST API
      • Google Sheets
      • Slack
    • Managing Integrations
  • DATASETS
    • Overview
    • Managing Dataset
  • Rules
    • Overview
    • Rule Types
      • SimpleRule
      • DecisionTable
      • Ruleset
      • Rule Chain
    • Rule Conditions
    • Rule Actions
    • Concepts
      • Rule Result
      • Test & Publish Rules
    • Add Input Attributes
      • JSON Input Attributes
      • List Input Attributes
  • Triggers
    • Trigger Rule via API
    • Trigger Rule via WebHook
    • Trigger Workflow via API
    • Trigger Workflow via WebHook
    • Scheduler
    • Rule Response Format
  • Workflow
    • Overview
    • Managing Workflow
    • Add Node
      • Action Nodes
        • Rule Node
        • Workflow Node
        • Custom Code Node
        • Database Node
        • REST API Node
      • Control Nodes
        • Loop Node
        • Delay Node
        • Response Node
        • Set Variables Node
        • Switch Block
    • Test & Publish Workflows
  • CODE AND DATABASE QUERIES
    • JavaScript Editor
    • Formula Editor
    • JSON Editor
    • List Editor
    • Excel-like Function
  • Embedded System
    • White-Labelling
    • Embeddable View
  • Self Hosting
    • Overview
    • Infrastructure Sizing
    • New Installation
      • Docker
      • Kubernetes
        • Set Up Kubernetes Cluster on AWS EKS
    • Additional Configuration
      • High Availability
      • Email Setup Guide
    • Upgrade Nected Version
  • Security
    • API Authentication
      • OAuth as part of Authentication under REST API
    • Role Based Access Control (RBAC)
    • SOC 2 Type 2, GDPR, ISO Compliance
  • Audit
    • Audit Trail
    • Approval Flow
    • Version Control & Rollback
    • Import/Export
  • Management API
    • Audit Log API
    • Global Variable API
  • References
    • Attribute Library
    • Global Variables
    • Pre-Configured Tokens
    • Pre-Configured Operators
    • NULL Value Handling/Behavior
    • Troubleshooting Errors
      • Multiple Tabs/Users Edits
      • Limits in Nected
    • Allowed Status Combinations
    • Environments
    • Usage Widget
    • Gen AI
  • ACCOUNT SETTINGS
    • Workspace Setting
      • Date Format and Timezone Settings
Powered by GitBook
On this page
  • 1. Property
  • 1. Custom Function
  • 2. Input Attributes
  • 3. Global Attributes
  • 4. System Attributes
  • 5. DataSet Attributes
  • 2. Operators
  • 3. Values
  • Error Handling
  1. Rules

Rule Conditions

PreviousRule ChainNextRule Actions

Last updated 8 months ago

You can seamlessly build rule conditions using the no-code Rule editor over Nected.

Conditions would have 3 components:

1. Property

Click on propertydropdown to select the properties.

Nected support below attributes to be selected as property:

1. Custom Function

At Nected, we believe that systems should be configurable & flexible to adapt to any business need without a need to do anything from outside.

Sample JS Formula:

{{.customInput.attributeName}} > {{.dataSet.attributeName}}

Custom Function in conditions should return a boolean only otherwise it will throw a "syntax error" issue in the editor & will block the rule to get tested.

2. Input Attributes

3. Global Attributes

4. System Attributes

System attributes are provided by the system and are related to time and other system-related information.

5. DataSet Attributes

2. Operators

Nected provides various pre-configured operators that you can use with SimpleRules and DecisionTables.

The following table lists all the pre-configured operators and their available values.

DataType
Available Operators
Desc

Common/Generic

  1. Any

  2. Exists

  3. Doesn’t Exist

  4. Is Null

  5. Is not Null

Number

  1. Between

  2. Not Between

  3. Equals

  4. Not Equals

  5. Greater than

  6. Less than

  7. Greater than or equals

  8. Less than or equals

  9. Is Even

  10. Is Odd

String

  1. Equals

  2. Not Equals

  3. Contains

  4. Does not Contains

  5. Starts With

  6. Does not start with

  7. Ends with

  8. Doesn’t Ends with

  9. Is IN

  10. IS NOT IN

  11. Is Empty

  12. is not Empty

Dates or DateTime

  1. Between

  2. Not Between

  3. Equals

  4. Not Equals

  5. Greater than

  6. Less than

  7. Greater than or equals

  8. Less than or equals

Boolean

  1. Is False

  2. Is True

List

Contains

Does not Contain

Is Empty

Is not Empty

Checks if the list contains a specific value.

Checks if the list does not contain a value.

Checks if the list is empty.

Checks if the list is not empty.

JSON

Has Key

Does not Have Key

Contains

Does not Contain

Checks if the JSON object contains a specific key.

Checks if the JSON object does not contain a specific key.

Checks if the JSON contains a specific value or key-value pair.

Checks if the JSON does not contain a specific value or key-value pair.

3. Values

Error Handling

In case of any issue in the condition, the Rule will show an error like mentioned below, and the Testing rule in staging will not be allowed till you fix the error. And since we don't allow rules to be published if not tested, publishing rules too would be blocked. This is to ensure that nothing wrong or bad goes into your production anyhow.

Hence, we have provided a to support any custom and specific condition(s) needed by your business and can't be built in a no-code editor. You can write any Javascript code using input attributes, global attributes, system attributes as well as dataset attributes as .

These are input attributes defined in and are passed as params in each Rule API. These can be referred to in any editor using token name starting with .customInput

These are attributes defined under and can be usable across multiple rules. These can be referred to in any editor using token name starting with .globalVar

These are attributes imported from columns. The type of columns too are derived from the database query directly. If you've selected a dataset as the source, you can use attributes from the dataset to form conditions within the rule. This allows you to leverage the data in your dataset for decision-making. These can be referred to in any editor using token name starting with .dataset

Values can mostly be constants or of the same datatype as property.

Javascript (JS) editor
tokens
Add Source
Global Variables
Dataset
tokens
Property
Operators
Values