Test Connector Assets
use connection testing to validate connector asset credentials, endpoints, and parameters before playbooks run this topic covers prerequisites, eligibility by asset type, manual and automatic tests, history, and how connection testing differs from action testing on the usage tab choose your path goal where to go test one asset while editing it test connection from an asset /#test connection from an asset test a new connector asset before saving test connection when creating an asset /#test connection when creating an asset test many assets across tenants configuration manager https //docs swimlane com/configuration manager β test or test connections run daily validation without manual tests enable automatic testing /#enable automatic testing review past test results review connection test history /#review connection test history test a playbook action that uses the asset connection testing and action testing /#connection testing and action testing understand why test connection is unavailable eligibility and limitations /#eligibility and limitations prerequisites connection testing is available only when both of the following are in place requirement details test asset connection feature flag an administrator must enable test asset connection in feature flags the flag is disabled by default assets β test permission starting in turbine 26 2 0 , the user role must include assets β test on enhanced rbac test requires read and update on the asset account admin , tenant admin , and super admin receive test by default; other roles must be granted test explicitly see enhanced role based access control (rbac) https //docs swimlane com/enhanced role based access control rbac eligibility and limitations asset type test connection visible connection test can run automatic testing connector backed asset (installed connector type) yes only when the connector supports a test action (see below) only when a test action is available custom asset (key icon) no no no when a connector backed asset supports connection testing the platform runs a connection test when the connector asset manifest defines a supported test asset action , or when creating a new asset and the connector exposes a get action with no required inputs when creating an asset , the platform may use that get fallback to enable test connection when editing an existing asset , the platform uses the persisted test action configuration or an explicit test asset action on the asset manifest a get fallback alone does not enable testing on edit if no test action was saved with the asset the test connection button can appear for connector assets even when a test cannot run (for example, the connector has no supported test action) in that case the button is disabled or the test cannot complete until the connector supports testing test connection from an asset validate a connector asset from the configuration tab without running a playbook navigate to orchestration > assets open the asset in edit asset mode on the configuration tab, review or update asset parameters as needed click test connection wait for validation to complete when the test finishes a successful validation displays test was successful a failed validation displays test was failed connection testing verifies that credentials, endpoints, and other configuration values are valid before the asset is used in playbooks manual connection tests performed before you save the asset are not recorded on the history tab test connection when creating an asset when you create a connector backed asset, test connection appears next to asset parameters when the connector type supports connection testing navigate to orchestration > assets click the plus icon and select a connector asset type complete required title , name , and parameter fields click test connection review the result, then click create to save the asset use this workflow to confirm configuration before the asset is used in playbooks enable automatic testing automatic testing runs one connection validation per day for supported connector assets open the asset in edit asset mode on the configuration tab, enable enable automatic testing click save the scheduled test uses the same validation process as test connection and helps surface connectivity or authentication issues before playbook execution automatic testing is disabled by default and must be enabled per asset it is available only for asset types that support connection testing automatic connection test entries appear on the history tab after the scheduled test runs because tests run once per day, new entries may not appear immediately after you enable automatic testing review connection test history the history tab on edit asset shows asset changes and connection testing activity summary fields field description created date the asset was created created by user who created the asset last modified date the asset was last updated last modified by user who last modified the asset activity table column description date date the activity occurred description type of activity status result of a connection test, when applicable user user associated with the activity details additional information for failed connection tests connection test activity types activity description connection test (manual) a test initiated with test connection connection test (automatic) a test initiated by enable automatic testing connection test status success β the connection test completed successfully failure β the connection test was unsuccessful asset creation and modification activities do not display a status view failed test details on the history tab, locate a failed connection test row click view in the details column a panel opens with diagnostic information for troubleshooting history retention asset history is retained for seven days older activities are removed from the history view test from configuration manager administrators can test connector assets across tenants from configuration manager https //docs swimlane com/configuration manager test (ellipsis menu) β test a single asset test connections (toolbar) β test multiple selected assets and review bulk results connection tests started in configuration manager update asset health metrics and appear on the asset history tab bulk tests require assets β test on each affected tenant for step by step procedures and bulk result columns, see configuration manager https //docs swimlane com/configuration manager connection testing and action testing the usage tab on edit asset lists playbooks and components that use the asset view & test opens the action test console β this runs the action with optional inputs; it is not the same as asset connection testing connection testing action testing (usage tab) purpose validate asset credentials and connectivity run a specific connector action where configuration tab β test connection ; configuration manager usage tab β view & test recorded on history yes (after save; manual and automatic) no to test an action from the usage tab open the asset in edit asset mode select the usage tab click view & test for the playbook or component row provide inputs ( from previous run or manual entry) if required click test and review the result section when a connector does not support testing if test connection is disabled or bulk testing reports unsupported assets the connector asset type may not define a supported test action custom assets never support connection testing mixed bulk selections that include unsupported assets must be corrected β deselect unsupported assets and test only eligible connector assets request test support for a connector swimlane and connector authors can add connection testing by defining a test asset action on the connector asset manifest (or by exposing a get action with no required inputs for new assets) to request test capability for a marketplace or custom connector, contact swimlane support with the connector name and asset type see also assets https //docs swimlane com/assets β create, edit, and manage assets configuration manager https //docs swimlane com/configuration manager β multi tenant asset management and bulk connection tests enhanced role based access control (rbac) https //docs swimlane com/enhanced role based access control rbac β assets β test permission