ERP Bridge
  • Welcome to ERP Bridge
  • Software & Hardware requirements
  • Environment Configuration
  • Data Preparation
  • Overview
  • Registration and first login
  • The Installation
    • 0 - Go to Installation wizard
    • 1 - Name
    • 2 - Hubspot Login
    • 3 - Sync Frequency
    • 4 - Download Wizard
    • ERP Bridge Wizard - On-Premise
      • 0 - Install the wizard on-premise (.msi)
      • 1 - Welcome screen
      • 2 - Login
      • 3 - Select Installation
      • 4 - Database
      • 5 - Database Tables
      • 6 - Download the agent
      • 7 - Start Agent
    • Back to the cloud
  • The Operation
    • 0 - Choose direction
    • 1 - Default settings
    • 2 - [HS -> DB] Filters
    • 2 - Database Mapping
    • 3 - Decision Rules
      • Example with 1 decision rule
      • Example with 2 decision rules
    • 4 - [DB -> HS] Associations
  • Start to Synchronize
  • Uninstall
  • Advanced topics
    • Change ERP Bridge Agent path
  • Troubleshoot
    • On-Premise wizard errors
  • HubSpot to Database sync
    • Handling empty fields
  • Security Documentation for ERP Bridge
    • 1. Product Access Control
    • 2. Rate Limit
    • 3. Authentication Resources
    • 4. Encryption
    • 5. Change Management
    • 6. Cloud Security
    • 7. Security certification
    • 8. Availability
    • 9. Logging
    • 10. Installer Desktop
    • 11. Server Agent
Powered by GitBook
On this page
  • Decision Algorithm
  • The difference between NEXT and STOP
  1. The Operation

3 - Decision Rules

Last updated 10 months ago

In this step you can program the logic behind the decisions made for each record. The system is basically a list of if-then conditions based of how many records or object are found in the destination data after searching for a specific property/column.

Let's explore a simple example with just 1 decision rule:

When there are more than one decisions, it's important to set the right "Decision Algorithm", this setting let you choose from 2 options:

Decision Algorithm

  • Funnel: the decision rule will filter the results already filtered from the decision rule before.

  • Isolate: the decision rule will always filter the results from the total, discarding every prior filter and evaluating every rule as separated/isolated.

Let's explore a simple example with just 2 decision rules and the decision algorithm set on "Funnel": Let's do another example:

The difference between NEXT and STOP

When you have just one decision rule, there is no difference between one and other.

When you have more than one decision rule, the NEXT rule will skip the current decision rule and bring the software to the next decision, so if we say that we are on the first rule of three, the NEXT rule will skip the current decision and jump to the second rule. With the STOP rule the software will skip all the rules for the current record and will go to the next record starting again from the first rule.

CLICK HERE!
CLICK HERE!
Decision Rules