Changes for page GET Invoice - SAP S/4HANA
Last modified by Erik Bakker on 2023/01/30 13:43
From version 4.1
edited by Erik Bakker
on 2022/05/02 08:17
on 2022/05/02 08:17
Change comment:
There is no comment for this version
To version 5.1
edited by Erik Bakker
on 2022/05/02 08:20
on 2022/05/02 08:20
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -7,17 +7,17 @@ 7 7 = Documentation = 8 8 9 9 **~1. How to use** 10 - With thisstorecomponent, youcaneasilysetup aconnection to a REST endpoint usingvarious authenticationmechanismswhiletakingthe responseinto account.10 +Ensure to locate the right connectivity method and import the right flow fragment. 11 11 12 12 **2. Keynotes & restrictions ** 13 13 14 -a. Note thatyouneedto select thevalidauthenticationbased onherequirement ofthe external system.14 +a. These flow fragments will contain only the eMagiz components to make a call out to the SOAP based webservice - These components do not hold any system messages - The basic authentication flow fragment requires empty key and trust store that are to be added separately. These are not included in this store component. 15 15 16 16 **3. License Information** 17 17 Part of the standard license agreement as agreed upon when using the store for the first time. 18 18 19 19 **4. Relevant eMagiz Academy Microlearnings** 20 -[[https:~~/~~/emagiz.github.io/docs/microlearning/ intermediate-rest-webservice-connectivity-index>>url:https://emagiz.github.io/docs/microlearning/intermediate-rest-webservice-connectivity-index]]20 +[[https:~~/~~/emagiz.github.io/docs/microlearning/novice-soap-webservice-connectivity-authorization-calling-a-soap-webservice>>url:https://emagiz.github.io/docs/microlearning/novice-soap-webservice-connectivity-authorization-calling-a-soap-webservice]] 21 21 22 22 23 23 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/?]]))) ... ... @@ -26,15 +26,15 @@ 26 26 27 27 ((((% border="2" cellpadding="10" cellspacing="10" style="width:292px" %) 28 28 |=(% style="width: 45px;" %)#|=(% style="width: 241px;" %)Option 29 -|(% style="width:45px" %) a|(% style="width:241px" %) OAuth2.0 -AuthorizationCode30 -|(% style="width:45px" %) b|(% style="width:241px" %) REST-BasicAuth31 -|(% style="width:45px" %) c|(% style="width:241px" %) REST -ClientCertificate32 -|(% style="width:45px" %) d|(% style="width:241px" %) REST- HeaderMapper33 -|(% style="width:45px" %) e|(% style="width:241px" %) OAuth 2.0 - ClientCredentials34 -|(% style="width:45px" %) f|(% style="width:241px" %) REST -SSL35 -|(% style="width:45px" %) g|(% style="width:241px" %) Dynamic Token36 -|(% style="width:45px" %) h|(% style="width:241px" %) Token37 -|(% style="width:45px" %) i|(% style="width:241px" %) No Authentication(Fire & Forget)29 +|(% style="width:45px" %) a|(% style="width:241px" %) Basic Authentication 30 +|(% style="width:45px" %) b|(% style="width:241px" %) WS Addressing - Call back 31 +|(% style="width:45px" %) c|(% style="width:241px" %) Client certificate 32 +|(% style="width:45px" %) d|(% style="width:241px" %) Mapped headers 33 +|(% style="width:45px" %) e|(% style="width:241px" %) Token based - static 34 +|(% style="width:45px" %) f|(% style="width:241px" %) Token based - dynamic 35 +|(% style="width:45px" %) g|(% style="width:241px" %) SSL 36 +|(% style="width:45px" %) h|(% style="width:241px" %) No authentication 37 +|(% style="width:45px" %) i|(% style="width:241px" %) Dynamic URL 38 38 ))) 39 39 {{/container}} 40 40 {{/container}}