3 lines
No EOL
1.3 KiB
XML
3 lines
No EOL
1.3 KiB
XML
<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Blocked Entity on AL Guidelines</title><link>https://alguidelines.dev/navpatterns/1-patterns/blocked-entity/</link><description>Recent content in Blocked Entity on AL Guidelines</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><atom:link href="https://alguidelines.dev/navpatterns/1-patterns/blocked-entity/index.xml" rel="self" type="application/rss+xml"/><item><title>Data Driven Blocked Entity</title><link>https://alguidelines.dev/navpatterns/1-patterns/blocked-entity/data-driven-blocked-entity/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://alguidelines.dev/navpatterns/1-patterns/blocked-entity/data-driven-blocked-entity/</guid><description>Written by Bogdan Andrei Sturzoiu, at Microsoft Development Center Copenhagen
|
|
Abstract This pattern implements a generic mechanism for dynamically restricting and allowing usage of a record by the business process administrator.
|
|
Problem A NAV record can be used in a number of functionalities across the app. There are situations, however, when the administrator wants to restrict the consumption of such a record, as well as lift the restriction when it is no longer relevant.</description></item></channel></rss> |