5
We release a new version of our application every three months and we are using Dynamics 365 as a development platform. Every release, we would need to cleanup and delete code within the "previous" versions feature callouts, and re-place the callouts in new locations, pertinent to the new features we've developed during the release. We do not want the previous release's callouts to appear for the user.

The current piecemeal approach forces us to remember everywhere we have placed a callout in the previous release, and delete it.

Since callouts are developed, placing a link to additional supporting documentation results in an awkward timing issue. We have to "pre-plan" where the callout location will point to way before the end user support documentation is completed if we want to include a "Learn more" URL.

If there was a configuration table that allowed us to pre-configure which form, and which control requires the callout, this would allow us to dynamically make the callout appear in the correct spot.

We would need information like:
- FormName
- ControlName
- CallOutTitle
- CallOutBody
- CalloutURL

Thanks for considering this item.
Category: User Experience
STATUS DETAILS
Needs Votes