Changes for page Cleanup a captured integration

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-Importing Store Items - Design Phase
	1	+novice-emagiz-store-importing-store-items-design

Content

...	...	@@ -14,60 +14,48 @@
14	14
15	15	== 2. Key concepts ==
16	16
17		-This microlearning centers around importing store items in the Design Phase. With eMagiz Store, we mean A content library available to the community to select re-usable solutions within the eMagiz platform.
	17	+The eMagiz Store is a concept in the eMagiz platform that allows users to import reusable content into a specific ILM phase. The Store has elements for each of the model phases Capture, Design, and Create, and is focused on expediting the delivery of integrations for users.
18	18
19		-* To import a store item in Design, you need to follow the import wizard
20		-* When importing in Design, you can import the system message and accompanying flow fragments
	19	+== 3. eMagiz Store - Introduction ==
21	21
22		-== 3. Importing Store Items - Design Phase ==
	21	+=== 3.1 Store for Create ===
23	23
24		-In contrast with the Create phase store items (which provide you a set of components to achieve a particular objective), the Design Phase store items give you the additional functionality to import the system message(s). For example, to import a system message from the Store in Design, you must navigate to the system message via the context menu. When doing so for the first time, eMagiz will show you the following options after entering the "Start Editing" mode.
	23	+The eMagiz store for the Create phase allows users to drag & drop flow fragments into the flow that requires editing. A flow fragment is a combination of 1 or more model components that together can execute a certain piece of work inside that flow. For example, a file pickup that includes an archive option and specific file filters. Or the required components that are needed to send a message to a REST/JSON web service that is secured with OAuth2.0.
25	25
26		-[[image:Main.Images.Microlearning.WebHome@novice-emagiz-store-importing-store-items-design--import-options-system-message.png]]
	25	+The Store for the Create phase can be found in the left-hand panel of the Flow designer - at the same location as where you select the model components.
27	27
28		-When you select the option Store, eMagiz will show you all alternatives within the eMagiz store to which a Message Definition is linked. Note that you can search by Name and by Brand in this overview.
	27	+=== 3.2 Store for Design ===
29	29
30		-[[image:Main.Images.Microlearning.WebHome@novice-emagiz-store-importing-store-items-design--store-overview-design.png]]
	29	+The eMagiz store for the Design phase allows selecting specific operations from available systems such as Exact online, or Salesforce. So these are more datamodel-oriented items and more target/source system oriented. The general idea is that you import store content whilst defining your data model message and System definitions. At that moment, you can select to import one or more message definitions. eMagiz will then guide the user to import the system message definition, as well as to import the mapping between the data model and message definition. A reusable merge definition can be created between the existing data model (CDM, Gateway model, or Event model) and the system definition so that the data model can be updated in a proper way.
31	31
32		-Once you have found the item of your liking, you can select it by clicking on it. This action will lead you to the details page associated with the store item. Here you will find the relevant information related to this store item. On top of that, we provide you with a Versions & Variants tab that shows you all existing versions you could import.
	31	+Please note that when the Store item is selected in this phase, the associated flow fragments for the Create phase are automatically attached to the integration. That means when the integration is transferred to Create these flow fragments will automatically be generated into the appropriate flows. eMagiz considers putting these flow fragments into the right flow depending on the type of flow fragment.
33	33
34		-[[image:Main.Images.Microlearning.WebHome@novice-emagiz-store-importing-store-items-design--information-store-item-after-selection.png]]
	33	+* Connectivity flow fragments will be imported in exit gates, entry flow, event processors, and exit flows
	34	+* Processing flow fragments will be imported in exit gates, event processors, offramp flows, and onramp flows
	35	+* Universal flows can be imported into any flow
35	35
36		-In cases where you want the latest version use the button titled "Use latest version" on the Information tab. Once you have selected a version, eMagiz will show the following step of the process. Here you can choose whether you want to import the message definition(s), and it will ask you whether you wish to select accompanying flow fragments which are of use later on in Create. Since it is a GET operation, we only have a response definition to import. On top of that, we have two flow fragments. One that handles the authentication and one that holds the logic of the store item.
	37	+=== 3.3 Store for Capture ===
