Endpoints (UI Navigation)
Connexion has a concept of 'endpoints'. An endpoint is any point at which data is ingested into or sent from Connexion. For example, an MLLP socket on an HL7 Inbound device is an inbound endpoint, and an MLLP socket on an HL7 Outbound device is and outbound endpoint. Other endpoints could be the file system, FTP, network sockets, branch devices etc. Many built-in devices define endpoints, and these endpoints can be used to navigate to other channels involved in a particular message's workflow. For example, if you have an Outbound HL7 device sending to an Inbound HL7 device in the same system, the UI will display an endpoint icon to allow you to quickly jump to the linked channel.
When the Connexion UI loads, it parses all the endpoint data for the system and attempts find a matching endpoint in another channel. If it cannot find a match, then it will simply call the OS shell command with the device-defined endpoint. For example, the file writer device may publish a file or ftp endpoint, in which case the file explorer or default ftp client may be launched.
In some cases, instead of the UI dynamically matching endpoints, endpoints are stored with a device's configuration. For example, when linking remote agent and Connexion channels, an endpoint is generated and stored in each device. This allows the endpoint icon to point to channels in other Connexion or Gateway systems. Endpoints of remote systems typically have a more verbose format which includes all of the information required to launch a separate instance of either Connexion of the Gateway.
You also have the option of defining your own hard-coded endpoints. For example, if you want to associate a particular website with a device (for example, a customer portal or help link), then you can right-click on the device icon and choose the 'Edit Endpoints' option.
Click the 'Add' button and either choose to link to an existing device in Connexion, or choose to link to an external resource (such as a web page)
Start typing in the blank row to enter the name of your resource. Since we simply call the operating system with whatever string you provide, it will be opened by whatever installed program is registered for that string.
Your manual endpoint is now displayed on the given device.