Business case

Version 7.1 by eMagiz on 2023/04/03 13:52

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.

Should you have any questions, please contact academy@emagiz.com.

1. Prerequisites

2. Exercise

To kickstart your journey into the eMagiz platform, we have selected a set of exercises linked to the Crash Course Platform course that will guide you through the platform in building and validating your first integration. To start things off, we will introduce the business case in this exercise that will be used to model out the correct solution in eMagiz.

2.1 Business Case

Read and understand the following business case

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.
  

  • FMS
    • Retrieve Invoice Information. Objective is to let clients fetch invoices and understand the status of these invoices.
  • OMS
    • Retrieve carrier information. This information is relevant to understand what color the truck is where the order is placed on. 
    • Send order. Clients can directly submit orders to eMagiz Ltd. in a digital manner
  • Country Validator
    • Retrieve ISO3 code. This service can translate ISO-2 codes to ISO-3 codes and vice versa. eMagiz trades with clients internationally.

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.