Free PL-500 Exam Dumps Preview

Contoso Pharmaceuticals

Background

Contoso Pharmaceuticals distributes specialty pharmaceuticals, ingredients, and raw materials throughout North America. The company has 33 offices and 12 warehouses across the US, Mexico, and Canada. As their customers' needs grow in sophistication, Contoso wants to delight customers with breakthrough products, exceptional service, and on-time delivery of materials. They want to automate time consuming and manual processes that are prone to error. Contoso wants to consolidate and automate ordering and fulfillment processes.

1. The company has a fleet of 500 delivery trucks. The company has 150 drivers and uses third-party contractors to deliver goods.
2. The company has 400 warehouse workers and 30 finance clerks.
3. Contoso has 85 sales representatives and 50 customer service representatives. Sales representatives spend most of their time on the road visiting customers or prospects.
4. The IT department consists of four system administrators and six system analysts.

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
1. 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.
2. Sales representatives manage customer requests by using Dynamics 365 Sales.
3. Contoso has Microsoft Power Platform development, user acceptance testing (UAT), and production environments.
4. Administrators create one Accounts Payable (AP) mailbox for each environment to support testing.
5. The use of a DLP policy and Desktop Flow development is specified as part of the automation requirements.

Security

You assign all users one or more Microsoft Dataverse security roles.

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 teamprints 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
1. Large volume orders must be processed before other orders.
2. Invoices must be cross-checked with received items against packing slip for shipments.
3. The finance team must be able to analyze patterns in transactional data to conduct fraud prevention activities.
4. You must automate the process of entering data about incoming orders into SMSApp.
5. The solution must follow the principle of least privilege.

Purchase Order Quantity flow
1. You must create an unmanaged solution to update purchase order details in SMSApp.The flow must use a manual trigger.
2. 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
1. 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.
2. You must use different Accounts Payable email addresses for development user acceptance testing (UAT), and production environments.
3. You must use an environment variable to represent the Accounts Payable mailbox for the environment in use.
4. You must be able to use the environment variable across multiple cloud flows, a custom connector, and a canvas app.

Technical requirements
1. Users must only be allowed to connect to and access systems that are required for the employee to perform required job tasks.
2. All automation flows must be either co-owned or shared between staff.
3. All employees must be able to access the new environment to build personal productivity automations.
4. You must distribute the workload for desktop flows to optimize productivity.
5. A DLP policy must be created and applied to the Development environment. Connectors required by the data entry automation flow must be added to the policy.

Order fulfillment flow
You must automate the customer communication process by using an unattended desktop flow. The flow must check the fulfilment 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.

Monitor flows
1. All data extracted from Invoices should be stored in a custom Dataverse table.
2. You must assign users from the finance to the Finance business unit. You must add these users to a new security role named Finance.
3. Finance users must be prevented from creating or deleting invoice records.
4. All users must be able to view invoices.

Issues
Invoice data
All users report that they can see and modify invoice data.
New environment
1. The IT department creates a new environment that includes Microsoft Dataverse. An employee reports operational issues in Power Platform Admin center.
2. A user switch to the new environment and creates a cloud flow named FlowA that triggers a desktop flow. The user reports that the cloud flow does not trigger the desktop flow to run.
3. A user attempts to create a Desktop flow in the default environment. A Dataverse error message displays.

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
The warehouse team observers that the order fulfillment flow has stopped working. Orders are flowing into SMSApp but customers do not receive tracking emails. A system administrator is troubleshooting the flow on the target machine.

Background

First Up Consultants is a professional services organization headquartered in Europe, with offices in North America. The company supports small-to medium-sized and enterprise organizations with a range of information technology, project management change management, and finance management consultancy needs. The organization employs 500 full-time consultants and engages with over 1,000 external contractors to support the delivery of its various projects.

Current environment

The company has been using Microsoft Power Platform for several years and currently has the following implemented:

- A model-driven app named Project Planning Application that is used by the project management office
(PMO) team within the company to plan, schedule and collate information for each client project. The application supports the following functionality areas:

o Storage for project-level information, such as start date, end date and client data.

o A series of inputs to capture detailed information for statements of work as part of a standard document format. This information is manually entered by the PMO team.

o Information regarding internal and external consultants is stored within a custom table called Resources

