This commit is contained in:
JesperSchulz 2021-11-08 15:53:12 +00:00
parent 158b902b20
commit cb4e8e2194
131 changed files with 3191 additions and 3076 deletions

View file

@ -1,5 +1,3 @@
<?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 BC AL Help</title><link>https://bcalhelp.dev/navpatterns/1-patterns/blocked-entity/</link><description>Recent content in Blocked Entity on BC AL Help</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><atom:link href="https://bcalhelp.dev/navpatterns/1-patterns/blocked-entity/index.xml" rel="self" type="application/rss+xml"/><item><title>Data Driven Blocked Entity</title><link>https://bcalhelp.dev/navpatterns/1-patterns/blocked-entity/data-driven-blocked-entity/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://bcalhelp.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>
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>