I was looking in the documentation, and was having trouble finding the expected behavior for when updating modified UDTs with the EAM module.
My general use case is that I would like to have a central enterprise gateway, with two regional enterprise gateways that are then connected to all of the gateways within their respective regions. I would like to define and then distribute UDTs from the tag provider of this central gateway, down to the tag provider of the regional gateways where the UDTs can be modified as necessary by regional teams before being distributed out to the tag provider of each gateway below them.
What I am curious about is if I create a UDT, distribute it out to a regional gateway which then adds an additional field unique to their region, and updates the tag path to fit the naming structure of their region; how will those changes be implemented when I push a new version of this UDT from the central gateway? Will these changes be visible in a diff so the team may readjust to fit the new UDT design with the changes they already made, will the team need to go back and make each change again after the UDT is updated, or is there a different process entirely?