For example, let's say you are using the Tulip Player on your computer to test a Trigger that runs a connector function with a POST request. You may not want to be adding test data to your production database.
Instead, you may want to run the connector function with a test database. You can use "Environments" in Tulip to accomplish this.
Environments allow you to run the same connector functions on different databases/services, depending on the status of the app.
In other words, when you run an app in development mode, a connector function will automatically run on your testing or development environment.
To enable multiple connector environments on your account, navigate to the Connectors tab via the Account Settings page of your Instance. Toggle the switch under "Allow Selection of Connector Environment in Developer Mode".
Setting Up Multiple Environments
After you create a new SQL or HTTP Connector, you will see a screen like this.
By default, "1 connection" will be selected, which means that connector functions in all app versions will connect with the same server.
But, if you want to run Connector Functions in multiple environments, select "2 connections". You will now have the opportunity to add details about 2 separate servers.
Use Add Connection Details to add details about each server.
Trigger Example
Let's imagine that you are running the following Connector function in an app:
Here would be the sequence of events:
Administrator or operator opens the step in the app, which triggers the "New Connector Function" trigger.
In the "Then" statement, you are specifying that the "Get_Configuration" function will run on the "Server Assembly DB" connector with the input of text "test".
If the app is in "development mode" when the step is opened, then the function will run on the server connected to the Testing/Development environment. If the step is opened in a published version of the app, the function will run on the server connected to the Production environment.
Using Environments with Approvals
So far, we have discussed two separate environments. But, if you have the Approvals feature in your account, there will be an option to specify three environments: production, testing and development.
In this case, the "testing" environment will be used when the app is in the "Awaiting Approval" state.
You can also head to community.tulip.co to post your question or see if others have faced a similar question!
Connectors
Connectors are how your Tulip apps can connect to other systems. Connectors can make API calls with HTTP Connectors, or pull data directly from SQL databases. Additionally OPC-UA Connectors can be used to retrieve Machine data.
Once pulled, data can be used throughout your applications.
Connector Function
Connector Functions are individual operations to interact with an HTTP or SQL Datasources. Functions can have inputs and outputs, and can be called from Triggers.
Once pulled, data can be used throughout your applications.
Connector Function
Connector Functions are individual operations to interact with an HTTP or SQL Datasources. Functions can have inputs and outputs, and can be called from Triggers.
Once pulled, data can be used throughout your applications.
Environment
An environment is a set of parameters that match specific configurations for tests. An environment includes API endpoints and authentication profiles for REST, SOAP, and GraphQL services, as well as database connection settings, custom project properties, and parameters of connection to JMS servers.
Tulip Player
Tulip Player is the Windows/Mac executable program where users can run Tulip apps. Tulip player allows you to create a more seamless user experience by removing the need for a web browser and allows increased IT controls.
Trigger
Triggers are the mechanism to do things in Tulip Apps. Store data, move users between Steps, Interface with hardware, Etc.
Triggers can be added to widgets, machines, devices, apps, and steps.
Tulip Instance
A Tulip customer account. Your instance can be found at https://[your-instance].tulip.co
When your instance is referenced, we are just talking about your Tulip account on an organization-level, not user-level.
Developer Mode
Developer Mode is a dedicated interface to test your applications. Dev mode doesn't write to Tables or create Completions so production data isn't impacted.
Connectors
Connectors are how your Tulip apps can connect to other systems. Connectors can make API calls with HTTP Connectors, or pull data directly from SQL databases. Additionally OPC-UA Connectors can be used to retrieve Machine data.
Once pulled, data can be used throughout your applications.
Connector Function
Connector Functions are individual operations to interact with an HTTP or SQL Datasources. Functions can have inputs and outputs, and can be called from Triggers.
Once pulled, data can be used throughout your applications.
Trigger
Triggers are the mechanism to do things in Tulip Apps. Store data, move users between Steps, Interface with hardware, Etc.
Triggers can be added to widgets, machines, devices, apps, and steps.
Connectors
Connectors are how your Tulip apps can connect to other systems. Connectors can make API calls with HTTP Connectors, or pull data directly from SQL databases. Additionally OPC-UA Connectors can be used to retrieve Machine data.
Once pulled, data can be used throughout your applications.
Was this article helpful?
Thank you for your feedback! Our team will get back to you