formatted nav patterns

This commit is contained in:
christianbraeunlich 2022-02-05 18:19:26 +01:00
parent 38a19d75d8
commit 2fad891a77
59 changed files with 1403 additions and 1970 deletions

View file

@ -18,13 +18,15 @@ The pattern is most easily described when you look at an example. This example i
[![ ][image0]][anchor0]
The goal of this functionality is to:
• List all the different connections to external services,
• Have a central place to navigate to the corresponding setup of the service.
The goal of this functionality is to:
* List all the different connections to external services,
* Have a central place to navigate to the corresponding setup of the service.
The functionality (**Service Connections**) itself, is not aware of the state nor setup nor any context of all the different services in the list. All it does is:
• It raises an event as an opportunity for all services within the NAV application to subscribe to,
• It has a public function **InsertServiceConnection** that the subscribers can use to register itself at the Service Connection.
The functionality (**Service Connections**) itself, is not aware of the state nor setup nor any context of all the different services in the list. All it does is:
* It raises an event as an opportunity for all services within the NAV application to subscribe to,
* It has a public function **InsertServiceConnection** that the subscribers can use to register itself at the Service Connection.
The event **OnRegisterServiceConnection** is raised when the page (1279 - **Service Connections**) is opened.