o Information within the Resources table regarding full-time consultants is typically populated manually by the PMO team. For external consultants, the company regularly attends industry events and collates business cards for potential new employees or external contractors. Information regarding these individuals is then manually entered into the application. The PMO team then asks suitable candidates to complete an application form in Microsoft Word standard format and upload it via a secure URL. Again, the PMO team then manually enters the data into Project Planning Application.

- A canvas app named Time Entry Application is used by the employees and external contractors to
capture the time worked on projects. The application has been configured with the following defined controls:

o dpStartDate: A date picker control to indicate the start date of the lime entry.

° dpEndOate: A date picker control to indicate the end date of the time entry.

o inptDescription: A control used to indicate the type of activity and project worked on.

- A mobile app stories the current use's email address as part of a variable called varUserName

The company uses Microsoft SharePoint on premises to store all sensitive documents.

Company policy mandates that all client-related documents are stored within this environment only.

The company uses SAP as its back-end accounting system. The company maintains separate SAP systems in each legal jurisdiction where it is based. The system is relied upon for the following critical business processes:

- External contractors working on a project send their invoices to a dedicated mailbox that is monitored by
the company's accounting team. The accounting team must then manually process these invoices into SAP at the end of each month. Due to the number of external contractors, hundreds of invoices must be processed monthly.

- Basic API access for the SAP system is provided via a mixture of native application APIs and a
middleware Simple Object Access Protocol (SOAP) API hosted on premises. The middleware API supports the ability to post time entries against the relevant projects in any SAP system by specifying the system and client ID as a query parameter in the URL. The middleware API was developed several years ago. and the source code is no longer available. Data is returned in XML format, which can then be analyzed further.

- When a project enters the closure phase, members of the PMO team need to navigate to SAP. enter
some details, and then capture information from a PDF that is generated and opened on the screen, such as the final settlement amount. This information is then manually entered into Project Planning Application.

The company maintains a separate system containing detailed profile information regarding internal employees. The PMO team currently manually enters information from this system into the Resources table. Developers in the company have created a modem REST API for this system, which is actively maintained. The system contains highly sensitive personal information (PI) regarding each employee.

The company has several on-premises Windows environments that it has identified as suitable for usage because they exist within the same physical network as SAP and the middleware API. These environments must be patched regularly, and all activities targeting these environments must be automated.

Project Planning Application

- Rather than manually populating the statement of work information, users should plate it in a SharePoint
folder for this information to be extracted and mapped to the correct inputs.

- A new automation is required to integrate with the profile information system. Because the company
plans to consume this data in several ways, a streamlined mechanism for working with the API is required to improve reusability.

- An automation is required to handle the project closure steps in SAP and to store the relevant information
from SAP into the app.

- Once a new candidate uploads a completed application form, information from the form should be copied
automatically into Project Planning Application.

Time Entry Application

- Time Entry Application needs to be extended to integrate alongside SAP. ensuring postings for time
entries are processed successfully. When a time entry is submitted, the entry should be posted automatically to SAP.

- Time entries must always be submitted with relevant text that indicates the type of activity and project
worked on.
- The automation should be able to detect and handle any errors that occur when posting individual time
entries.

Invoice Processing

- Invoices sent to the account's mailbox must be processed automatically and created as invoices within
SAP.

General

- Development efforts should be avoided or mitigated when there is native functionality already available.

- Reusability of components is desired to assist citizen developers in creating any solutions in future.

- All automation activities should run without disruption during an outage or a patching cycle.

- Use of username and password credentials should be avoided.

- Automations should not rely on human intervention to execute.

- Use of public cloud file services should be restricted.

- Where possible. ISON should be the preferred format when transferring data.

Issues

- Users within the PMO team report that it takes many hours to put the data from each business card into
the system.

- You create the automation to process the time entries, called Submit Time Entry, and add it to the
application. Users report issues with the formula used to connect to the automation.

- During a monthly patch cycle. IT support team members cannot identify the correct steps to patch the
machine without disrupting any automation.

- While performing an audit of the new solution during the test phase, the company's information security
team identifies that users can freely save client confidential documents to OneDrive for Business.

- When creating the automation for the project closure process, you discover that some of the required
information needs to be exported via the SAP GUI and extracted from a comma-separated value (CSV) file.

- When building the automation for the profile information system, you identify that all requests into the API
will fail unless the following HTTP header value is specified;

