Skip to Content

Changes for page GET Order - Exact Online

Last modified by Erik Bakker on 2023/01/30 13:35
From version 2.1
edited by Erik Bakker
on 2022/04/29 15:18
Change comment: There is no comment for this version
To version 27.1
edited by Erik Bakker
on 2022/05/02 12:36
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -REST - Request & Response
1 +POST Task - Salesforce
Parent
... ... @@ -1,1 +1,1 @@
1 -Main.eMagiz Store.Accelerators.WebHome
1 +Main.eMagiz Store.System Connectors.WebHome
Content
... ... @@ -1,33 +1,33 @@
1 1  {{container}}
2 2  {{container layoutStyle="columns"}}
3 -(((1. How to use
4 -With this store component, you can easily set up a connection to a REST endpoint using various authentication mechanisms while taking the response into account.
3 +(((
4 +== About ==
5 +With the help of this store item, you can easily perform operations in the Salesforce 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 Salesforce’s REST API.
5 5  
6 -2. Keynotes & restrictions
7 -Note that you need to select the valid authentication based on the requirement of the external system.
7 +== Documentation ==
8 8  
9 -3. License Information
9 +==== 1. How to use====
10 +With this store component, you can easily set up a connection to Salesforce to perform operations within the system. A flow can easily be copied to retrieve information from another Salesforce endpoint and the general format of the system message definition accepted by Salesforce.
11 +
12 +==== 2. Keynotes & restrictions====
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]]
19 +
20 +==== 3. License Information====
10 10  Part of the standard license agreement as agreed upon when using the store for the first time.
11 11  
12 -4. Relevant eMagiz Academy Microlearnings
13 -https://emagiz.github.io/docs/microlearning/intermediate-rest-webservice-connectivity-index
23 +==== 4. Relevant eMagiz Academy Microlearnings====
14 14  
15 - Would you please consult the privacy policy of eMagiz at the following link: https://www.emagiz.com/privacy-policy/
16 -]])))
25 +[[https:~~/~~/emagiz.github.io/docs/microlearning/intermediate-rest-webservice-connectivity-index>>url:https://emagiz.github.io/docs/microlearning/intermediate-rest-webservice-connectivity-index]]
17 17  
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/?]])))
18 18  
19 19  
20 -((((% border="2" cellpadding="10" cellspacing="10" style="width:292px" %)
21 -|=(% style="width: 45px;" %)#|=(% style="width: 241px;" %)Option
22 -|(% style="width:45px" %) a|(% style="width:241px" %) OAuth 2.0 - Authorization Code
23 -|(% style="width:45px" %) b|(% style="width:241px" %) REST - Basic Auth
24 -|(% style="width:45px" %) c|(% style="width:241px" %) REST - Client Certificate
25 -|(% style="width:45px" %) d|(% style="width:241px" %) REST - Header Mapper
26 -|(% style="width:45px" %) e|(% style="width:241px" %) OAuth 2.0 - Client Credentials
27 -|(% style="width:45px" %) f|(% style="width:241px" %) REST - SSL
28 -|(% style="width:45px" %) g|(% style="width:241px" %) Dynamic Token
29 -|(% style="width:45px" %) h|(% style="width:241px" %) Token
30 -|(% style="width:45px" %) i|(% style="width:241px" %) No Authentication (Fire & Forget)
31 -)))
30 +
31 +((()))
32 32  {{/container}}
33 33  {{/container}}