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
on 2022/05/02 12:21
Change comment:
There is no comment for this version
To version 9.1
edited by Erik Bakker
on 2022/05/02 09:34
on 2022/05/02 09:34
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 - POSTContact- Hubspot1 +eMagiz Data Sink - Parent
-
... ... @@ -1,1 +1,1 @@ 1 -Main.eMagiz Store. System Connectors.WebHome1 +Main.eMagiz Store.Accelerators.WebHome - Content
-
... ... @@ -2,33 +2,31 @@ 2 2 {{container layoutStyle="columns"}} 3 3 ((( 4 4 == About == 5 -With the help of this storeitem, you caneasilyperformoperations in theHubSpotsystemwiththe helpofeMagiz.This store itemprovidesseveralflowsrelatedtostandardoperationsandthe associatedsystemmessagesoftheseoperations. All flow itemssupport OAuth2 connectivity to HubSpot’sREST API.5 +With the help of this functionality, you can sink your messages into the eMagiz data sink bucket. Once the message is stored in the eMagiz data sink bucket, you will have the option to view this message in the Manage phase. 6 6 7 -This Store item specifically is designed to write contacts to Hubspot via a POST Call. 8 - 9 9 == Documentation == 10 10 11 11 ==== 1. How to use==== 12 - Withthisstorecomponent,youcan easilysetupaconnectiontoHubSpoto performoperationswithinthe system.Aflowcan easily becopied toretrieveinformationfromanotherHubSpotendpointandthegeneralformat ofthesystemmessagedefinition acceptedbyHubSpot.10 +Once stored, eMagiz can retrieve all messages with the same ID attached during the sink action via the Manage phase. In this case, it is assumed that your eMagiz data sink is such that you can review them on the fly. Other eMagiz data sink variants are offered that required specific on-demand queries. 13 13 14 14 ==== 2. Keynotes & restrictions==== 15 15 16 -* Note that th eeMagizusermust have anappin theHubSpotnvironmentfortheOAuth2connectivity tosuccessfully connect.17 -* SomeresponsesfromHubSpotcancontainnullvalues for fieldsthatare not filledin. Thesefields are removedwithan XSLT Transformerandthen validatedagainsttheresponsesystem message. eMagiz usersshouldtakete that afterthis transformation,allattributesare transformed to Stringtypes.Thismeansthat furthertransformation isrequired,especiallywith integers,decimals,enumerations, andbooleansbeforethevalidationwiththegateway message definition.18 -* Someflowendpoints requireadditionalparameterstoretrieveorsend information tothesystem. This isannotated in therespective flows.19 -* Pleasecheck out thefollowinglinktosetuptheOAuth2.0connectionwithHubspot:[[https:~~/~~/developers.hubspot.com/docs/api/working-with-oauth?>>url:https://developers.hubspot.com/docs/api/working-with-oauth]]14 +* Note that you should think about when you want to archive your data to the eMagiz data sink. That choice determines what the impact on the functional flow is. 15 +* Don't use a wiretap to invoke this part of the flow, as that causes the sink's behavior to happen before the actual processing. If the sink fails, the message will not be delivered via the functional part of the flow. 16 +* Note that we define (among others) how the message is stored in the data sink bucket in this component. The file structure expression should not be altered, as changing this would break the functionality. 17 +* Note that the 'standard' eMagiz headers to define the source system (i.e. relevant systems) and the messageType need to be available upon sinking to make this functionality work. 20 20 21 21 ==== 3. License Information==== 22 - Part ofthestandard license agreementasagreeduponwhenusing the storeforthefirst time.20 +To use this store item you need to secure an additional license on the eMagiz platform. If you are interested in such a license please contact us at productmanagement@emagiz.com. 23 23 24 - ====4.Relevant eMagizAcademyMicrolearnings====22 +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/?]]))) 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/?]]))) 29 29 30 - 31 - 32 -((())) 26 +((((% border="2" cellpadding="10" cellspacing="10" style="width:292px" %) 27 +|=(% style="width: 45px;" %)#|=(% style="width: 241px;" %)Option 28 +|(% style="width:45px" %) a|(% style="width:241px" %) XML message(s) 29 +|(% style="width:45px" %) b|(% style="width:241px" %) JSON Message(s) 30 +))) 33 33 {{/container}} 34 34 {{/container}}