o Accept: application/son

Contoso Pharmaceuticals

Background

Contoso Pharmaceuticals distributes specialty pharmaceuticals, ingredients, and raw materials throughout North America. The company has 33 offices and 12 warehouses across the US, Mexico, and Canada. As their customers' needs grow in sophistication, Contoso wants to delight customers with breakthrough products, exceptional service, and on-time delivery of materials. They want to automate time consuming and manual processes that are prone to error. Contoso wants to consolidate and automate ordering and fulfillment processes.

1. The company has a fleet of 500 delivery trucks. The company has 150 drivers and uses third-party contractors to deliver goods.
2. The company has 400 warehouse workers and 30 finance clerks.
3. Contoso has 85 sales representatives and 50 customer service representatives. Sales representatives spend most of their time on the road visiting customers or prospects.
4. The IT department consists of four system administrators and six system analysts.

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
1. 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.
2. Sales representatives manage customer requests by using Dynamics 365 Sales.
3. Contoso has Microsoft Power Platform development, user acceptance testing (UAT), and production environments.
4. Administrators create one Accounts Payable (AP) mailbox for each environment to support testing.
5. The use of a DLP policy and Desktop Flow development is specified as part of the automation requirements.

Security

You assign all users one or more Microsoft Dataverse security roles.

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 teamprints 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
1. Large volume orders must be processed before other orders.
2. Invoices must be cross-checked with received items against packing slip for shipments.
3. The finance team must be able to analyze patterns in transactional data to conduct fraud prevention activities.
4. You must automate the process of entering data about incoming orders into SMSApp.
5. The solution must follow the principle of least privilege.

Purchase Order Quantity flow
1. You must create an unmanaged solution to update purchase order details in SMSApp.The flow must use a manual trigger.
2. 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
1. 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.
2. You must use different Accounts Payable email addresses for development user acceptance testing (UAT), and production environments.
3. You must use an environment variable to represent the Accounts Payable mailbox for the environment in use.
4. You must be able to use the environment variable across multiple cloud flows, a custom connector, and a canvas app.

Technical requirements
1. Users must only be allowed to connect to and access systems that are required for the employee to perform required job tasks.
2. All automation flows must be either co-owned or shared between staff.
3. All employees must be able to access the new environment to build personal productivity automations.
4. You must distribute the workload for desktop flows to optimize productivity.
5. A DLP policy must be created and applied to the Development environment. Connectors required by the data entry automation flow must be added to the policy.

Order fulfillment flow
You must automate the customer communication process by using an unattended desktop flow. The flow must check the fulfilment 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.

Monitor flows
1. All data extracted from Invoices should be stored in a custom Dataverse table.
2. You must assign users from the finance to the Finance business unit. You must add these users to a new security role named Finance.
3. Finance users must be prevented from creating or deleting invoice records.
4. All users must be able to view invoices.

Issues
Invoice data
All users report that they can see and modify invoice data.
New environment
1. The IT department creates a new environment that includes Microsoft Dataverse. An employee reports operational issues in Power Platform Admin center.
2. A user switch to the new environment and creates a cloud flow named FlowA that triggers a desktop flow. The user reports that the cloud flow does not trigger the desktop flow to run.
3. A user attempts to create a Desktop flow in the default environment. A Dataverse error message displays.

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
The warehouse team observers that the order fulfillment flow has stopped working. Orders are flowing into SMSApp but customers do not receive tracking emails. A system administrator is troubleshooting the flow on the target machine.

Background

First Up Consultants is a professional services organization headquartered in Europe, with offices in North America. The company supports small-to medium-sized and enterprise organizations with a range of information technology, project management change management, and finance management consultancy needs. The organization employs 500 full-time consultants and engages with over 1,000 external contractors to support the delivery of its various projects.

Current environment

The company has been using Microsoft Power Platform for several years and currently has the following implemented:

- A model-driven app named Project Planning Application that is used by the project management office
(PMO) team within the company to plan, schedule and collate information for each client project. The application supports the following functionality areas:

o Storage for project-level information, such as start date, end date and client data.

o A series of inputs to capture detailed information for statements of work as part of a standard document format. This information is manually entered by the PMO team.

o Information regarding internal and external consultants is stored within a custom table called Resources

