Connection - VisualCron
The VisualCron Connection stores the address and sign-in settings that these Tasks, Triggers and features use to connect to another VisualCron Server:
- the Internal - Job/Task Control Task, to control Jobs and Tasks on another Server
- the Event Trigger - VisualCron Trigger, to react to events on another Server
- the Event Trigger - Desktop Trigger, to listen for desktop events on a remote VisualCron Server
- the Remote VisualCron Server option in Task Main Settings - Execution Context
- Servers - Sync Server Objects
- the Server Agent connection to a Broker Server
- the Server Connection option of Add Server Deck in Workspaces
- Send to connection ... on the right-click menu of Jobs, which copies them to another Server
Common settings

The Common settings and Proxy tabs are the same for every Connection type that has them; see Common settings and Proxy. VisualCron Connections cannot be tested from this window, and do not use Code page. Timeout is how long, in seconds, VisualCron waits while it connects to the other Server. When a Job/Task Control Task has its own timeout, the Task's timeout is used instead. In that case, the Server currently uses the hours of the Task's timeout in place of its minutes, so the minutes that are set in the Task are not applied.
Main settings
These fields are on Connection settings -> Main settings.

- Address: the host name or IP address of the other VisualCron Server
- Port: the port of the other Server. "16444" on a new Connection
- Username and Password: a VisualCron user on the other Server. That user's permissions decide what VisualCron can do there
Proxy

VisualCron Connections show a Proxy tab, but VisualCron does not use it. The Connection always connects directly, so make sure that the other Server's address and port can be reached without a proxy.