Changes for page Business case

Last modified by Erik Bakker on 2023/05/01 10:46
From version 5.1
edited by eMagiz
on 2023/04/03 13:49
Change comment: There is no comment for this version
To version 10.1
edited by Eva Torken
on 2023/04/20 10:50
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.eMagiz
1 +XWiki.etorken
Content
... ... @@ -1,6 +1,7 @@
1 -{{container}}{{container layoutStyle="columns"}}(((
2 -With this exercise, we start our journey into the eMagiz platform. This exercise will explain the business case used throughout all exercises linked to the Crash Course Platform Course. In the following exercises, we will guide you step by step through the platform so you can learn how to use it.
3 -
1 +{{container}}
2 +{{container layoutStyle="columns"}}(((
3 +With this exercise, we start our journey into the eMagiz platform. This exercise will explain the business case used throughout all exercises linked to this Crash Course. In the following exercises, we will guide you step by step through the platform so you can learn how to use it.
4 +
4 4  Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]].
5 5  
6 6  == 1. Prerequisites ==
... ... @@ -15,18 +15,14 @@
15 15  
16 16  **Read and understand the following business case**
17 17  
18 -As eMagiz Ltd. we want to directly receive & send information from/to three internal systems responsible for the primary process. It concerns the FMS (Financial Management System) that handles the invoicing of eMagiz Ltd, the OMS (Order Management system) that handles the Orders that are incoming from clients and lastly a service that translates ISO code from countries. eMagiz Ltd. has decide to expose API operation to their clients so that the message traffic is standardized and less manual intervention is required for the backoffice. See below for specifications per system.
19 +As eMagiz Ltd. we want to directly receive & send information from/to an internal system responsible for the primary process. It concerns the OMS (Order Management system) that handles the Orders that are incoming from clients. eMagiz Ltd. has decide to expose API operation to their clients so that the message traffic is standardized and less manual intervention is required for the backoffice. See below for specifications.
19 19  
20 -* FMS
21 - ** Retrieve Invoice Information. Objective is to let clients fetch invoices and understand the status of these invoices.
22 22  * OMS
23 - ** Retrieve carrier information. This information is relevant to understand what color the truck is where the order is placed on.
22 + ** Retrieve carrier information. This information is relevant to understand what color the truck is on which the order is placed.
24 24   ** Send order. Clients can directly submit orders to eMagiz Ltd. in a digital manner
25 -* Country Validator
26 - ** Retrieve ISO3 code. This service can translate ISO-2 codes to ISO-3 codes and vice versa. eMagiz trades with clients internationally.
27 27  
28 -
29 -== 3. Solution ==
25 +eMagiz Ltd. has two large clients that would start to use these operations. ACME requires the ability to submit orders, retrieve invoices and carriers. Street Smart requires access to all operations. Both clients can work with API keys for authentication purposes.
30 30  
31 31  
32 -)))((({{toc/}}))){{/container}}{{/container}}
28 +)))((({{toc/}}))){{/container}}
29 +{{/container}}