Hey Dojo,
I have a situation where a protocol is upgraded to a new major range. In the previous range, the protocol had two connections. However, the new range is of type virtual and has no connections any more.
After setting the new range as the Production version, the element.xml still holds the ports information. Is this intentional and can these cause problems with e.g. the timeout state of the element? After all, the port is not defined in the protocol, but still seems to be lingering around in the element.xml...
Is there a mechanism to remove the ports from the element.xml? Code that can be run for these elements?
Hi Jan-Klaas,
When changing the connections in a protocol, we recommend to recreate the element because of this reason. That is also why a new range is created to point out the impact of this change.
Thanks for the answer. I’m afraid recreating the elements is not an option because they contain critical element data. Alternatively, we need to create new elements and automatically migrate/copy the element data from the old element to the new element. It would take significant work to turn this into a convenient and seamless migration. So, I’ll probably leave it as it is.
Thanks again.