Skip to Content
Last modified by Erik Bakker on 2023/01/30 13:50
From version 45.1
edited by Erik Bakker
on 2022/05/02 13:07
Change comment: There is no comment for this version
To version 15.1
edited by Erik Bakker
on 2022/05/02 09:49
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -POST eMail - Microsoft Graph
1 +Add Namespace
Parent
... ... @@ -1,1 +1,1 @@
1 -Main.eMagiz Store.System Connectors.WebHome
1 +Main.eMagiz Store.Accelerators.WebHome
Content
... ... @@ -2,20 +2,18 @@
2 2  {{container layoutStyle="columns"}}
3 3  (((
4 4  == About ==
5 -With the help of this store item, you can easily perform operations in the Microsoft Graph system with the help of eMagiz. This store item provides several flows related to standard operations and the associated system messages of these operations. All flow items support OAuth2 connectivity to Microsoft Graph’s REST API.
5 +With the help of this transformation, you can easily add a namespace to your message. This is sometimes needed to communicate with an external system.
6 6  
7 7  == Documentation ==
8 8  
9 9  ==== 1. How to use====
10 -With this store component, you can easily set up a connection to Microsoft Graph to perform operations within the system. A flow can easily be copied to retrieve information from another Microsoft Graph endpoint and the general format of the system message definition accepted by Microsoft Graph.
10 +With the help of this transformation, you can easily add a namespace to your message. This is sometimes needed to communicate with an external system.
11 11  
12 12  ==== 2. Keynotes & restrictions====
13 13  
14 -* Note that the eMagiz user must have an app in the Azure Active Directory environment for the OAuth2 connectivity to successfully connect.
15 -* All responses from Microsoft Graph can contain null values for fields that are not filled in. These fields are removed with an XSLT Transformer and then validated against the response system message for some of the operations, but it is not compulsory to do so. eMagiz users should take note that after this transformation, all attributes are transformed to String types. This means that further transformation is required, especially with integers, decimals, and enumerations before the validation with the gateway message definition.
16 -* Some flow endpoints require additional parameters to retrieve or send information to the system. This is annotated in the respective flows.
17 -* Check out the following link for more context on the Microsoft Graph API: [[https:~~/~~/docs.microsoft.com/en-us/graph/use-the-api>>url:https://docs.microsoft.com/en-us/graph/use-the-api]]
18 -* Check out the following link for more context on the Microsoft Graph API Explorer: [[https:~~/~~/developer.microsoft.com/en-us/graph/graph-explorer>>url:https://developer.microsoft.com/en-us/graph/graph-explorer]]
14 +* Note that this is a custom XSLT that is designed for a specific cause.
15 +* Always try to understand the context before you implement this transformation.
16 +* Note that you need to define your specific namespace yourself when you want to implement this solution within your model.
19 19  
20 20  ==== 3. License Information====
21 21  Part of the standard license agreement as agreed upon when using the store for the first time.
... ... @@ -22,9 +22,9 @@
22 22  
23 23  ==== 4. Relevant eMagiz Academy Microlearnings====
24 24  
25 -[[https:~~/~~/emagiz.github.io/docs/microlearning/intermediate-rest-webservice-connectivity-index >>url:https://emagiz.github.io/docs/microlearning/intermediate-rest-webservice-connectivity-index ]]
23 +None
26 26  
27 -//Would you please consult the privacy policy of eMagiz at the following link:// [[https:~~/~~/www.emagiz.com/privacy-policy/?>>url:https://www.emagiz.com/privacy-policy/?]])))
25 +Would you please consult the privacy policy of eMagiz at the following link: [[https:~~/~~/www.emagiz.com/privacy-policy/?>>url:https://www.emagiz.com/privacy-policy/?]])))
28 28  
29 29  
30 30