o Information within the Resources table regarding full-time consultants is typically populated manually by the PMO team. For external consultants, the company regularly attends industry events and collates business cards for potential new employees or external contractors. Information regarding these individuals is then manually entered into the application. The PMO team then asks suitable candidates to complete an application form in Microsoft Word standard format and upload it via a secure URL. Again, the PMO team then manually enters the data into Project Planning Application.

- A canvas app named Time Entry Application is used by the employees and external contractors to
capture the time worked on projects. The application has been configured with the following defined controls:

o dpStartDate: A date picker control to indicate the start date of the lime entry.

° dpEndOate: A date picker control to indicate the end date of the time entry.

o inptDescription: A control used to indicate the type of activity and project worked on.

- A mobile app stories the current use's email address as part of a variable called varUserName

The company uses Microsoft SharePoint on premises to store all sensitive documents.

Company policy mandates that all client-related documents are stored within this environment only.

The company uses SAP as its back-end accounting system. The company maintains separate SAP systems in each legal jurisdiction where it is based. The system is relied upon for the following critical business processes:

- External contractors working on a project send their invoices to a dedicated mailbox that is monitored by
the company's accounting team. The accounting team must then manually process these invoices into SAP at the end of each month. Due to the number of external contractors, hundreds of invoices must be processed monthly.

- Basic API access for the SAP system is provided via a mixture of native application APIs and a
middleware Simple Object Access Protocol (SOAP) API hosted on premises. The middleware API supports the ability to post time entries against the relevant projects in any SAP system by specifying the system and client ID as a query parameter in the URL. The middleware API was developed several years ago. and the source code is no longer available. Data is returned in XML format, which can then be analyzed further.

- When a project enters the closure phase, members of the PMO team need to navigate to SAP. enter
some details, and then capture information from a PDF that is generated and opened on the screen, such as the final settlement amount. This information is then manually entered into Project Planning Application.

The company maintains a separate system containing detailed profile information regarding internal employees. The PMO team currently manually enters information from this system into the Resources table. Developers in the company have created a modem REST API for this system, which is actively maintained. The system contains highly sensitive personal information (PI) regarding each employee.

The company has several on-premises Windows environments that it has identified as suitable for usage because they exist within the same physical network as SAP and the middleware API. These environments must be patched regularly, and all activities targeting these environments must be automated.

Project Planning Application

- Rather than manually populating the statement of work information, users should plate it in a SharePoint
folder for this information to be extracted and mapped to the correct inputs.

- A new automation is required to integrate with the profile information system. Because the company
plans to consume this data in several ways, a streamlined mechanism for working with the API is required to improve reusability.

- An automation is required to handle the project closure steps in SAP and to store the relevant information
from SAP into the app.

- Once a new candidate uploads a completed application form, information from the form should be copied
automatically into Project Planning Application.

Time Entry Application

- Time Entry Application needs to be extended to integrate alongside SAP. ensuring postings for time
entries are processed successfully. When a time entry is submitted, the entry should be posted automatically to SAP.

- Time entries must always be submitted with relevant text that indicates the type of activity and project
worked on.
- The automation should be able to detect and handle any errors that occur when posting individual time
entries.

Invoice Processing

- Invoices sent to the account's mailbox must be processed automatically and created as invoices within
SAP.

General

- Development efforts should be avoided or mitigated when there is native functionality already available.

- Reusability of components is desired to assist citizen developers in creating any solutions in future.

- All automation activities should run without disruption during an outage or a patching cycle.

- Use of username and password credentials should be avoided.

- Automations should not rely on human intervention to execute.

- Use of public cloud file services should be restricted.

- Where possible. ISON should be the preferred format when transferring data.

Issues

- Users within the PMO team report that it takes many hours to put the data from each business card into
the system.

- You create the automation to process the time entries, called Submit Time Entry, and add it to the
application. Users report issues with the formula used to connect to the automation.

- During a monthly patch cycle. IT support team members cannot identify the correct steps to patch the
machine without disrupting any automation.

- While performing an audit of the new solution during the test phase, the company's information security
team identifies that users can freely save client confidential documents to OneDrive for Business.

- When creating the automation for the project closure process, you discover that some of the required
information needs to be exported via the SAP GUI and extracted from a comma-separated value (CSV) file.

- When building the automation for the profile information system, you identify that all requests into the API
will fail unless the following HTTP header value is specified;

o Accept: application/son

