Connected system objects store authentication and connection information. This allows you to easily connect to external integrations and data sources. It also allows you to deploy connection information across environments and use different connection information for each environment.
For integration connected systems, you can share base URL and authentication details across multiple integrations. This means that a password only has to be updated once, even if it's used in 10 different integrations.
For data source connected systems, you can control access to data sources using object-level security. That means you can restrict access to sensitive information during development.
This article provides detailed design information about the connected system object and its configuration options.
See also:
When you create a connected system you can choose from three main types of connected systems:
Each connected system has their own properties. See the linked page for each connected system for more information about their properties.
Each time you modify and save a connected system, a new version is created. All objects that use the connected system will use the latest version. All versions are accessible to designers who can view the connected system, and a connected system can be reverted back to a previous version at any time.
For information on how to manage object versions, see Managing Object Versions.
The security role map of a connected system controls which developers can see or modify it and its properties.
If default security groups are configured for your application, the default security groups pre-populate the role map when you create a connected system. If default security groups are not configured for your application, you are automatically assigned Administrator permissions for any connected system you create. System administrators can always access a connected system, regardless of object-level permissions.
See Editing Object Security to modify a connected system's security.
For data source connected systems, if you are using the Appian Cloud database, see Appian Cloud Database Administration for more information on how to grant access to specific schemas in the database.
The following table outlines the actions that can be completed for each permission level in a connected system's security role map.
| Actions | Administrator | Editor | Viewer | Deny |
|---|---|---|---|---|
| Integration Connected Systems Only | ||||
| Execute integrations that use the connected system | Yes | Yes | Yes | Yes |
| Data Source Connected System Only | ||||
| Execute a stored procedure called by a function or smart service | Yes | Yes | Yes | No |
| All Connected Systems | ||||
| Select the connected system in other design objects | Yes | Yes | Yes | No |
| View connected system definition | Yes | Yes | Yes | No |
| Update connected system definition | Yes | Yes | No | No |
| View the security | Yes | Yes | No | No |
| Update the security | Yes | No | No | No |
| Delete the connected system | Yes | No | No | No |
