1 - Create a cloud flow in a solution.
2 - Navigate to https://admin.powerplatform.com.
3 - Add an enviornment variable to a solution.
Topic 2, Contoso Pharmaceuticals
Current environment
Overview
Contoso Pharmaceuticals has a custom enterprise resource management (ERP) system. It is difficult to integrate other applications and services with the system. Office staff manually key in purchase orders, customer orders, and invoices after they receive a scan or hard copy of an agreement.
Applications
* The company uses a custom supplier management system named SMSApps that runs on each user's workstation. The system is costly to run and maintain. SMSApp does not have an API.
* Sales representatives manage customer requests by using Dynamics 365 Sales.
* Contoso has Microsoft Power Platform development, user acceptance testing (UAT), and production environments.
* Administrators create one Accounts Payable (AP) mailbox for each environment to support testing.
* The use of a DLP policy and Desktop Flow development is specified as part of the automation requirements.
Business process
1. Sales representatives create quotes by using a Microsoft Word document template. The template allows representatives to include product quantity, and cost estimation details that will be needed to fulfil an order. The representative converts quotes to a PDF file and emails the file to the customer for approval.
2. The sales representative alerts the finance team about the new order and emails the finance team a copy of the quote for processing.
3. The finance team prints the quote and manually creates a purchase order (PO) into SMSApp to request materials from a known and trusted vendor.
4. The SMSApp distributes the PO to stakeholders. The system sends a copy to a shared finance team mailbox.
5. Once a PO is fulfilled by a vendor, the system sends an email to the finance mailbox. The finance team releases an order to the warehouse.
6. Materials are shipped from the vendor to one of Contoso's warehouses. Warehouse workers enter key information from the waybill into SMSApp. The materials are unloaded and racked in the warehouse until they are shipped to customers.
7. Upon checking for new daily orders in SMSApp, they see an open order is pending that is awaiting the newly received materials
8. The Warehouse worker loads an order onto a truck for delivery and marks the order as complete in SMSApp.
9. Sales representatives provide fulfillment status and tracking information for orders.
10. A finance clerk prepares an invoice and sends the invoice to the customer by email. The clerk sends a copy of the email to the shared AP mailbox.
11. The AP team monitors the shared mailbox to confirm that the customer has paid the invoice.
Requirements
Functional Requirements
* Large volume orders must be processed before other orders.
* Invoices must be cross-checked with received items against packing slip for shipments.
* The finance team must be able to analyze patterns in transactional data to conduct fraud prevention activities.
* You must automate the process of entering data about incoming orders into SMSApp.
* The solution must follow the principle of least privilege.
Purchase Order Quantity flow
* You must create an unmanaged solution to update purchase order details in SMSApp. The flow must use a manual trigger.
* Members of Accounts Payable team will be testers for the solution. They must be able to access the Purchase Order Quantity flow.
Flow for processing invoice data
* You must create a flow to monitor the AP mailbox. When an invoice arrives as an attachment in the inbox, the flow must automatically process the invoice data by using a form processing model. The flow must cross-check the received items against the packing slip.
* You must use different Accounts Payable email addresses for development user acceptance testing (UAT), and production environments.
* You must use an environment variable to represent the Accounts Payable mailbox for the environment in use.
* You must be able to use the environment variable across multiple cloud flows, a custom connector, and a canvas app.
Technical Requirements
* Users must only be allowed to connect to and access systems that are required for the employee to perform required job tasks.
* All automation flows must be either co-owned or shared between staff.
* All employees must be able to access the new environment to build personal productivity automations.
* You must distribute the workload for desktop flows to optimize productivity.
Monitor flows
* All data extracted from Invoices should be stored in a custom Dataverse entity. Only employees who are part of Finance role should be able to edit all Invoice data but must be prevented from creating or deleting one.
Issues
Invoice data
All users report that they can see and modify invoice data.
New environment
* The IT department creates a new environment. A user creates a cloud flow named FlowA in the environment that triggers a desktop flow. A user reports that the cloud flow does not trigger the desktop flow to run.
* Microsoft Dataverse is not provisioned in the new environment. You attempt to create a Desktop flow in the default environment but receive a Dataverse error message and cannot proceed.
Data entry automation flow
An administrator runs a new desktop flow in the development environment to automate data entry into SMSApp. The flow automatically reverts to a suspended state.
Order fulfillment flow
You must automate the customer communication process by using an unattended desktop flow. The flow must check the fulfillment status of each active order in SMSApp. If an order is fulfilled, the flow must send the customer an email that includes tracking information for their order.
