Skip to Content

Changes for page eMagiz Store

Last modified by Erik Bakker on 2024/08/26 11:02
From version 27.1
edited by Erik Bakker
on 2023/06/15 12:51
Change comment: There is no comment for this version
To version 28.1
edited by Erik Bakker
on 2023/06/15 13:02
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,5 +1,5 @@
1 1  {{container}}{{container layoutStyle="columns"}}(((
2 -In this fundamental, we will zoom in on the concepts of the eMagiz Store and how it can benefit our community whilst developing within the platform. Building on this fundamental we have several [[microlearnings>>doc:Main.eMagiz Academy.Microlearnings.Novice.eMagiz Store.WebHome||target="blank"]] related to the eMagiz Store that give a more in-depth explanation on the technicalities when working with the store.
2 +In this fundamental, we will zoom in on the concepts of the eMagiz Store and how it can benefit our community while developing within the platform. Building on this fundamental, we have several [[microlearnings>>doc:Main.eMagiz Academy.Microlearnings.Novice.eMagiz Store.WebHome||target="blank"]] related to the eMagiz Store that gives a more in-depth explanation of the technicalities when working with the store.
3 3  
4 4  Should you have any questions, please get in touch with academy@emagiz.com.
5 5  
... ... @@ -10,56 +10,52 @@
10 10  == 2. Key concepts ==
11 11  
12 12  * The eMagiz Store is accessible from various phases of the ILM
13 -* The eMagiz Store is designed for reusability, speed, and transfering best-practices
14 -* Generic content is maintained by eMagiz. Partners content is maintained by our partners.
15 -* The eMagiz content is divised into connectors and accelerators
13 +* The eMagiz Store is designed for reusability, speed, and transferring best-practices
14 +* EMagiz maintains generic content. Our partners maintain their content.
15 +* The eMagiz content is divided into connectors and accelerators
16 16  
17 17  == 3. eMagiz Store ==
18 18  
19 -We have designed the eMagiz Store in such a way that it supports our users whilst developing in the Design and Create phase of eMagiz in creating a working integration. Store items developed by eMagiz and by our partners focus on increasing the speed of delivery, promoting reusability across models and instilling best-practices in the hearts and minds of our users.
19 +We have designed the eMagiz Store to support our users while developing in the Design and Create phase of eMagiz in creating a functional integration. Store items developed by eMagiz and by our partners focus on increasing the speed of delivery, promoting reusability across models, and instilling best practices in the hearts and minds of our users.
20 20  
21 -The eMagiz Store currently plays host to a large number of connectors connecting to systems such as Exact Online, Salesforce, SAP, Microsoft Graph and more. On top of that we offer a wide range of accelerators that contain often used transformations, standardized connectivity methods (i.e. REST, SOAP, SFTP) and technically challenging solution that could come in handy (i.e. Groovy solutions).
21 +The eMagiz Store currently hosts many connectors connecting to systems such as Exact Online, Salesforce, SAP, Microsoft Graph, and more. On top of that, we offer a wide range of accelerators that contain often-used transformations, standardized connectivity methods (i.e., REST, SOAP, SFTP), and technically challenging solutions that could come in handy (i.e., Groovy solutions).
22 22  
23 +[[image:Main.Images.Fundamental.WebHome@fundamental-emagiz-store--benefits-overview.png]]
23 23  
24 -
25 25  === 3.1 Content Management ===
26 26  
27 -Within the eMagiz store we have two streams of content that can be publiced in the store. The first stream of content is maintained and managed by ourselves as eMagiz. This stream focuses on accelerators (i.e. store items that simplify something in Create such as calling a REST endpoint) and on generic connectors (i.e. connectors that are used in a wide variety of markets, such as Salesforce). The secondary stream of content is maintained and managed by each of our partners. As partner they have the option to export relevant content for their own customer base to the eMagiz store to further enhance the experience in using the platform and adding value faster.
27 +Within the eMagiz store, we have two streams of content that can be published. The first stream of content is maintained and managed by ourselves as eMagiz. This stream focuses on accelerators (i.e., store items that simplify something in Create, such as calling a REST endpoint) and generic connectors (i.e., connectors used in various markets, such as Salesforce). Each of our partners maintains and manages the secondary stream of content. As partners, they can export relevant content for their customer base to the eMagiz store to enhance the platform's experience and add value faster.
28 28  
29 -=== 3.2 Suggestions, Questions and Feedback ===
29 +=== 3.2 Suggestions, Questions, and Feedback ===
30 30  
31 -We can imagine that when using the store or simply browsing through what the store can offer you suggestions, questions and feedback might arise. In each of these cases we appreciate you contact us in a specific manner. In case you have suggestions for new feedback do not hesitate to contact us at [[productmanagement@emagiz.com>>mailto:productmanagement@emagiz.com]]. In case of questions please use our Q&A forum within the portal. In case of feedback you can use the feedback button in the portal to report your feedback so we can take a look at it.
31 +Suggestions, questions, and feedback might arise when using the store or simply browsing through what the store can offer you. In each of these cases, we appreciate you contacting us in a specific manner. In case you have suggestions for new feedback, do not hesitate to contact us at [[productmanagement@emagiz.com>>mailto:productmanagement@emagiz.com]]. In case of questions, please use our Q&A forum within the portal. In case of feedback, you can use the feedback button in the portal to report your feedback so we can look at it.
32 32  
33 -The first perspective on the Cloud we take is how we run multiple customers within the same eMagiz Cloud solution that we offer. The picture below shows how we structured our Cloud to ensure that your data is kept safely within your environment.
33 +The first perspective on the Cloud we take is how we run multiple customers within the same eMagiz Cloud solution that we offer. The picture below shows how we structured our Cloud to ensure your data is kept safely within your environment.
34 34  
35 35  === 3.3 Example usage ===
36 36  
37 -Within the documentation portal we have a list of connectors and accelerators that are managed and maintained by eMagiz. The list can be found [[here>>doc:Main.eMagiz Store.WebHome||target="blank"]]. On top of that we have some example videos in which we demonstrate how you can use the store to your advantage through the use of some use cases. Please check out the links below for each of these use cases:
37 +Within the documentation portal, we have a list of connectors and accelerators managed and maintained by eMagiz. The list can be found [[here>>doc:Main.eMagiz Store.WebHome||target="blank"]]. On top of that, we have some example videos in which we demonstrate how you can use the store to your advantage through some use cases. Please check out the links below for some of these use cases.
38 38  
39 -
40 40  === 3.4 Key benefits ===
41 41  
42 -Now that we have explained how our Cloud is configured, we will wrap up this fundamental by looking at the key benefits the Cloud holds for you when building your models with the help of the eMagiz platform. Below we have summarized these key benefits:
41 +Now that we have explained the eMagiz Store from a conceptual level, we will wrap up this fundamental by looking at the key benefits of the eMagiz Store within the eMagiz platform. Below we have summarized these key benefits:
43 43  
44 -* Each model has its VPC
45 -* Meta information is stored on EFS for auto-scaling purposes
46 -* Meta information is stored on EFS to guarantee a quick recovery in case of an outage
47 -* Monitoring capabilities provide auto-healing options
48 -* The eMagiz Cloud can be fully controlled via the eMagiz platform (check out our microlearnings under suggested additional readings)
49 -* A carwash is placed in front of all VPCs to add a layer of security
50 -* You can add additional features to your specific VPC
43 +* The store (items) are designed to increase speed, reusability, and the use of best-practices
44 +* Both eMagiz and partners actively maintain the content provided in the store.
45 +* Many store items are already available to kickstart your development right now.
51 51  
52 52  == 4. Key takeaways ==
53 53  
54 54  * The eMagiz Store is accessible from various phases of the ILM
55 -* The eMagiz Store is designed for reusability, speed, and transfering best-practices
56 -* Generic content is maintained by eMagiz. Partners content is maintained by our partners.
57 -* The eMagiz content is divised into connectors and accelerators
50 +* The eMagiz Store is designed for reusability, speed, and transferring best-practices
51 +* EMagiz maintains generic content. Our partners maintain their content.
52 +* The eMagiz content is divided into connectors and accelerators
58 58  
59 59  == 5. Suggested Additional Readings ==
60 60  
61 -If you are interested in this topic and want to learn how you can utilize the eMagiz Store whilst developing in the eMagiz platform, please check out our microlearnings offering on the eMagiz Store:
56 +If you are interested in this topic and want to learn how you can utilize the eMagiz Store while developing in the eMagiz platform, please check out our microlearnings offering on the eMagiz Store:
62 62  
58 +* [[Salesforce - Use case>>https://www.youtube.com/watch?v=fX22TQqkMP0||target="blank"]]
63 63  * [[Novice - eMagiz Store>>doc:Main.eMagiz Academy.Microlearnings.Novice.eMagiz Store.WebHome||target="blank"]]
64 64  
65 65  )))((({{toc/}}))){{/container}}{{/container}}