I have spent the day studying what I can get my hands on regarding the new App Designer and the concepts behind it. I get that it's intention is to support modularization. What I don't get is what is the main entry point for the end user? Is the intention that the default SiteMap's "My Apps" subarea is the item users click to get to the list of custom applications? That seems kind of awkward. My basic question is what role does the default SiteMap play once you have many Apps? Perhaps it would be the "common" things for the county?
Here is our implementation. I work for a local governmental entity. I have developed a fully custom case tracking and welfare payment system for our Social Services Dept (thanks to the help of many on this forum). Our SiteMap, at this juncture, only supports this one department; i.e., Social Services. Our roadmap has us expanding our Dynamics platform to embrace applications within each Department. So there could be one or more for Police, one or more for Mental Health, etc. I was excited to learn what I learned today about the core functionality of Apps, but still am a bit fuzzy on how many apps are integrated with the main Sitemap.
Thanks in advance for any clarification.
*This post is locked for comments
I have the same question (0)
