Best Practices For Globally Used APIs in V9
Hey,
In version 8 we were able to add APIs by going to Settings -> Integrations -> External Services. Once added, we were able to access them in all our Projects.
When migrating to version 9, we realized that the external services are only available when going into the Project and adding them from Manage -> Integrations -> External Services.
What is the best practice for globally used APIs which can be used by many other Projects? What is the use of the old Settings -> Integrations -> External Services folder?
Comments
-
Hey there,
For globally used APIs, the best practice would be to create a common Project which includes all the necessary global APIs which need to be shared. This common Project could then be established as a Dependency in all other relevant Projects as needed.
More on Project Dependencies: Project Dependencies
The old Settings -> Integrations -> External Services folder is available for you to create APIs and then move them to the necessary Project. Additionally, when migrating from version 8 to 9, all relevant entities will be accessible here and transferrable to the respective Project.
Hope this helps!
-Cody
Howdy, Stranger!
Categories
- 4.2K All Categories
- 65 General
- 11 Training
- 201 Installation / Setup
- 1.1K Flows
- 106 Rules
- 261 Administration
- 212 Portal
- 490 General Q & A
- 694 Forms
- 333 Reports
- 3 Designer Extensions
- 47 Example Flows
- 51 CSS Examples
- 1 Diagram Tile
- 7 Javascript Controls
- 178 Pages
- 5 Process Mining
- New Features
- 178 Datastructures
- 69 Repository
- 221 Integrations
- 28 Multi-Tenant
- 27 SDK
- 78 Modules
- 56 Settings
- 25 Active Directory
- 12 Version 7
- 35 Version 8
- 76 Lunch And Learn Questions