Explanation

Explanation

Box 1: Data loss prevention policy
Data loss prevention (DLP) policies enforce rules for which connectors can be used together by classifying connectors as either Business or Non-Business. If you put a connector in the Business group, it can only be used with other connectors from that group in any given app or flow. Sometimes you might want to block the usage of certain connectors altogether by classifying them as Blocked.
Box 2: Security group
If your company has multiple Microsoft Dataverse environments, you can use security groups to control which licensed users can be a member of a particular environment.
Reference:
https://docs.microsoft.com/en-us/power-platform/admin/wp-data-loss-prevention
https://docs.microsoft.com/en-us/power-platform/admin/control-user-access

Explanation

Box 1: Omnichannel for Customer Service dashboard
Scenario: Workers must be able to communicate in near real-time with worker support agents.
The company has a team or worker support agents that respond to inquiries from current and prospective workers. Some of the worker support agents are multilingual.
If you choose to expand your customer service offering to provide chat and channels, the Customer Service workspace seamlessly adjusts to support managing conversations as well.
Note: As an agent with the Customer Service Representative security role, when you open Customer Service workspace, you start on the Customer Service Agent Dashboard unless your administrator has changed the default view. This dashboard shows you your active cases, cases you can work in queues you are assigned to, and your open activities. You can open existing cases and activities or begin working new cases from the queues you are assigned to and create activities.
Box 2: Dynamics 365 Customer Service
Scenario: First Up uses an on-premises system to manage current and historical patient data including medications and medical visits.
Reference:
https://docs.microsoft.com/en-us/dynamics365/customer-service/csw-overview

Reference:
https://docs.microsoft.com/en-us/powerapps/maker/data-platform/data-platform-entity-lookup
Topic 2, Relecloud
To start the case study
To display the first question in this case study, click the Next button. Use the buttons in the left pane to explore the content of the case study before you answer the questions. Clicking these buttons displays information such as business requirements, existing environment, and problem statements. If the case study has an All Information tab, note that the information displayed is identical to the information displayed on the subsequent tabs. When you are ready to answer a question, click the Question button to return to the question.
Background
Relecloud provides regional air service in North America. The company uses a variety of systems, apps, and services to manage the business. You are hired to design a new solution to manage passenger information, reservations, and maintenance.
Current environment
The company uses Microsoft Office 365.
The company has a custom app for managing and tracking passenger luggage. The app uses Microsoft Dataverse.
For flights longer than four hours, passengers receive a meal. Customers can select a meal when they make a reservation and can save the meal choices as a customer preference.
The company offers two types of meals: standard and vegetarian. Meal types can be temporarily unavailable. The airline is considering offering other meal types, such as gluten-free and low-sodium options.
The company uses paper-based reservation checklists to help ensure that all the steps for a reservation are complete.
The company uses vendors to service aircraft.
Environment
Ensure that employees can sign in to all Microsoft apps by using one set of credentials per employee.
Minimize the use of third-party products and custom development.
Reduce customer support call volumes by having the system automatically resolve common issues.
The security rule for agents must contain the privileges in the default Customer Service Representative security role.
Log issues as cases. The case form must show variable sections based on the case type. Include a custom entity named Seats and grant agents access to the entity.
Application use layout should be role specific.
Agents
You must standardize the format used by agents to enter customer phone numbers.
Agents need a solution to replace paper reservation checklists.
Agents need dashboards to show a current count of all reservations on the entity.
Agents need a way to track reservation issues.
Agents need a visual indicator in the interface to determine the reservation step to provide a seamless customer experience.
Agents need different versions of cancellation policies to send customers. One version must be controllable within the system.
Agents need to view which pieces of luggage match to each passenger, and then need to add the total on the passenger record.
IT
IT staff needs a mobile solution to see IT cases at the top of the menu since this is their primary focus.
IT staff needs a system that is easy to navigate to active cases.
IT specialists want to design Power BI reports. They need to understand the underlying table relationships of the system.
IT specialists need a solution that is visual rather than text-based so they can quickly complete their tasks.
Management
Management requires paginated reports for stakeholders.
Management wants to provide frequent flyers with better service when the flyers call.
Managers need to see all customer dashboards at the top of their menu on their mobile device.
Maintenance
Maintenance supervisors must not have access to Dynamics 365 Customer Service. The supervisors must be able to communicate with the contracts team about contracts.
Aircraft maintenance vendors must have only view and upload privileges to their invoices and receipts.
Contracts with maintenance companies must be stored in Dynamics 365 Customer Service.

You can help ensure that people enter data consistently and follow the same steps every time they work with a customer by creating a business process flow. For example, you might want to create a business process flow to have everyone handle customer service requests the same way, or to require that people get approval for an invoice before submitting an order. Business process flows use the same underlying technology as other processes, but the capabilities that they provide are very different from other features that use processes.
Reference:
https://docs.microsoft.com/en-us/power-automate/business-process-flows-overview