Once you log on to Studio using your organizational authentication you can see a default Home page. You can customize your account with changes to the profile settings. You can define and make use of the different environments when building, testing, and distributing apps.
Under your Studio Account Profile, you can find the Manage Environments that allows you to add and customize your data environments. There can be several members of your development team. Typically you would have clean/live data in your Production databases. However, when you are creating different apps, then the data that you use can have certain limitations or just be sample data and need not mirror the Production data with the variety of tests and trials that you would like to conduct.
Thus with Manage Environments you would build only the data environment to use for your app-building process. It will only be the data environment that is customized for the Connectors, database as well as API connectors. Remember that you would not be customizing the App environment. That will remain unchanged as Prod, Beta, and Dev.
Managing Data Environment
When you click Manage Environment you can see the Environment page. Here note that the Production, Staging, and Development are the default data environments already provided for you. These environments cannot be removed or deleted or modified. Manage Environment provides you the features to add a new custom environment as per your requirement. You can also edit or remove the environments you have added using the Manage Environment option. These environments are account-level environments that can be utilized in all your apps. requirement. You can also edit or remove the environments you have added using the Manage Environment option.
When you define these environments, remember that the Sheets will however be basically mapped to either of the three default environments namely the Prod, Beta, or Dev environments. By default, the Production environment will have Sheet’s Prod env, Staging environment will have Sheet’s Beta environment and Development environment will have Sheet’s Dev environment.
When you click Manage environment, you are taken to the Environment page, where you can find the Add Environment option to add new custom environments.
Click Add Environment and enter the Environment Name. When adding the environment name make sure that you follow the valid naming format. The format to name should not start with a number and special characters cannot be used in the name.
Select the Sheet Environment where your data would be mapped for the newly created environment.
Click Add. Your environment gets added to the list of Environments.
If you want to make a modification or change to an existing custom environment, go to More options indicated by the three dots (…) and click Edit.
Modify the name or environment as required and click Edit. Make the necessary changes and click Save.
If you want to delete the environment, go to More options indicated by the three dots (…) and click Delete.
There will be a confirmation dialog before deletion. Click Delete to confirm. Note that when you select and click delete, the selected environment appears lighter and with a buffering symbol. Once you click delete the selected environment is deleted.
You can thus easily Manage Environments depending upon your development needs. These custom environments that you create can be used when building your apps. Data Environment keywords are also added which can be used for carrying out the different operations.
Now typically these environments would be useful when configuring the API connectors and the DB Connectors. You can also find it useful when you Manage Accounts for Global Connectors like Airtable. There could be different scenarios where you might want to make use of the custom environments.
The custom data environments can be needed in complex and multiform app development scenarios which involve several members working on these apps. You could configure connectors accordingly. The Action flow also contains the On-screen Action under the Utility Block to change the data environments as a step in course of the action.
Note: By Default all Api and database connectors added are for the Production Data environment and your connector must have at least the Production environment configured.
You don’t need to configure connectors for All environments, only those you require need to be configured.