Changes for page GET Order - Exact Online
Last modified by Erik Bakker on 2023/01/30 13:35
From version 28.1
edited by Erik Bakker
on 2022/05/02 12:37
on 2022/05/02 12:37
Change comment:
There is no comment for this version
To version 19.1
edited by Erik Bakker
on 2022/05/02 12:15
on 2022/05/02 12:15
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 - POST Order- Salesforce1 +Add CDATA - Parent
-
... ... @@ -1,1 +1,1 @@ 1 -Main.eMagiz Store. System Connectors.WebHome1 +Main.eMagiz Store.Accelerators.WebHome - Content
-
... ... @@ -2,20 +2,17 @@ 2 2 {{container layoutStyle="columns"}} 3 3 ((( 4 4 == About == 5 -With the help of this store item, you can easilyperform operationsintheSalesforcesystemwiththehelp of eMagiz. This storeitem providesseveral flows related tostandardoperationsand theassociated system messages of these operations. Allflowitemssupport OAuth2 connectivity to Salesforce’s REST API.5 +With the help of this transformation, you can easily wrap the body of your message in CDATA tags. This is sometimes needed to call an external web service. 6 6 7 7 == Documentation == 8 8 9 9 ==== 1. How to use==== 10 -With th is storecomponent, you can easily set upa connectionto Salesforce to performoperationswithin the system. A flowcan easilybe copiedto retrieveinformationfromanotherSalesforceendpointandthe generalformat of thesystemmessagedefinitionaccepted by Salesforce.10 +With the help of this transformation, you can easily wrap the body of your message in CDATA tags. This is sometimes needed to call an external web service. 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 +* 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. 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,7 +22,7 @@ 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]]22 +None 26 26 27 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/?]]))) 28 28