PL-100 Leak Questions

Box 1: 1.0.0.0

When identifying versions of the app solution, all dependencies, entities, and user interfaces components must be identified to avoid any unintentional issues caused by reverting individual components to a previous version.

A solution’s version has the following format: major.minor.build.revision. An update must have a higher major, minor, build or revision number than the parent solution. For example, for a base solution version 3.1.5.7, a small update could be a version 3.1.5.8 or a slightly more signficant update could have version 3.1.7.0. A substantially more significant update could be version 3.2.0.0.

Box 2: 20.11.1.1

Scenario:

You must use the following version control numbering scheme:

- Major: The last two digits of the year the app is packaged

- Minor: Two digits that represent the month when the app is packaged

- Build: A number that is incremented to represent significant changes to the app

- Revision: The incremented revision for a package

New versions of the application must completely replace previous versions of the app.

Graphical user interface, text, application, email Description automatically generated

Box 1: Business Process

Scenario: If a sales representative submits a status report and assigns the At Risk status to a process, the app must prompt the sales representative to enter a detailed description for the risk. This information must be emailed to the regional manager.

Business process flows provide a guide for people to get work done. They provide a streamlined user experience that leads people through the processes their organization has defined for interactions that need to be advanced to a conclusion of some kind. This user experience can be tailored so that people with different security roles can have an experience that best suits the work they do.

Box 2: Common Data Service when a record is created

The Microsoft Dataverse (Common Data Service) connector provides the following triggers to help you define when your flows start:

When a row is created, updated, or deleted

When an action is performed

When a flow step is run from a business process flow

Box 1: App Checker

Scenario: Several sales representatives have accessibility restrictions. User2 is visually impaired and cannot see images. User3 is unable to use a mouse.

Users who have vision, hearing, or other impairments can use your canvas app more easily and successfully if you consider accessibility as you design how the app looks and behaves. If you're not sure how to make your app more accessible, you can run the AppChecker Accessibility checker in Power Apps Studio.

Box 2: Solution Checker

Scenario: Before deploying the app to production, you must ensure that the app conforms to Microsoft accessibility and performance guidelines.

Use solution checker to validate your model-driven apps in Power Apps.

Graphical user interface, text, application Description automatically generated

Box 1: Power Apps mobile app

Scenario:

User1 often works in a warehouse that does not have internet connectivity.

User1 needs to edit an existing status report and submit a new status report.

The app must be able to run both online and offline. If the mobile device on which the app runs is connected to the internet, the app must immediately submit the status report.

You can build offline capabilities in your PowerApps app so your app users can access some data or save some data even when they don't have an internet connection.

Box 2: Connector

Scenario: Azure SQL Database is used to store other data

Use the SQL Server connector to connect to SQL Server, in either Azure or an on-premises database, so that you can manage your data with create, read, update, and delete operations.