Omnata Product Documentation
  • Omnata Sync for Snowflake
    • What is Omnata Sync for Snowflake?
    • How it works
      • Terminology
      • Branching Mode
      • Sync Directions and Strategies
        • Outbound
        • Inbound
      • Rate Limiting
      • Access Control
      • Notifications
      • Security and Privacy
      • Internal tables
      • Internal Stored Procedures
      • FAQ
    • Step-by-step guides
      • 1. Install the Omnata Sync Engine
      • 2. Install the Omnata Plugin
      • 3. Configure the Plugin
      • 4. Create a connection
      • 5. Create a sync
    • Apps
      • Aerobotics
        • 📘Release History
      • Airtable
        • 📘Release History
      • Amazon Ads
        • Privacy Notice
      • ApprovalMax
        • 📘Release History
      • Bamboo HR
        • 📘Release History
      • Clockify
        • 📘Release History
      • Contentful
        • 📘Release History
      • GitHub
        • 📘Release History
      • Github
      • Google Ads
        • 📘Release History
      • Google Sheets
        • 📘Release History
      • HubSpot
        • 📘Release History
      • Hubspot
      • Infor Data Lake
        • 📘Release History
      • Jira
        • 📘Release History
      • LinkedIn Ads
        • 📘Release History
      • Mailgun
        • 📘Release History
      • Marketo
        • 📘Release History
      • Meta Marketing
        • 📘Release History
      • Microsoft Ads
        • 📘Release History
      • Microsoft Dynamics 365 Business Central
        • 📘Release History
        • 📘Release History
        • 📘Release History
        • 📘Release History
        • 📘Release History
      • Microsoft Entra ID
        • 📘Release History
        • 📘Release History
        • 📘Release History
        • 📘Release History
      • Microsoft Excel
      • Microsoft SQL Server
        • 📘Release History
      • Monday.com
        • 📘Release History
      • MRPeasy
        • 📘Release History
      • PayHero
        • 📘Release History
      • Pinterest Ads
        • Privacy Policy
      • PostgreSQL
        • 📘Release History
      • Salesforce
        • Salesforce Permissions needed
        • Formula Fields
        • How we use the Salesforce APIs
        • 📘Release History
      • Salesforce Marketing Cloud
        • OAuth for APIs, SFTP for file transfer with GPG on outbound
        • OAuth for APIs, SFTP for file transfer
        • OAuth for APIs, Cloud Storage for file transfer
        • 📘Release History
      • Shopify
        • Outbound sync data structures
        • 📘Release History
      • Slack
        • 📘Release History
      • Tiktok Ads
        • Privacy Policy
      • Typeform
        • 📘Release History
      • Wise
        • 📘Release History
      • Xero
        • 📘Release History
      • Zendesk Support
        • 📘Release History
        • 📘Release History
    • Plugins
      • Anatomy of a Plugin
      • Example Plugins
        • Example Plugin: Slack
        • Example Plugin: Zoho CRM
      • Creating Plugins
      • Advanced Plugin topics
        • Advanced rate limiting / concurrency
        • Custom Jinja filters
        • Custom Record Transformers
        • Dynamic Configuration Forms
        • Test case generation
    • Branching
      • Inbound Sync branching
      • Outbound Sync branching
    • Integrations
      • dbt
        • Validation Tests (coming soon)
    • 📘Release History
  • Omnata Connect for Salesforce
    • Overview
    • Getting Started
      • Install the Salesforce App
      • Connect to your data warehouse
        • Snowflake
        • BigQuery
        • Rockset
        • Firebolt
        • SingleStore (previously MemSQL)
      • Deciding which mode to use
    • Omnata with Salesforce Connect (External Objects)
      • Object Configuration
      • View your data in a list
      • Link to other objects
      • Use in a Report
      • Database schema changes
      • Writing to External Objects
    • Omnata with Salesforce Lightning Components
      • Object Configuration
      • View your data in a list
      • Link to other objects
      • Using the Lightning Component on a page
      • Assigning Permissions
    • Advanced Features
      • Row Level Filtering
      • Multi-Currency handling
        • About Multi-Currency
        • Support in Omnata Connect
        • Apex Features
    • Integrations
      • Datadog
    • Omnata with Salesforce Apex
    • Security
    • Use cases
      • Linked object drill-downs
      • Global Search
      • ERP and historical data
      • Embedded product metrics
    • Best Practices
      • Global Search
      • Change Management
      • Snowflake table design
      • Salesforce page layout
      • Salesforce Caching
