Deployer

General

Deployer is managed by Fleet Manager
Deployer is managed by Fleet Manager but the Deployer instance is not currently running
Only the plugin difference between the plugins used in the project and those installed will trigger a warning when importing a project or deploying it from another node rather than the difference between all plugins in the instances (Experimental - Some rare uses of plugins may not be pointed) - (has a best-effort (Tier 2) support)
URL should be http[s]://host[:port]. A URL suffix is unexpected and will likely not work.
An admin API key valid on the remote Deployer
When Deployer is configured in "Publish on a remote Deployer", the Deployer of this DSS node is generally not used. Enable this to show it nevertheless.

API Deployer

 Product life-cycle steps

Project Deployer

Allow to create Project Deployer infrastructure that can contain multiple Automation nodes for improved WebApps availability.
Product life-cycle steps

Design nodes

 The design nodes the deployer will be allowed to communicate with.
Design nodes are managed by Fleet Manager
No remote design nodes configured. If api endpoints were published from remote design nodes, their Model Status & External Model will not be retrieved.
Internal URL (Used by Deployer) External URL
{{ node }} {{ designNodes.externalUrls[$index] }}

API and Project Deployers

Local Deployer is not enabled. Configuration must be performed on the remote deployer.

API Designer: Testing

SQL connection to load the bundled data when testing API services.