We are happy to announce that we just released a set of improvements to Catalogues and Channel Maps, by refactoring how the save functionality works!

To improve data sync—especially when common fields or catalog mappings change, we now send data directly to the components (i.e. a pop up, a save action etc.) that need it. This makes the process faster and simpler. In other words, this means each component can be treated separately, giving us more flexibility and allowing for more careful handling of behaviours (and bug solving).

Here's the problem we wanted to solve

The previous catalogue save functionality lacked control over specific changes, leading to several problems. All components relied on a single data source for catalogue information. Consequently, any modification was triggering a global update, making it impossible to identify the exact changes. This was causing a set of (smaller & medium) issues, for example the difficulty of assigning specific pop ups only to catalogue or only to maps.

Here's why this is important

This enhanced implementation not only delivers the immediate benefits of improved efficiency and reduced complexity in the catalogue save functionality but also establishes a significantly more robust and adaptable foundation for the ongoing development and deployment of future features and releases. By addressing the current limitations and streamlining the underlying architecture, this refactoring creates a more scalable and maintainable system that can readily accommodate anticipated growth and evolving business requirements. This proactive approach will minimize potential technical debt and facilitate a smoother, more agile development process moving forward.

Here's how you benefit

For you, the main benefit is a more stable and reliable experience across the catalogue and Channel Maps features. You might notice the improvement right away—especially if you've previously encountered odd or inconsistent behaviour— or you may simply find that things run more smoothly. This change also sets a stronger foundation for future improvements and feature development.