37	37
38		-[[image:Main.Images.Microlearning.WebHome@novice-emagiz-store-importing-store-items-design--making-choices-on-the-store-item.png]]
	39	+The eMagiz Store will be expanded to the Capture phase in upcoming quarters. The current idea is to allow the selection of systems and integrations on level up so that the work on Design and Create becomes even easier. Once we have made that step, we'll update this section with the right positioning.
39	39
40		-It is up to you what you exactly want to import. Maybe only the definition is enough for you, or perhaps you want the whole package. So here you have the choice to do so. Once you are satisfied with your selection, press "Use message(s)." This will start the import process. As a result, eMagiz will import the model on the canvas and define the system message(s) in the right panel.
	41	+=== 3.4 Content Management for Store items ===
41	41
42		-[[image:Main.Images.Microlearning.WebHome@novice-emagiz-store-importing-store-items-design--import-result-in-design.png]]
	43	+At this moment, the Store content is provided by the eMagiz team only. The concept of a company or private store is under consideration, and for now, intra-company content can be moderated by the Copy-Paste functionality in the Create phase. Suggestions for new content can be sent to [[productmanagement@emagiz.com>>mailto:productmanagement@emagiz.com]] / questions can be asked via the QA forum which may include feedback on a store item.
43	43
44		-Now you should create the mapping from your data model to the system message(s) yourself, and when you are finished, you can transfer the solution to Create just as you are used to doing.
	45	+=== 3.5 Licensing Store ===
45	45
46		-=== 3.1 Importing Design Store Item - Effect in Create ===
	47	+Store content can be imported by any user except for store items that are licensed. For instance, the Data Sink is a licensed feature, and the Store item for Data Sink can only be imported in case this license is granted in the integration model.
47	47
48		-Once you have transferred the solution to the Create phase and open the relevant flow for which you have imported the store item, you will see a "Pending configuration" button on the bottom of your canvas.
	49	+The disclaimer for using Store content can be found here:
49	49
50		-[[image:Main.Images.Microlearning.WebHome@novice-emagiz-store-importing-store-items--pending-configuration.png]]
51		-
52		-After pressing this button, you will see a pop-up showing all flow fragments to import. You can select each flow fragment separately by pressing the Setup button. Note that if you want to configure this at a later moment, you can choose the option "Do this later" and come back later to finish the job. On top of that, you can press Cancel if you change your mind and don't want to import the flow fragments.
53		-
54		-[[image:Main.Images.Microlearning.WebHome@novice-emagiz-store-importing-store-items--importing-flow-fragments.png]]
55		-
56		-When pressing this, eMagiz will show you the import wizard. This configuration wizard finishes the import process.
57		-
58		-[[image:Main.Images.Microlearning.WebHome@novice-emagiz-store-importing-store-items--configuration-wizard.png]]
59		-
60		-For all the details on this wizard, please check out the following microlearning.
61		-
62	62	== 4. Assignment ==
63	63
64		-Import a Store item in Design to import the system message(s) and subsequently transfer it to Create to see how to import the pending configurations. This assignment can be completed with the help of the (Academy) project that you have created/used in the previous assignment.
	53	+There is no assignment for this microlearning. Please refer to the next microlearning in this module so that you can experience it properly.
65	65
66	66	== 5. Key takeaways ==
67	67
68		-* To import a store item in Design, you need to follow the import wizard
69		-* When importing in Design, you can import the system message and accompanying flow fragments
70		-* After importing the system message in Design, you can configure the flow fragments in Create with the help of the button called "Pending configurations."
	57	+* Each phase in eMagiz holds store items that will aid you in building your solution in eMagiz
	58	+* eMagiz Store Content will be managed by eMagiz.
71	71
72	72	== 6. Suggested Additional Readings ==
73	73
...	...	@@ -75,7 +75,7 @@
75	75
76	76	== 7. Silent demonstration video ==
77	77
78		-{{video attachment="novice-emagiz-store-importing-store-items-design.mp4" reference="Main.Videos.Microlearning.WebHome"/}})))
	66	+There is no demonstration video of this functionality.)))
79	79
80	80	((({{toc/}}))){{/container}}
81	81	{{/container}}