This commit is contained in:
JeremyVyska 2021-11-04 21:35:51 +00:00
parent c736753393
commit 3941105a09
398 changed files with 49386 additions and 129 deletions

View file

@ -0,0 +1,9 @@
<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Notifications on BC AL Help</title><link>https://microsoft.github.io/bcalhelp/navpatterns/1-patterns/notifications/</link><description>Recent content in Notifications on BC AL Help</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><atom:link href="https://microsoft.github.io/bcalhelp/navpatterns/1-patterns/notifications/index.xml" rel="self" type="application/rss+xml"/><item><title>In-context Notifications</title><link>https://microsoft.github.io/bcalhelp/navpatterns/1-patterns/notifications/in-context-notifications/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://microsoft.github.io/bcalhelp/navpatterns/1-patterns/notifications/in-context-notifications/</guid><description>__By Soumya Dutta at Microsoft Development Center Copenhagen
Context Application developers need to raise a notification on events that are not blocking but do require attention from users. Notifications alert users to issues or information, and let them decide whether to react immediately or finish what they&amp;rsquo;re doing first.
Problem Application developers have started to use system calls like CONFIRM or MESSAGE to alert or inform users about a condition. These calls interrupt users by displaying a window in the middle of the screen and forcing an immediate response.</description></item><item><title>Notification Lifecycle Management Pattern</title><link>https://microsoft.github.io/bcalhelp/navpatterns/1-patterns/notifications/notification-lifecycle-management-pattern/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://microsoft.github.io/bcalhelp/navpatterns/1-patterns/notifications/notification-lifecycle-management-pattern/</guid><description>Notification Lifecycle Management pattern
_By David Bastide at Microsoft Development Center Copenhagen _
Context
This pattern is about sending notifications in Dynamics NAV, starting with version 2018, tracking them in the Notification Lifecycle Management framework, and recalling them when needed.
Description
Notifications are easy to use in a wide range of cases. Instead of using notifications in a fire-and-forget way, we need to track them so that we can recall them if we need to.</description></item></channel></rss>