It appears that the launchpad designer is not reflecting the correct catalogue/group information that is actually stored in our system, this discrepancy occurred when transporting a change from dev to QA, QA is where the problem is. Has anyone had a problem like this or know of anyway to fix this? Situation is below.
We had a custom catalog/group. It existed in both Dev and Q. We removed a tile from the catalogue/group in dev, assigned it to a transport and moved it to QA.
Accordingly, the QA users no longer see the tile, success! However when I open the launchpad designer I still see the tile in the catalogue and group. However, since this tile is not showing for the user, it means that somewhere the catalogue/group information is stored correctly (assumption, I have no idea why else it would vanish nor do I know how to actually corroborate this in on the gateway).
My hunch is that the browser based launchpad designer is somehow displayed cached information that is not longer valid. This has been further strengthened by the fact that we recently implemented a note for one of our apps and that change is not being reflected in the app, but I can see the code has been implemented on the gateway.
Steps to resolve so far:
SMICM, clear local+global cache.
Chrome->dev tools->empty cache and hard reload.
incorrect info is still displayed.
Anyone have any tips? Or does anyone know a tcode/table I can access to view the catalogue/group info directly on gateway and validate my assumption?