manuelap-msft
commented
1 year ago Thanks for the feedback!
It's not on our roadmap to implement this, mostly because
- Not all customers use all the parts of the CoE kit and with one app it'd be difficult to enable customers to adopt different parts of the CoE kit at their own pace
- For admins, we often see organizations split responsibilities between different personas (e.g. a Support Admin that looks after Inactivity/Orphan clean up, an InfoSec admin that looks after compliance) and they would experience a very noisy and busy app if everything was in one
- Especially for admins, the app would be very busy and likely suffer performance issues
However, as we have now moved to mainly using custom pages (aside from a few apps that are still missing the re-design but are on our backlog), it would be very easy to implement a "one" app approach yourself. You could create a new model driven app and add all our custom pages and table views to the navigation and group it the way you'd like to use it. This should be quite simple, and would also work for future upgrades etc.
I'll add this to our documentation backlog, so we can document this step by step in our "extend the CoE kit" article.
bhavikj65
CoEStarterKitBot
Is your feature request related to a problem? Please describe.
No response
Describe the solution you'd like
Since the CoE kit is built on Dataverse, I believe that having a single app for Makers and a distinct app for Admins would be preferable to having many apps for various use cases. like Command cetner, Inactivity, DLP, Developer compliance etc.
One app for makers and another for administrators will make it more cost-effective since it's challenging to distribute these applications with a sizable community of makers, especially in business contexts, and because all of these apps are premium and require licencing.
Describe alternatives you've considered
N/A
Additional context?
No response