Today, I noticed three different activation/deactivation methods in DW, which could probably be more streamlined.
In Data Integration mappings you click on the green or red circle, which reveals a popup, where you then need to click the menu to activate/deactivate:
In the query editor you also have a green/red circle, but clicking it (or rather, clicking the row) opens the sidebar, where you can not interact with activate/deactivate. You need to lick the three dots button, which reveals a context menu you can use to activate/deactivate:
In Assortments, again you have the circles but clicking it means clicking the row, which opens assortment setup page. From here, you can click on "Edit" in "Information to open the screen, where you can toggle the "Active" checkbox:
From the overview you can also click the three dots button go directly to the Edit screen.
It's petty stuff, I admit, but a one-click toggle button with be great, and a uniform way of operating backend controls would be an improvement, especially when we have a uniform way of building the backend UI.
Today, I noticed three different activation/deactivation methods in DW, which could probably be more streamlined.
In Data Integration mappings you click on the green or red circle, which reveals a popup, where you then need to click the menu to activate/deactivate:
In the query editor you also have a green/red circle, but clicking it (or rather, clicking the row) opens the sidebar, where you can not interact with activate/deactivate. You need to lick the three dots button, which reveals a context menu you can use to activate/deactivate:
In Assortments, again you have the circles but clicking it means clicking the row, which opens assortment setup page. From here, you can click on "Edit" in "Information to open the screen, where you can toggle the "Active" checkbox:
From the overview you can also click the three dots button go directly to the Edit screen.
It's petty stuff, I admit, but a one-click toggle button with be great, and a uniform way of operating backend controls would be an improvement, especially when we have a uniform way of building the backend UI.