Explanation :

Box 1: Power Apps app

Customers who sign up for add-on Jamaica excursions bring friends who have not signed up ahead of time. The sales representatives record the customer information on paper, take pay ment, and then enter the information into the system later. The information is frequently inaccurate and creates discrepancies.

Box 2: Common Data Model

Dynamics 365 common data model (CDM) is designed to simplify the data integration and management across business processes and applications. Microsoft int roduced CDM as an integral part PowerApps offering.

The good news is that Dynamics 365 CDM enables apps to easily integrate and share data even without custom and extensive integration.

Note: In Jamaica, employees use SoftwareC, a homegrown application based on spreadsheets. Local sales representatives use pen and paper in the field.

New customers in Jamaica must be reviewed and approved due to frequent customer data discrepancies. The sales representatives in the field will enter information that must b e routed to validate against existing data.

Margie’s created a second company based in Jamaica, followed by the acquisition of a third company in the United Kingdom (UK).

All three countries must use Dynamics 365 Finance.

Margie’s Travel wants to enable customer self-service in the future for customers based in the US and UK.

Note:

* The CTO has learned that there are updates to globalization features in Dynamics 365 Finance. The IT staff has been tasked with ensuring that they are the first group to receive these updates.

* The IT department has decided not to code for globalization issue s because they are in an upcoming service update. They are closing in on go-live and need to make sure that the updates are applied in time.

Service updates are continuous, touchless updates that provide new features and functionality. You are in control and manage how your organization receives these updates. For example, you can sign up for the First Release program so that your organization receives updates first. You can apply the updates to any of your environments manually (self-update) or remain on the default release schedule and receive the auto-updates when you schedule them using LCS.

Margie’s Travel offers consumers a loyalty program. Consumers can earn points per dollar spent across all in countries in which Margie’s operates. The loyalty program is currently managed by using a spreadsheet.

Box 1: Corporate libraries

Note: The infrastructure team must move the code for the loyalty program to test environment.

It’s important to note that yo u can browse a Business process modeler (BPM) library that is a global library or a corporate library. However, before you can edit and work with a BPM library, it must be part of your project in Microsoft Dynamics Lifecycle Services (LCS). Libraries that are distributed by Microsoft appear under Global libraries, whereas libraries that are published by your organization appear under Corporate libraries.

Box 2: Create business process

Margie’s Travel learns that the loyalty program across multiple countrie s is not a standard industry process and is not a standard feature in Dynamics 365 Finance.

There are several ways to author a BPM library. You can do so from scratch either building directly in the client or by importing an Excel template.

Note: Once user acceptance testing (UAT ) has been completed, the project manager must report the number of tenants for production to Microsoft.

Go-live Readiness Review prerequisites

The project team should validate solution readiness. The following prerequisites must be met before the Go-live Readiness Review with Microsoft can be initiated. The production environment can be deployed after the Go-live Readiness Review with Microsoft has been successfully completed.

* User acceptance testing (UAT) and performance testing have been completed or almost completed in a Tier-2 (or higher) environment.

* The environment version that is planned for the go-live complies with the Software lifecycle policy.

* The environment version that is planned for the go-live complies with the Software lifecycle poli cy.

* All licenses that are required for go-live have been purchased in the correct tenant.

* Etc.