Currently we are able to see where a module or process is used on a Dashboard. We need to have a similar ability for the NUX which warns or stops you deleting an object if it is referenced on a Page or App.
Currently, the App is quite a separate entity from the model and is nothing to indicate the relationships between modules and actions using as starting point the classic interface.
As above also have been mentioning it is crucial to see if a module or action is "Used in Dashboard" as this is not now filled in. And also if a Module are used in a action.
I would also like the possibility to have a "saved view - overview".
In the saved view overview I would like to see if all of the saved views in one place and see if they are used in a process/Export(Action) or in a dashborad. I would also prefer if I could change name or delete them from the same overview.
I remember the time we didn't have the 'Used in Dashboards' column - then it was a challenge to clean-up the model from old modules/action and it took hours of dedicated work. Now we have this problem again - we all know how important to keep the model clean, but it's always a big risk to delete smth in use. Hope, this will be in roadmap in the nearest future.
Please please add this functionality. We are currently transitioning over to the NUX and we have definitely run into this issue a few times where we wanted to update a module but weren't sure where it was being referenced in the NUX.
Yes, we all strive to apply best practices of making our solutionsPerformant and only have modules /line items that areNecessary (fromPLANS）。随着团队的开发，有时会构建一个模块，但随后未使用。我们希望经常审查该模型，并丢弃不再使用的模块/订单项。鉴于我们的模型可以很大，许多模块和页面，因此仍然不容易看到哪些模块和页面。当然，我们将应用ALM并在部署到产品之前测试任何删除，但是我们真的担心我们会使用模块错过某些页面。这种“使用的模块/动作”可见性对于我们遵循计划并安全维护我们的模型至关重要。
I agree, this functionality is needed and would be highly valuable. For an enterprise-scale deployment, having the ability to easily trace back to the base module is crucial.
As someone who spends most of my time diagnosing issues in models and NUX pages, the ability to have traceability for modules being used in UX pages the same way we have it for model references and dashboards would made troubleshooting so much easier.
I want to revive this. As Anaplan grows in larger organizations, this is rapidly becoming essential. The amount of time spent triangulating which modules are used where is approaching critical thresholds on projects. This would save time and expense and allow for drastically easier maintenance.
