Communication api have got two types of data to update: 1. The data saved in core, ef room name, avatar name etc. 2. The dynamic form fields where any sort of info should be sent to the communication provider.

Changing any data in communication api and dyniamic fields now triggers a task and everything happens in one task and technically it has be one task to update the room. That means, core communication api wont have any understanding of the dynamic form fields coming from the plugin and what needs to saved. Example, nothing changed in the dynamic form fields but with the click save changes, it will add a task.

Add a checking layer in api to understand the change before adding a task for efficiency. List of fields to keep an eye on:

• Room name
• Avatar
• Room topic – coming from dyniamic form fields in matrix, but can be anything from the plugins