Skip to Content

Changes for page GET Order - Exact Online

Last modified by Erik Bakker on 2023/01/30 13:35
From version 20.1
edited by Erik Bakker
on 2022/05/02 12:21
Change comment: There is no comment for this version
To version 4.1
edited by Erik Bakker
on 2022/05/02 08:17
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -POST Contact - Hubspot
1 +SOAP Web service Connectivity
Parent
... ... @@ -1,1 +1,1 @@
1 -Main.eMagiz Store.System Connectors.WebHome
1 +Main.eMagiz Store.Accelerators.WebHome
Content
... ... @@ -1,34 +1,40 @@
1 1  {{container}}
2 2  {{container layoutStyle="columns"}}
3 3  (((
4 -== About ==
5 -With the help of this store item, you can easily perform operations in the HubSpot 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 HubSpot’s REST API.
4 += About =
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 -This Store item specifically is designed to write contacts to Hubspot via a POST Call.
7 += Documentation =
8 8  
9 -== Documentation ==
9 + **~1. How to use**
10 +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.
10 10  
11 -==== 1. How to use====
12 -With this store component, you can easily set up a connection to HubSpot to perform operations within the system. A flow can easily be copied to retrieve information from another HubSpot endpoint and the general format of the system message definition accepted by HubSpot.
12 +**2. Keynotes & restrictions **
13 13  
14 -==== 2. Keynotes & restrictions====
14 +a. Note that you need to select the valid authentication based on the requirement of the external system.
15 15  
16 -* Note that the eMagiz user must have an app in the HubSpot environment for the OAuth2 connectivity to successfully connect.
17 -* Some responses from HubSpot 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, especially with integers, decimals, enumerations, and booleans before the validation with the gateway message definition.
18 -* Some flow endpoints require additional parameters to retrieve or send information to the system. This is annotated in the respective flows.
19 -* Please check out the following link to set up the OAuth 2.0 connection with Hubspot: [[https:~~/~~/developers.hubspot.com/docs/api/working-with-oauth?>>url:https://developers.hubspot.com/docs/api/working-with-oauth]]
20 -
21 -==== 3. License Information====
16 +**3. License Information**
22 22  Part of the standard license agreement as agreed upon when using the store for the first time.
23 23  
24 -==== 4. Relevant eMagiz Academy Microlearnings====
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]]
25 25  
26 -[[https:~~/~~/emagiz.github.io/docs/microlearning/intermediate-rest-webservice-connectivity-index >url:https://emagiz.github.io/docs/microlearning/intermediate-rest-webservice-connectivity-index]]
27 27  
28 -//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/?]])))
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/?]])))
29 29  
30 30  
31 31  
32 -((()))
27 +((((% border="2" cellpadding="10" cellspacing="10" style="width:292px" %)
28 +|=(% style="width: 45px;" %)#|=(% style="width: 241px;" %)Option
29 +|(% style="width:45px" %) a|(% style="width:241px" %) OAuth 2.0 - Authorization Code
30 +|(% style="width:45px" %) b|(% style="width:241px" %) REST - Basic Auth
31 +|(% style="width:45px" %) c|(% style="width:241px" %) REST - Client Certificate
32 +|(% style="width:45px" %) d|(% style="width:241px" %) REST - Header Mapper
33 +|(% style="width:45px" %) e|(% style="width:241px" %) OAuth 2.0 - Client Credentials
34 +|(% style="width:45px" %) f|(% style="width:241px" %) REST - SSL
35 +|(% style="width:45px" %) g|(% style="width:241px" %) Dynamic Token
36 +|(% style="width:45px" %) h|(% style="width:241px" %) Token
37 +|(% style="width:45px" %) i|(% style="width:241px" %) No Authentication (Fire & Forget)
38 +)))
33 33  {{/container}}
34 34  {{/container}}