Currently, workbench editors suffer from an inability to react to changes in assets immediately, without refreshing the page. This can be observed when multiple assets are in a relation (e.g. Data objects A, B, where A contains B as a field). When the data object B is renamed (let's say to C), user is warned about the possible impact (which is good), however object A can be further modified until the editor is reloaded (only then a parsing problem is detected). Once again when renaming C back to B, it takes a refresh to be able to use A again.

Provide a mechanism, which will resolve the issue across all types of assets (e.g. cover cases when a data object is used in DRL file, etc.). Investigate a way to leverage recent impact analysis improvements. One possible idea is to make use of CDI events to propagate information about dirty assets (ones that have been affected by recent changes) and let the editors react accordingly (e.g. reload a data object).