Wiki source code of eMagiz Store - Introduction

Last modified by Erik Bakker on 2024/09/03 10:01

Hide last authors
Erik Bakker 1.1 1 {{container}}
2 {{container layoutStyle="columns"}}
3 (((
Carlijn Kokkeler 18.1 4 This section introduces the eMagiz Store, a powerful feature designed to streamline the development process across various phases of your integration projects. Whether you're working in the Create, Design, or Capture phases, the Store provides ready-made components and flow fragments that can be easily integrated into your workflows, saving you time and effort. We'll explore how the Store can be used in each phase, the management of Store content, and the licensing considerations for certain features.
Erik Bakker 1.1 5
Erik Bakker 6.1 6 Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]].
Erik Bakker 1.1 7
8 == 1. Prerequisites ==
9
10 * Basic knowledge of the eMagiz platform
11
12 == 2. Key concepts ==
13
Erik Bakker 5.1 14 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.
Erik Bakker 1.1 15
Erik Bakker 2.1 16 == 3. eMagiz Store - Introduction ==
Erik Bakker 1.1 17
Erik Bakker 2.1 18 === 3.1 Store for Create ===
Erik Bakker 1.1 19
Erik Bakker 5.1 20 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.
Erik Bakker 1.1 21
Erik Bakker 5.1 22 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.
Erik Bakker 1.1 23
Erik Bakker 2.1 24 === 3.2 Store for Design ===
Erik Bakker 1.1 25
Erik Bakker 5.1 26 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.
Erik Bakker 1.1 27
Erik Bakker 5.1 28 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.
Erik Bakker 1.1 29
Erik Bakker 5.1 30 * Connectivity flow fragments will be imported in exit gates, entry flow, event processors, and exit flows
31 * Processing flow fragments will be imported in exit gates, event processors, offramp flows, and onramp flows
32 * Universal flows can be imported into any flow
Erik Bakker 1.1 33
Erik Bakker 2.1 34 === 3.3 Store for Capture ===
Erik Bakker 1.1 35
Erik Bakker 5.1 36 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.
Erik Bakker 1.1 37
Erik Bakker 2.1 38 === 3.4 Content Management for Store items ===
Erik Bakker 1.1 39
Erik Bakker 5.1 40 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.
Erik Bakker 1.1 41
Erik Bakker 2.1 42 === 3.5 Licensing Store ===
Erik Bakker 1.1 43
Erik Bakker 5.1 44 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.
Erik Bakker 1.1 45
Erik Bakker 2.1 46 The disclaimer for using Store content can be found here:
Erik Bakker 1.1 47
Erik Bakker 8.1 48 == 4. Key takeaways ==
Erik Bakker 1.1 49
Erik Bakker 2.1 50 * Each phase in eMagiz holds store items that will aid you in building your solution in eMagiz
51 * eMagiz Store Content will be managed by eMagiz.
Erik Bakker 1.1 52
Erik Bakker 8.1 53 == 5. Suggested Additional Readings ==
Erik Bakker 1.1 54
Erik Bakker 19.1 55 If you are interested in this topic and want more information on it please read the help text provided by eMagiz and read the following link
56
57 * [[Fundamentals (Navigation)>>doc:Main.eMagiz Academy.Fundamentals.WebHome||target="blank"]]
58 ** [[eMagiz Store (Explanation)>>doc:Main.eMagiz Academy.Fundamentals.fundamental-emagiz-store.WebHome||target="blank"]]
Danniar Firdausy 13.1 59 * [[Crash Course (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.WebHome||target="blank"]]
60 ** [[Crash Course API Gateway (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course API Gateway.WebHome||target="blank"]]
61 *** [[Setting up Exit gate (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course API Gateway.crashcourse-api-gateway-setting-up-exit-gate||target="blank"]]
Carlijn Kokkeler 16.1 62 * [[Novice (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Novice.WebHome||target="blank"]]
63 ** [[eMagiz Store (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Novice.eMagiz Store.WebHome||target="blank"]]
Carlijn Kokkeler 17.1 64 *** [[Importing Store Items - Design Phase (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Novice.eMagiz Store.novice-emagiz-store-importing-store-items-design.WebHome||target="blank"]]
65 *** [[Merge Store Data Model (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Novice.eMagiz Store.novice-emagiz-store-merge-store-data-model.WebHome||target="blank"]]
66 *** [[Selecting Store Items - Create (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Novice.eMagiz Store.novice-emagiz-store-selecting-store-items.WebHome||target="blank"]]
67 *** [[Importing Store Items - Create (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Novice.eMagiz Store.novice-emagiz-store-importing-store-items.WebHome||target="blank"]]
68 *** [[Configuring Store Items (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Novice.eMagiz Store.novice-emagiz-store-configuring-store-items.WebHome||target="blank"]]
Erik Bakker 19.1 69 * [[eMagiz Store Offerings (Menu)>>doc:Main.eMagiz Store.WebHome||target="blank"]]
70 ** [[Accelerators (Navigation)>>doc:Main.eMagiz Store.Accelerators.WebHome||target="blank"]]
71 ** [[Store Connectors (Navigation)>>doc:Main.eMagiz Store.System Connectors.WebHome||target="blank"]]
72 * [[eMagiz Store (Search Result)>>url:https://docs.emagiz.com/bin/view/Main/Search?sort=score&sortOrder=desc&highlight=true&facet=true&r=1&f_space_facet=0%2FMain.&f_type=DOCUMENT&f_locale=en&f_locale=&f_locale=en&text=%22emagiz+store%22||target="blank"]]
Erik Bakker 1.1 73
Danniar Firdausy 13.1 74 )))
75
Erik Bakker 1.1 76 ((({{toc/}}))){{/container}}
77 {{/container}}