Propagate Extension Database Connection change without needing to publish Consumers

By Carlos Alfaro on 20 Oct

When an Extension Database Connection configuration is changed, all the Consumers are marked as outdated and need to be republished to reflect the change on runtime.

This could be changed to automatically get the correct connection on runtime, without the need to republish sometimes dozens of eSpaces, just like it is done currently for the Webservices and REST Effective URL changes.

CA

This idea has no comments yet. Be the first to comment!