With a Remote Domain configuration, the Client Domain can access objects from the Server Domain via scripts, by using the Application.GetObject method, or via Links, that is, any functionality that creates a connection to another object, such as user event expressions, ElipseX Object-type properties, Link sources, Alarms, or fields in Historic or Storage objects, among others. Objects accessed this way can be either Viewer or Server objects.

Access to objects from other Domains is performed via alias or Domain Name, which must precede each object's complete path, separated by a colon. That is, for Link sources or an Application.GetObject method to reference another Domain, users must use a DOMAIN:PATH syntax, where DOMAIN is the alias given to that Remote Domain connection, and PATH is the complete path of an object or property from that Domain. In case of Links, sources may include expressions referring to several objects, with possible combinations among local objects and Remote Domains, such as Driver1.Tag1 + Remote:Driver2.Tag1 * 2.

Remote Domain's names may also need brackets, such as [DOMAIN]:PATH. In this case, the same rules applied for naming objects are valid. Names of Domains need brackets in the following cases:

•Contains any character that is not a letter (a-z | A-Z) when used as the first character of a Domain's name

•Contains any character that is not a letter (a-z | A-Z), a number (0-9), or an underscore (_) when used after the first character of a Domain's name