Upon successful Multi-Galaxy pairing, the DI Objects from the remote Galaxy become visible and can be browsed within the IO Device.

Once Galaxy A and Galaxy B are successfully paired, if objects with IO references are exported from one Galaxy (and imported into the other), the expectation is that these attributes will continue to source their values from the peer Galaxy.Currently, there is no efficient method to bulk-update these IO references. For example, an attribute referenced as Pump.PV in Galaxy A must be manually updated to GalaxyA:Pump.PV in Galaxy B. Because this modification can only be done individually, object by object, dealing with thousands of such adjustments creates an unmanageable workload—it is essentially an engineering disaster.Therefore, I highly recommend that upon successful Multi-Galaxy pairing, the DI Objects of the peer Galaxy should be made visible and browsable within the IO Devices view. Alternatively, the system must provide a mechanism (such as a bulk-edit utility) to rapidly configure and update these cross-Galaxy IO references.