Powered by GitBook
On this page
  • App
  • Connection
  • Sync
  • Branch
  • States
  • Sync Health States
  • Sync Activity States
  • Sync Run Health States
  • Terminology specific to outbound syncs
  • Record States
  • Record Sync Action
  • Record Apply States
  • Record Apply Reasons
  • Terminology specific to inbound syncs
  • Stream
  1. Omnata Sync for Snowflake
  2. How it works

Terminology

This page describes the terminology Omnata Push uses throughout the product.

App

An App (short for Application) is a SaaS product.

Examples: Salesforce, Hubspot, Zendesk

Internally, each App has a Plugin which contains all the code for communicating with that App.

Connection

A Connection is a link to a customer's instance of an App.

Examples: Salesforce Production Environment, Salesforce Sandbox 2

Sync

A Sync defines a configuration and schedule to synchronise data from Snowflake to an App, via a particular Connection.

Examples: Contacts Sync to Salesforce Production Environment

Branch

Branching is how change management occurs within Omnata push. Every Sync has an implied 'main' branch, which is the production environment.

A Sync created in Advanced mode can have branches, which allow proposed changes to be tested outside of the production environment, and merged in when ready.

Branching is described in more detail in the 'Branching' page.

States

Sync Health States

Describes the Sync's state from a success perspective.

Pending: Sync is yet to have its first run

Healthy: All pending records have either been successfully applied, or outstanding issues suppressed

Incomplete: The most recent sync containing records had at least one success, but there are records with unresolved sync failures

Failed: The most recent sync that contained records had zero success

Delayed: Sync behind schedule due to rate limiting, but otherwise Healthy

Sync Activity States

Describes the sync's current activity.

Pending: Sync is yet to have its first run

Running: The sync is currently executing

Waiting: The sync is waiting for the next scheduled run time

Paused: The schedule has been paused, so that runs will no longer trigger at the configured time

Sync Run Health States

Describes a Sync Run's state from a success perspective.

Pending: Sync Run has been initiated

In Progress: Sync Run is currently in progress

Healthy: All records were successfully sync'd without error

Incomplete: At least one success occurred, but there were records which experienced errors

Failed: All records in the sync experienced errors

Delayed: The sync run was incomplete due to rate limiting, but otherwise Healthy

Terminology specific to outbound syncs

Record States

Describes what was most recently observed in the source (Snowflake).

Created: Record was created in the source. When the Sync strategy is "Replace", all records remain in this state.

Updated: Record was updated in the source

Deleted: Record was deleted in the source

Record Sync Action

Describes the action required as a result of the record state, given the sync strategy.

Below is the standard set of Sync Actions, which covers most common actions to perform in apps.

Custom Sync Actions can be defined in plugins and utilised by custom sync strategies.

Name
Description

Create

Object will be created in the app

Update

Object will be updated in the app

Delete

Object will be deleted in the app

Send

Record will be sent to the app

Record Apply States

The state of the Record's sync action.

Success: Record has been applied in the app

Source Failure: The record failed pre-flight checks

Destination Failure: The record failed to be applied in the app

Delayed: The record was delayed due to rate limiting or the cancellation of a sync run

Active: The record is actively being applied

Not Required: No action was required

Resync Requested: The record has been marked for resync. Sync action will have been set at the same time.

Skipped Once: The most recent change was manually skipped, but future changes will continue to sync

Skipped Always: The record has been permanently excluded from the sync

Record Apply Reasons

The reason for current apply state.

Transform Error: An error occurred while performing the transformation that occurs during staging.

Change Criteria Met: The record changed.

Previously Delayed: The record was included in a previous run, but was not processed in that run.

Resync Requested: The user requested that the record have a resync performed.

Previously Failed: The previous attempt to apply the sync action failed.

Terminology specific to inbound syncs

Stream

Represents an object within an app, e.g. Salesforce has Account, Contact, etc. This term is borrowed from the Singer Specification.

PreviousHow it worksNextBranching Mode

Last updated 7 months ago