Changes for page POST Calendar Event - Microsoft Graph
Last modified by Erik Bakker on 2023/01/30 13:47
From version 10.1
edited by Erik Bakker
on 2022/05/02 09:37
on 2022/05/02 09:37
Change comment:
There is no comment for this version
To version 44.1
edited by Erik Bakker
on 2022/05/02 13:06
on 2022/05/02 13:06
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -e MagizDataSink1 +POST User Account - Microsoft Graph - Parent
-
... ... @@ -1,1 +1,1 @@ 1 -Main.eMagiz Store. Accelerators.WebHome1 +Main.eMagiz Store.System Connectors.WebHome - Content
-
... ... @@ -2,35 +2,32 @@ 2 2 {{container layoutStyle="columns"}} 3 3 ((( 4 4 == About == 5 -With the help of this functionality, you can sinkyourssages intotheeMagizdatasink bucket.Oncethemessageis storedintheeMagizdatasinkbucket,youwillhave theoption toviewthis messageintheManage phase.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. 6 6 7 7 == Documentation == 8 8 9 9 ==== 1. How to use==== 10 - Oncestored,eMagizcanretrieveallmessageswiththesameIDattached duringthesink actionvia theManage phase.Inthiscase,it isassumedthatyoureMagizdatasinkissuchthat youcanreview themonthefly.OthereMagizdatasinkvariantsareofferedthatrequiredspecificon-demandqueries.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. 11 11 12 12 ==== 2. Keynotes & restrictions==== 13 13 14 -* Note that you should think about when you want to archive your data to the eMagiz data sink. That choice determines what the impact on the functional flow is. 15 -* Don't use a wiretap to invoke this part of the flow, as that causes the sink's behavior to happen before the actual processing. If the sink fails, the message will not be delivered via the functional part of the flow. 16 -* Note that we define (among others) how the message is stored in the data sink bucket in this component. The file structure expression should not be altered, as changing this would break the functionality. 17 -* Note that the 'standard' eMagiz headers to define the source system (i.e. relevant systems) and the messageType need to be available upon sinking to make this functionality work. 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]] 18 18 19 19 ==== 3. License Information==== 20 - To use this store itemyouneedto secureanadditionallicenseon the eMagiz platform.Ifyouareinterestedinsucha licensepleasecontactusatproductmanagement@emagiz.com.21 +Part of the standard license agreement as agreed upon when using the store for the first time. 21 21 22 22 ==== 4. Relevant eMagiz Academy Microlearnings==== 23 23 24 -[[https:~~/~~/emagiz.github.io/docs/microlearning/ advanced-data-management-data-sink>>url:https://emagiz.github.io/docs/microlearning/advanced-data-management-data-sink]]25 +[[https:~~/~~/emagiz.github.io/docs/microlearning/intermediate-rest-webservice-connectivity-index >>url:https://emagiz.github.io/docs/microlearning/intermediate-rest-webservice-connectivity-index ]] 25 25 26 -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/?]]))) 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/?]]))) 27 27 28 28 29 29 30 -((((% border="2" cellpadding="10" cellspacing="10" style="width:292px" %) 31 -|=(% style="width: 45px;" %)#|=(% style="width: 241px;" %)Option 32 -|(% style="width:45px" %) a|(% style="width:241px" %) XML message(s) 33 -|(% style="width:45px" %) b|(% style="width:241px" %) JSON Message(s) 34 -))) 31 +((())) 35 35 {{/container}} 36 36 {{/container}}