DSYNC integration glossary
Slave: The slave is the direction of the data synchronization without the cube. It is usually the destination system. The cube is located on the line connecting the two applications.
Master: The master is the source or origin system, we identify the master by a small cube placed on the line between the two systems being connected.
Relation: A relation is a link between two systems. If you are asked to check the relations please check the authorization settings (Keys) and then the map between the systems. Maps will have required fields indicated with a red asterisk.
RT: RT is our abbreviation for Real time. Data synchronization jobs that take place when an action occurs.
API: Application programming interface is the method to connect into or out of DSYNC.
FTP: File Transfer Protocol is the method that DSYNC uses to accept, push, pull data between applications.
Data Layout: A data layout is the schema or structure on a particular system. Data layouts are the format and structure required on the system side to be able to streamline data being processed into or out of the system. Data layouts can be simple; for example, they can have one endpoint or contain multiple endpoints for synchronization.
Map: The mapping section is where endpoints of your data layout can be paired, connected and transformed. The map is where you can instruct the DSYNC platform to pair one data field to another.
Endpoint: An endpoint is a data field within a system. DSYNC is super flexible and can work with multiple endpoints within a system. An example of a data endpoint could be customer data.
Dashboard: The DSYNC dashboard is the main canvas of the integration platform. The dashboard is your main graphical interface for connecting systems together.
BC: BC is an acronym for Base Core. BC endpoints are custom coded by the DSYNC team for specific functions.
Relation Settings: A section within your DSYNC dashboard for setting the direction of your data synchronization
CRON Period Settings: The section where developers can set the schedule of when the data synchronization should occur.
Period: Enables users to set the time period for activating the data SYNC. Time schedules can be set for any combinations by using the minute, hour, day, year settings feature.
Source: The source is the origin or starting point of the data workflow
Destination: The destination is the receiving point of the data work flow
Shared Key: A shared key can be set to indicate how your systems should match the data between your applications.
Editor: The editor is feature found within our mapping section. It is used for applying snippets of source code usually from the systems API documentation. The editor is used by developers to quickly build data layouts, and data structures for systems. Source code can be copied and pasted into the editor and DSYNC will convert the code into our cloud integration platform. The editor can also be used preview the data that will be run through the system as a test job.
Notification: A feature used to notify users on success of a data sync or the failure of the data sync.
Custom Fields: Found within the mapping section this feature enables users to enter a completely custom data field that is not listed on the available options. The custom field can is free text and is a handy tool used to synchronize complex systems.
XML: Extensible Markup Language. An XML integration is in essence a format to connect data, that acts as a "communication method" between multiple parties. XML integration allows different formats or programming languages to communicate effectively. XML integration can represent complex structures of a variety of types, well beyond the simple tables of delimited text commonly used to exchange information, and comes with tools for describing those structures
Preview: The preview feature is for testing data synchronization results. The preview function is handy for debugging your mapping. To try out the preview function you will need to have some sample data to test against your mapping.
Template: DSYNC have readymade templates for commonly used systems. The templates for developers are located within our bitbucket account or can be obtained from our sales crew. Templates save a lot of time by helping with correct corresponding fields required for some systems.
SKUs: Sku’s are a common abbreviation used in the manufacturing and retail sector. Usually a SKU is an identifier. From DSYNC perspective SKU’s can be created by the user in any style, format of combination, DSYNC simply looks for corresponding SKUs to update. Some systems automatically generate a SKU for users and if this is the main source of truth system it can typically be the SKU that is used to update the downstream applications.
Function (FX icon): A function is where you can set data transformation rules. DSYNC is not just about pushing the same data from one system to another the platform can be used to change data to the right format along the way. DSYNC can also take the same data and set functions to change the data and output to multiple systems. Common use cases we see for the Functions setting include changing the date format, setting capitals, changing spaces or fields.
Field Type: DSYNC is a flexible integration platform enabling users to change to your desired field type. Options for the data field include; Boolean, Object, Text, Number, URL, eMail, Date, Time, Date and Time. DSYNC can be used to alter, transform data between multiple applications.
Headers: Headers are http request headers. They are components of the header section of request and response messages in the Hypertext Transfer Protocol (HTTP). They define the operating parameters of an HTTP transaction.
Batch Splitter: Found within your data layout section. The Batch splitter enables you to take a collection of entities (Multiple objects / Array of objects) within the data layout and process these individually. Example if you are working with Sales order data and all you need is the sales order items then use the batch splitter to extract and process only the items
oAuth 1: OAuth is an open standard for access delegation, commonly used as a way for Internet users to grant websites or applications access to their information on other websites but without giving them the passwords. OAuth provides to clients a "secure delegated access" to server resources on behalf of a resource owner. It specifies a process for resource owners to authorize third-party access to their server resources without sharing their credentials.
oAuth 2: OAuth 2.0 is a complete rewrite of OAuth 1.0 from the ground up
Generic oAuth: DSYNC are developing a generic oAuth connector to assist our developer community.
SDK: An SDK is a Software Developer/Development Kit and is a set of instructions used by developers to program certain features of functions. DSYNC has an SDK that is used by developers to build own connector assets that can quickly connect to the systems on our network.
PO: A PO is an abbreviation for Purchase Order. Depending on the system DSYNC can synchronize purchase orders from one system to another.
Bidirectional: Fancy name for two-way synchronization. Most our systems we build into our ready-made format are bidirectional. There may be some circumstances where we are limited by the systems capabilities or there may be a endpoint that DSYNC is unable to write and update to. Some systems lock down endpoints from being updated.
Vendor: A vendor is typically a supplier
RSS URL: DSYNC can integrate different reports and feeds then publish them to a unique URL. The unique URL is generated from within your DSYNC dashboard and can be protected by a username and password. Another great feature of the DSYNC RSS feature is publishing to multiple RSS URLS the same information in different formats.
Consumer Key: DSYNC uses secure keys provided by systems as a way for DSYNC to be authorized to talk to the system. Keys are usually generated from within the system you are linking. Sometimes systems ask for a return key. DSYNC also has the ability to generate a secure token. DSYNC secure tokens are located within your account section.
Consumer Secret: Similar to the consumer key, a consumer secret is a secure token generated to enable DSYNC access to talk to the system.
Basic Access Authorization: This field is located within the system set up section and in most cases is an optional field. Basic Access Authorization is usually a user name field.
Protocol: A protocol within the DSYNC application is a settings field for your FTP. When synchronizing data between an FTP DSYNC requires the protocol to access the location.
Port: The port is a setting required for DSYNC to access information at an FTP location.