City Power and Light

Background

City Power and Light is one of the biggest energy companies in North America. They extract, produce and transport oil. The company has more than 50 offices and 100 oil extraction facilities throughout the United States, Canada, and Mexico. They use railways, trucks, and pipelines to move oil and gas from their facilities.

The company provides the following services:
1. Produce oil from oil sands safely, responsibly, and reliably
2. Refine crude oil into high-quality products
3. Develop and manage wind power facilities.
4. Transport oil to different countries/regions.
5. City Power and Light uses various Microsoft software products to manage its daily activities and run its machine-critical applications.

Requirements
ManagePipelineMaintenanceTasks
A user named Admin1 creates a cloud flow named ManagePipelineMaintenanceTasks.
Admin1 applies a data loss prevention (DLP) policy to the flow. Adminlshares the flow with a user named PipelineManager1 as co-owner. You must determine the actions that PipelineManager can perform.

MaintenanceScheduler
You create a cloud flow that uses a desktop flow. The desktop flow connects to third-party services to fetch information. You must not permit the desktop flow to run for more than 20 minutes.

You must configure sharing for MatinenanceScheduler to meet the following requirements:
1. User1 must be able to work with you to modify the desktop flow.
2. User2 must be able to access and review the run history for the flow.
3. You must grant User3 permissions to run but not modify the desktop flow.

ERPDataOperations flow
City Power and light uses an enterprise resource planning (ERP) system. The ERP system does not have an API.
Each day the company receives an email that contains an attachment. The attachment lists orders from the company's rail transportation partners. You must create an automation solution that reads the contents of the email and writes records to the ERP system. The solution must pass credentials from a cloud flow to a desktop flow.

RailStatusUpdater
City Power and Light actively monitors all products in transit. You must create a flow named RailStatusUpdater that manages communications with railways that transport the company's products.
RailStatusUpdater includes five desktop flow actions.
You must run the desktop flows in attended mode during testing. You must run the desktop flows in unattended mode after you deploy the solution. You must minimize administrative efforts.

Packaging
You must package the automations in a solution. All required components must be included in the solution.

Issues
ProductionMonitor flow
You create a cloud flow named ProductionMonitor which uses the Manually trigger a flow trigger. You plan to trigger ProductionMonitor from a cloud flow named ProdManager.
You add a Run a Child flow action in ProdManager to trigger ProductionMonitor. When you attempt to save ProdManager the following error messaqe displays:

Request to XRM API failed with error: 'Message:Flow client error returned with status code "Bad request"

