Changes for page GET Invoice - SAP S/4HANA
Last modified by Erik Bakker on 2023/01/30 13:43
From version 27.1
edited by Erik Bakker
on 2022/05/02 12:36
on 2022/05/02 12:36
Change comment:
There is no comment for this version
To version 8.1
edited by Erik Bakker
on 2022/05/02 09:31
on 2022/05/02 09:31
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 - POSTTask - Salesforce1 +SOAP Web service Connectivity - Parent
-
... ... @@ -1,1 +1,1 @@ 1 -Main.eMagiz Store. System Connectors.WebHome1 +Main.eMagiz Store.Accelerators.WebHome - Content
-
... ... @@ -2,32 +2,40 @@ 2 2 {{container layoutStyle="columns"}} 3 3 ((( 4 4 == About == 5 - Withthe help of this storeitem,you can easilyperform operationsintheSalesforcesystemwith thehelp of eMagiz. Thisstoreitem providesseveralflows related to standardoperationsand theassociatedsystem messagesoftheseoperations.Allflow items supportOAuth2connectivity toSalesforce’sRESTAPI.5 +This store element will allow you to create an easy connection to SOAP based web services. XML data can be send to these web services, and for each connectivity type there is a Flow Fragment available. 6 6 7 7 == Documentation == 8 8 9 9 ==== 1. How to use==== 10 - With thisstorecomponent, youcan easily set up a connection to Salesforceto performoperations withinthesystem. A flowcanasily becopiedto retrieveinformationfromanother Salesforce endpointandthe general formatofthesystemmessage definitionaccepted by Salesforce.10 +Ensure to locate the right connectivity method and import the right flow fragment. 11 11 12 12 ==== 2. Keynotes & restrictions==== 13 13 14 -* Note that the eMagiz user must have an app in the Salesforce environment for the OAuth2 connectivity to successfully connect. 15 -* All responses from Salesforce 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. eMagiz users should take note that after this transformation, all attributes are transformed to String types. This means that further transformation is required before passing the gateway message validation. Especially Integers, Decimals, and Enumerations should be transformed, but also Booleans and other non-string types. 16 -* All decimal values should be converted to doubles or floats. Salesforce returns all decimal values with exponents. For example, the field AnnualRevenue might be 52.E03, which is only allowed by xs:double or xs:float. 17 -* To obtain fields using a GET HTTP method for operations like Accounts, Invoices, etc., the eMagiz user must specify a SOQL query in the HTTP Outbound Gateway in the flow. An example is given in each flow, although it is advised to limit the number of rows you want to retrieve from the API. 18 -* Check out the following link for more context on the OAuth2.0 protocol in relation to Salesforce: [[https:~~/~~/developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/intro_oauth_and_connected_apps.htm>>url:https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/intro_oauth_and_connected_apps.htm]] 14 +* These flow fragments will contain only the eMagiz components to make a call to a SOAP based webservice. 15 +* 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. 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 22 23 23 ==== 4. Relevant eMagiz Academy Microlearnings==== 21 +[[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]] 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]] 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/?]])))24 +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 31 -((())) 28 +((((% border="2" cellpadding="10" cellspacing="10" style="width:292px" %) 29 +|=(% style="width: 45px;" %)#|=(% style="width: 241px;" %)Option 30 +|(% style="width:45px" %) a|(% style="width:241px" %) Basic Authentication 31 +|(% style="width:45px" %) b|(% style="width:241px" %) WS Addressing - Call back 32 +|(% style="width:45px" %) c|(% style="width:241px" %) Client certificate 33 +|(% style="width:45px" %) d|(% style="width:241px" %) Mapped headers 34 +|(% style="width:45px" %) e|(% style="width:241px" %) Token based - static 35 +|(% style="width:45px" %) f|(% style="width:241px" %) Token based - dynamic 36 +|(% style="width:45px" %) g|(% style="width:241px" %) SSL 37 +|(% style="width:45px" %) h|(% style="width:241px" %) No authentication 38 +|(% style="width:45px" %) i|(% style="width:241px" %) Dynamic URL 39 +))) 32 32 {{/container}} 33 33 {{/container}}