Changes for page POST Contact - Hubspot

Summary

• Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-REST - Request & Response
	1	+eMagiz Data Sink

Content

...	...	@@ -1,33 +1,32 @@
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 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.
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
10		-Part of the standard license agreement as agreed upon when using the store for the first time.
	9	+==== 1. How to use====
	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.
11	11
12		-4. Relevant eMagiz Academy Microlearnings
13		-https://emagiz.github.io/docs/microlearning/intermediate-rest-webservice-connectivity-index
	12	+==== 2. Keynotes & restrictions====
14	14
15		- Would you please consult the privacy policy of eMagiz at the following link: https://www.emagiz.com/privacy-policy/
16		-]])))
	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.
17	17
	19	+==== 3. License Information====
	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.
18	18
	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/?]])))
19	19
	24	+
	25	+
20	20	((((% border="2" cellpadding="10" cellspacing="10" style="width:292px" %)
21	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)
	28	+|(% style="width:45px" %) a|(% style="width:241px" %) XML message(s)
	29	+|(% style="width:45px" %) b|(% style="width:241px" %) JSON Message(s)
31	31	)))
32	32	{{/container}}
33	33	{{/container}}