Starting in AX-3.7, the synthetic types framework feature allows you to browse remote stations containing modules and types not present on your local Workbench installation. As a result, you have the capability to manage much more diverse systems.

This synthesis occurs automatically when you connect to a remote station containing modules and types not on the local Workbench installation.

For example, you may find that the Adr Service is installed on a remote station, however, the adr module is not installed on the local Workbench installation. Previously, in AX-3.6 and earlier, attempting to access a station from a Workbench installation without the same set of modules would result in exceptions and the inability to browse the remote station tree. Now, in AX-3.7, Workbench can query the station for module and type definitions when unknown types are encountered. The information is then used to synthesize the modules and types, minimally representing those objects in Workbench, and permitting you to access the remote station and navigate the station tree.

Modules and types synthesized over the Fox connection are bound to the current connection and are cleared from memory when the connection is closed. The synthesized modules and types are not added to the Workbench registry, they are only available while connected to the remote station.

When types are synthesized, only the slots or enumeration entries are recreated in Workbench. The only accessible logic is that which is inherited from super types that exist within modules in the Workbench installation.

Components not accessible in synthesized types:

Workbench uses special styling to distinguish synthesized modules and types from those that exist in the Workbench installation. For example, in Figure 1 below, a small “beaker” icon is combined as a badge on top of the normal network and device icons to indicate the AdrNetwork and AdrDevice are synthesized. The beaker badge is combined with component icons on the property sheet as well.