Search: "business"

This exercise will explain the business case used throughout all exercises linked to this Crash Course.

Prerequisites == * Have read the business case as the first exercise * Completed the previous microlearnings of this crash course == 2.

With manage, we mean: Stay in control of which alerting tags are used within your project and what they mean * Make tags descriptive in nature * Differentiate who requested the tag (Business, Support, Standard) * Remove tags that are not linked to a trigger anymore == 3.

There are three key aspects you should take into account when managing your alerting tags: * Make tags descriptive in nature * Differentiate who requested the tag (Business, Support, Standard) * Remove tags that are not linked to a trigger anymore To manage your alerting tags you navigate to Manage -> Alerting -> Tags === 3.1 Make tags descriptive in nature === The beneficial nature of having the option to tag certain triggers within alerting is that the tag tells you and those you work with why that specific tag is chosen to be linked to a trigger.

Key takeaways == * There are three key aspects you should take into account when managing your alerting tags: * Make tags descriptive in nature * Differentiate who requested the tag (Business, Support, Standard) * Remove tags that are not linked to a trigger anymore == 6.

Exercise == The goal of the exercise is to fill in the Capture phase of your model based on the provided information in the business case. To fill in Capture you need to define the systems, integrations, information, and tags based on the provided information. To correctly fill in Capture you need the following definitions as they are provided to you as part of the business case. * [[Order definition CAPE>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.order-definition-cape.WebHome||target="blank"]] * [[Order definition TMS>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.order-definition-tms.WebHome||target="blank"]] {{info}}Note that you should save the contents of the file as an XSD and attach it to each of the lines drawn in Capture{{/info}} == 3.

This exercise will explain the business case used throughout all exercises linked to this Crash Course.

Prerequisites == * Have read the business case as the first exercise * Completed the previous microlearnings of this crash course == 2.

These are things to discuss in the triangle business, eMagiz Developer and Architect. * Data providers & consumers - The first thing to discuss is who will provide data and who will consume the data.

The definitions require a business perspective around the interpretation and use in the business process at hand

This exercise will explain the business case used throughout all exercises linked to this Crash Course.

Prerequisites == * Have read the business case as the first exercise * Completed the previous microlearnings of this crash course == 2.

Many transformations take place through discussions with business owners or by reviewing business documentation.

By the end, you will understand the pros and cons of each pattern and how to make an informed decision based on both business and technical factors. Should you have any questions, please get in touch with [[academy@emagiz.com>>mailto:academy@emagiz.com]]. == 1.

The answer is a series of checks and balances that look both at the business and technical aspects. === 3.1 Checks and balances === At first, look at the business side of your integration scenario before delving into the technical disqualifiers. You should ask the first question: **Does the business process require a real-time response (for both success and error messages)?

We’ll cover how to monitor and evaluate partition sizes in the Manage phase to ensure that your configurations align with your business needs. Understanding these metrics helps optimize storage and performance for your event streaming setup.

Understanding whether the design size is sufficient to serve the business process for which the topic was created is relevant. If there is insufficient partition size, it could mean that some messages are deleted too early and not considered for the business process. Furthermore, there are limits to partition size in the eMagiz Cloud.

* *Add comment* Interact with the requestor via Comments * *Subscribe* Receive email updates about interactions on a specific question ==== 3.1.3 Turn around times ==== The eMagiz team is dedicated to answering these questions within the same business day unless answered earlier by other Community users. ===3.2 Incidents=== If you have an issue with your instance blocking the use of the platform and some deadlines result in pressure to resolve it faster, you need to register an incident in our eMagiz Support Portal.

* The eMagiz team is dedicated to responding to questions within the same business day * The eMagiz team is continuously evaluating your feedback and tries its best to resolve issues at our discretion == 5.