and details "("error":
{"code":ChildFlowUnsupportedForinvokerConnections", "message": The workflow with id 8d3bcde7-7e98-
eb11-b1ac-000d3a32d53f", named FlowA cannot be used as a child workflow because child workflows
only support embedded connections. "}}"Code" 0x80060467 InnerError.'

CapacityPlanning flow
Developers within the company use cloud flows to access data from an on-premises capacity planning system.
You observe significant increases to the volume of traffic that the on-premises data gateway processes each day. You must minimize gateway failures.

DataCollector flow
You have a desktop flow that interacts with a web form. The flow must write data to several fields on the form.
You are testing the flow. The flow fails when attempting to write data to any field on the web form.

RailStatusUpdater flow
The RailStatusUpdater flow occasionally fails due to machine connection errors. You can usually get the desktop flow to complete by resubmitting the cloud flow run. You must automate the retry process to ensure that you do not need to manually resubmit the cloud flow when machine connection errors occur.

Background

First Up Consultants is a professional services organization headquartered in Europe, with offices in North America. The company supports small-to medium-sized and enterprise organizations with a range of information technology, project management change management, and finance management consultancy needs. The organization employs 500 full-time consultants and engages with over 1,000 external contractors to support the delivery of its various projects.

Current environment

The company has been using Microsoft Power Platform for several years and currently has the following implemented:

- A model-driven app named Project Planning Application that is used by the project management office
(PMO) team within the company to plan, schedule and collate information for each client project. The application supports the following functionality areas:

o Storage for project-level information, such as start date, end date and client data.

o A series of inputs to capture detailed information for statements of work as part of a standard document format. This information is manually entered by the PMO team.

o Information regarding internal and external consultants is stored within a custom table called Resources

o Information within the Resources table regarding full-time consultants is typically populated manually by the PMO team. For external consultants, the company regularly attends industry events and collates business cards for potential new employees or external contractors. Information regarding these individuals is then manually entered into the application. The PMO team then asks suitable candidates to complete an application form in Microsoft Word standard format and upload it via a secure URL. Again, the PMO team then manually enters the data into Project Planning Application.

- A canvas app named Time Entry Application is used by the employees and external contractors to
capture the time worked on projects. The application has been configured with the following defined controls:

o dpStartDate: A date picker control to indicate the start date of the lime entry.

° dpEndOate: A date picker control to indicate the end date of the time entry.

o inptDescription: A control used to indicate the type of activity and project worked on.

- A mobile app stories the current use's email address as part of a variable called varUserName

The company uses Microsoft SharePoint on premises to store all sensitive documents.

Company policy mandates that all client-related documents are stored within this environment only.

The company uses SAP as its back-end accounting system. The company maintains separate SAP systems in each legal jurisdiction where it is based. The system is relied upon for the following critical business processes:

- External contractors working on a project send their invoices to a dedicated mailbox that is monitored by
the company's accounting team. The accounting team must then manually process these invoices into SAP at the end of each month. Due to the number of external contractors, hundreds of invoices must be processed monthly.

- Basic API access for the SAP system is provided via a mixture of native application APIs and a
middleware Simple Object Access Protocol (SOAP) API hosted on premises. The middleware API supports the ability to post time entries against the relevant projects in any SAP system by specifying the system and client ID as a query parameter in the URL. The middleware API was developed several years ago. and the source code is no longer available. Data is returned in XML format, which can then be analyzed further.

- When a project enters the closure phase, members of the PMO team need to navigate to SAP. enter
some details, and then capture information from a PDF that is generated and opened on the screen, such as the final settlement amount. This information is then manually entered into Project Planning Application.

The company maintains a separate system containing detailed profile information regarding internal employees. The PMO team currently manually enters information from this system into the Resources table. Developers in the company have created a modem REST API for this system, which is actively maintained. The system contains highly sensitive personal information (PI) regarding each employee.

The company has several on-premises Windows environments that it has identified as suitable for usage because they exist within the same physical network as SAP and the middleware API. These environments must be patched regularly, and all activities targeting these environments must be automated.

Project Planning Application

- Rather than manually populating the statement of work information, users should plate it in a SharePoint
folder for this information to be extracted and mapped to the correct inputs.

- A new automation is required to integrate with the profile information system. Because the company
plans to consume this data in several ways, a streamlined mechanism for working with the API is required to improve reusability.

- An automation is required to handle the project closure steps in SAP and to store the relevant information
from SAP into the app.

- Once a new candidate uploads a completed application form, information from the form should be copied
automatically into Project Planning Application.

Time Entry Application

- Time Entry Application needs to be extended to integrate alongside SAP. ensuring postings for time
entries are processed successfully. When a time entry is submitted, the entry should be posted automatically to SAP.

- Time entries must always be submitted with relevant text that indicates the type of activity and project
worked on.
- The automation should be able to detect and handle any errors that occur when posting individual time
entries.

Invoice Processing

- Invoices sent to the account's mailbox must be processed automatically and created as invoices within
SAP.

General

- Development efforts should be avoided or mitigated when there is native functionality already available.

- Reusability of components is desired to assist citizen developers in creating any solutions in future.

- All automation activities should run without disruption during an outage or a patching cycle.

- Use of username and password credentials should be avoided.

- Automations should not rely on human intervention to execute.

- Use of public cloud file services should be restricted.

- Where possible. ISON should be the preferred format when transferring data.

Issues

- Users within the PMO team report that it takes many hours to put the data from each business card into
the system.

- You create the automation to process the time entries, called Submit Time Entry, and add it to the
application. Users report issues with the formula used to connect to the automation.

- During a monthly patch cycle. IT support team members cannot identify the correct steps to patch the
machine without disrupting any automation.

- While performing an audit of the new solution during the test phase, the company's information security
team identifies that users can freely save client confidential documents to OneDrive for Business.

- When creating the automation for the project closure process, you discover that some of the required
information needs to be exported via the SAP GUI and extracted from a comma-separated value (CSV) file.

- When building the automation for the profile information system, you identify that all requests into the API
will fail unless the following HTTP header value is specified;

o Accept: application/son