| title | description | author | manager | ms.date | ms.topic | ms.prod | ms.service | ms.technology | ms.author | audience | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|
|
|
|
article |
business-applications |
|
|
[!includebanner]
Describe the new feature, and then give an elevator pitch of the business value for it. Include high-value capabilities that light up something exciting for our customers. The feature should be something that a customer needs to plan for...definitely larger than a hotfix or bug fix.
If the feature has been designated as a key feature, complete the entire template. Otherwise, only complete the Business value, Describe the feature, and Status sections.
Describe the top capabilities of the feature and and the business problems it solves.
Example End-of-day processing is a crucial element of retail operational workflow. This involves aggregation of raw transactions into meaningful business data to ensure that business and accounting rules are conformed to, before posting transactions as official business records. Improving the reliability and performance of this batch process and increasing the visibility of the processing for the administrator improves the user experience. Users can easily monitor the progress of the processing and see exactly what caused a validation failure. As a result, they can quickly resolve the issue and reliably retry the process without contacting Microsoft Support.
Describe how the feature works and the scenarios the feature enables. Include concrete examples and screenshots.
Example New capabilities include improved statement posting performance by removing table deadlocks and optimizing batch processing. The introduction of a state model in the posting process aids in rollback and recovery, which eliminates data corruption and the need for manual intervention. Enhanced in-app diagnostics with detailed status, errors, and logs (including details of transactions included in the scope of the statement, transactions resulting in errors, and possible steps to correct issues) allow for easy troubleshooting.
<>
Indicate each persona impacted: end user, admin, customizer, citizen developer, developer, business analyst, IT Pro
Example This feature is intended for retail administrators. It works without any additional setup.
List the license(s) a customer must have to use the feature.
Example This feature must be enabled in System parameters by an administrator.
Example To get started with model‑driven apps, use designers to:
- Define your site map. Model your app's navigation, pulling in only the subset of information your users need. Take advantage of multiple levels of hierarchy and the ability to reference external resources.
- Add dashboards. Include model‑driven dashboards or embedded Power BI content within your app.
- Include entities and components. Add specific forms, views, dashboards, and charts for targeted entities to craft your user experience.
List any compliance, privacy and security considerations that customers should plan for, including any steps or tools provided to help customers comply with GDPR.
Pick one: Generally available, Public preview, In development
Notes: In development features are features that some teams may have previously included on the roadmap site. Anything in Private preview is considered to be In development.
Enter the release, month, or month or later if dubious. (Release if committed to a release, Month if committed to a month, Month or later if dubious)
Cloud, On-premises, Government cloud
List whether this feature is available globally or restricted to specific regions.
Include an alias or link for feedback for the feature.
Link to item from Ideas or User voice.