JS

Question 1

Search Functionality

Answer 1

1) Quick Find - on the entity - fields defined in Find By
2) Advanced Search - Searchable property of the field if set to N will not show field on the Advanced find.
3) Categorized Search - 10 entities max , in the System settings. Fields defined in Quick Find view.
4) Relevance Search - across multiple entities , utilizing azure search functionality. enabled in power platform admin center . Settings -> Feature
Relevance Search is the preferred method for finding records as it searches more fields than the other methods and searches in notes and the contents of attachments.

Question 2

Power BI in Model driven app

Answer 2

You need to enable Power BI visualization embedding for your environment in Features, under Settings, in the Power Platform admin center.

Question 3

SP integration

Answer 3

1) SharePoint integration is known as “server-based integration” to distinguish it from the server-side synchronization that is used for email integration.
2) Provides the infrastructure to support OneNote integration in model-driven apps
3) a document library is created for each record where the entity is enabled for Document Management.
4) require SharePoint integration to be enabled if you want to use the collaboration features with Microsoft Teams.
Environment->Settings->Integration ->Document Management Settings-> Enable Serer based SP integration

Question 4

Canvas apps as teams app

Answer 4

1) Maker portal -> Details page of the app - > Add to Teams
2) Review and download the app(.zip) file
3) Upload your app as a custom app to Teams
4) To add canvas apps as a Teams app, the Upload custom apps option must be enabled by a Teams admin in the Teams app setup policies.
5) If you want this app to appear for all users, you need to upload the app for the organization and then, in the Teams admin portal, edit the “global app setup policy” and add the canvas
app to the list of pinned apps

Question 5

O365 Administration center

Answer 5

1) Users
2) Subscriptions
3) Allocation of licenses to users
4) Security groups and membership

Question 6

PPAC

Answer 6

1) Create environments.
2) Open environments.
3) Access environment settings.
4) Perform environment operations (copy, switch, delete, reset, admin mode,security group, convert trial).
5) Manage data loss prevention policies.
6) Integrate data.
7) Install/update applications and solutions.

Question 7

Maker portal

Answer 7

1) Manage CDS (entities, fields, relationships, forms, views, and rules).
2) Create apps.
3) Import data.
4) Export data.

Question 8

Connection Roles

Answer 8

*are created in PPAC
Environment->Settings-> connection roles.
*Category, Record Types, Matching Connection role.

Question 9

Business Rules vs Calculated

Answer 9

1) Business Rule - Conditions are checked when the form loads and whenever any field referenced within the condition changes.
Business rules are run automatically in the order that they were activated.
You cannot run a business rule manually.
2) Calculated field - re-calculated when form is saved.

Question 10

Scope of Business Rule

Answer 10

If you choose All Forms for the scope, the business rule will be applied for all the Main
forms and the Quick Create form.
Rules do not run again when a record is saved
unless the scope for the rule is set at an entity level.

Question 11

Limitations of BR

Answer 11

1) Business rules run only when the form loads and when the value of the field referenced in the rule is changed.
2) Rules do not run again when a record is saved unless the scope for the rule is set at an entity level.
3) If a business rule references a field that is not present on a form, the rule will not be applied. There will be no error message to inform you that the rule hasn’t been applied.
4) When the scope is set to Entity, the rule will run twice – once on the form and once on the platform.
5) Business rules work only with fields. If you need to manipulate other form elements, such as tabs or sections, you must use JavaScript.
6) You can’t have more than 10 if-else conditions in a rule.
7) Nested if-else statements are not supported.
8) Grouping of expressions in a condition is not supported.
9) Rules in conditions can be combined either using AND or using OR, but not both.
10) When you set a field value using a business rule, OnChange JavaScript event handlers for that field will not be triggered.

Question 12

Classic workflow vs Power Automate

Answer 12

Classic workflows have one advantage over Power Automate flows: they can be run in real
time, that is, synchronously.

Question 13

Classic Workflow can be triggered by following events on records in the CDS

Answer 13

Creating a record
Updating a record
Deleting a record
Changing the status of a record
Change of ownership (assigning) of a record

Question 14

Conditions in Classic Workflow

Answer 14

There are two types of conditions for processes:
Check conditions
Wait conditions
A process can use fields from the entity or any field from an entity in a many-to-one
relationship in a condition.
Check conditions can be nested, but be careful as the process editor cannot
handle more than five levels of nesting.
* Wait conditions can only be used in background workflows.
*A wait condition should always have a parallel wait condition to prevent the process from running forever
*If the background workflow you convert uses a wait condition, it will
become invalid and you won’t be able to activate it until you remove the
wait condition.

Question 15

Action vs classic workflow

Answer 15

Action processes cannot be triggered automatically.
Action processes are invoked from other components.
Action processes can have input and output arguments.
Action processes are associated with a single entity or can be set as global (not
associated with any entity).
Action processes always run under the security context of the calling user.
Action processes always run synchronously, in other words, in real time.

Question 16

Action process in Power Automate flow

Answer 16

To call an action process in a Power Automate flow, you need to use the

1) Common Data Service (current environment) connector.
2) You should use Perform a bound action for action processes associated with an entity,
3) and use Perform an unbound action for action processes set as Global.

There are built-in actions in the CDS that you can use, such as the following:
Set Word Template: Creates a Word document from a Word template
Add To Queue: Adds a record to a queue

Question 17

Logs for Workflow

Answer 17

1) Background - System jobs
You can toggle the Keep logs for workflow jobs setting in the properties of the
workflow editor
2) Realtime - do not create system jobs
in a real-time workflow, there is no log for successful operations. You can enable
Error logging by checking the keep logs for workflow jobs that encountered errors during setting in the Workflow Log Retention area in the process editor.
View of the errors - use Advanced Find and create view for “Process Session” entity.

Question 18

Priv for Import data

Answer 18

You need the Data Import and Data Map privileges to use the Import Data Wizard.

Question 19

Data templates

Answer 19

Data templates are spreadsheets that you can download to increase the success of data
imports.
The data templates are available in Advanced Settings under Data Management,

Question 20

Duplicate detection

Answer 20

• Adding multiple fields to a rule means all the fields must match. This is the equivalent of an AND operation.
• If you need to perform an OR operation, such as matching on the email address or phone number, you
  need to create separate rules, one for matching on the phone number and one for matching on the email address.
• You can have five duplicate detection rules per entity.
• Duplicate detection rules cannot be included in solutions

Question 21

Viewing Audit Records

Answer 21

1) Audit History - Entity under related records. view of all the changes made to a record.
2) Audit Summary - all audit events in the environment. PPAC
A new audit log is created every 90 days.
Microsoft makes all audit logs available from the Microsoft 365 Security and Compliance
Center with the added benefit of including reads and other data viewing activities, such as
exporting to Excel.
Some of the activities that are logged include the following:
Reads of individual records
Queries of multiple records
Export to Excel
Adding a user to a team
The activity logs can be viewed in the Microsoft 365 Security and Compliance Center

Question 22

Security levels

Answer 22

1) Azure Active Directory (AD) handles the authentication of users.
2) Office 365 and Azure AD manage users and their licenses.
3) Access to environments can be restricted in the Power Platform admin center.
4) CDS databases manage security, authorizing the use of data and services within applications.

Question 23

Security Group

Answer 23

Environments can be linked to an Azure AD security group. Once linked, only users in that security group will be able to access that environment

Question 24

Organization owned entity

Answer 24

Entities that are organization-owned do not have the Assign and Share privileges as these
privileges are concerned with record ownership – records for organization-owned entities do not have an owner.

Question 25

Note

Answer 25

If a user does not have at least read access on an entity, then that entity will not be shown in the model-driven app; it will not be shown in the navigation or appear in Advanced Find. If a user does not have the Create privilege for an entity, then the + NEW button will not be shown in the action bar. If a user does not have the Delete privilege on a record, then the delete icon will not be shown in the form for that record. If a user does not have the Append To privilege on a record, then they will be unable to attach other records to it such as phone calls, tasks, emails, and other types of activity. Assign and Share privileges do not control to whom a user can assign or share to; that is controlled by the Append privilege on the entity combined with the Append To privilege they have on the User and Team entities. The Assign and Share privileges control which records you can assign and share. Where there is a many-to-many relationship between two entities, the Append and Append To privileges are required on both entities in the relationship. Users are created in the root business unit by default and, except for users with administration roles, are not given a security role and are therefore prevented from accessing the CDS. A record cannot be assigned to a user or a team if that user/team does not have at least user-level access for that entity. If you haven't applied a security role to a team then you will be unable to assign a record to that team. You cannot give another user a privilege you do not have; that is, if you do not have the Delete privilege on a record, you cannot select Delete while sharing the record. Field security profiles are components that can be added to solutions

Question 26

Security roles can control/cannot control following components.

Answer 26

Can control 1) Forms 2) Dashboards 3) Business process flows cannot control access to the following components with security roles: 1) Fields 2) Charts 3) Views

Question 27

Can share

Answer 27

Personal views Personal charts Excel templates Word templates

Question 28

When you add user to an access team subgrid

Answer 28

When you add a user to such a sub-grid, the system does the following: 1)Creates an access team 2)Adds the user as a member of the new team 3)Shares the record with the new team Only users can be added to an access team sub-grid

Question 29

Process to add subgrid for Access team

Answer 29

The process to add a sub-grid is as follows: 1. Enable the entity for access teams. 2. Create an access team template. 3. Add a sub-grid of users to the entity form. 4. Select the access team template. Access teams cannot have security roles applied and cannot own records. One of the advantages of access teams is that you can query and see what records are shared with which users. It is not possible to find out what records are shared with owner teams.

Question 30

Azure AD Security group

Answer 30

Azure AD security groups operate like owner teams; they can have security roles applied and can own records. You can use Azure AD security group teams to manage app and data access.

Question 31

Field Security Profile

Answer 31

Common combinations for permissions are as follows: Read-only: Allow Read set to Yes, Allow Update and Allow Create set to No Password/PIN: Allow Read set to No, Allow Update and Allow Create set to Yes

Question 32

Theme in Portal

Answer 32

Portal apps use Bootstrap v3.3 Portal apps are built using the Bootstrap frontend framework using CSS and JavaScript. The use of this common framework means that you can leverage bootstrap to brand your portal website.

Question 33

Enable entity permissions

Answer 33

1) To secure an entity list or an entity form, check the Enable entity permissions checkbox on the entity form list record 2) Once you have enabled this option for a list or form, users will not be able to access these portal components. 3) You then need to associate the entity permissions record with each of the relevant web roles. An authenticated user must be assigned a web role to access the portal. Once you have added entity permissions to the web roles, a user with that web role will be able to access the data.

Question 34

appchecker

Answer 34

The App Checker tool runs a set of rules to find errors and identify potential issues when running your app. The rules cover the following areas: Formulas: Are there missing brackets, missing quotes, or invalid references? Runtime: Will the app pose a reliability risk, or is the app using deprecated functionality? Accessibility: Will the app cause problems for keyboard or screen reader tools? Performance: Are there any likely performance issues when running the app? The App Checker can also be run as a DevOps task when exporting solutions

Question 35

User Authentication for Canvas App

Answer 35

To access a Power App, the user must belong to your Azure Active Directory (AD) tenant. Office 365 users are managed by Azure AD, so adding a user to Office 365 is sufficient. Canvas apps support the use of guest users in your tenant if you require people outside of your organization to be able to run your app. Guest users cannot be made co-owners of canvas apps

Question 36

Performance in Canvas App

Answer 36

Controls: Keep the number of controls on a form as low as possible and make use of galleries instead of cards. The more controls you have, the slower the app will be. Use delegation: Check that queries are executed on the server, not in the app. If queries are not delegated, you will see poor performance when opening your app. Data connections: Limit the number of connections. Caching: Use the ClearCollect function to cache data during OnStart. Delayed load: Enable this option if you have multiple screens. It will only populate a screen when the screen is accessed rather than at startup. Delay output: Enable this option on text input fields so formulas are not evaluated on each keystroke. Formulas: Reduce the number of times a formula is used by setting a variable once and then referencing the stored result elsewhere.

Question 37

Model driven app

Answer 37

If you are using solutions, you can check the Use existing solutions to create the App option. You will then be able to select a solution and the components in the solution will be added to the app

Question 38

Types of Forms

Answer 38

There are four types of entity form in the Common Data Service: Main: The form used for creating and editing records. This form is used on all clients. The form contains the fields for the entity and other controls, such as the timeline. The main form will show business process flows along the top of the form. The same form definition is used for web applications, Outlook clients, and the mobile apps for tablets and phones Card: The card form is used with interactive dashboards. The card form is also used to display columns in views when the view is in a compact format, for subgrids, and on mobile clients. Quick create: Allows users to create new records without navigating away from the existing form or view. Quick view: Shows a subset of read-only fields on the form for records from lookup fields. The quick view form is also used for the tile in hierarchical views.

Question 39

Timeline control

Answer 39

The Timeline control displays notes, activities, activity feed posts, Yammer posts, and knowledge articles

Question 40

Quick View Form

Answer 40

Quick view forms have a simple structure. They are a single one-column tab with one or more one-column sections. You cannot add more tabs, but you can add more one-column sections. Only fields, spacers, and subgrids can be added to quick view forms. The ability to use subgrids is especially useful as when the quick view form is added to another form, the user can see the details of the parent record and other related records.

Question 41

Quick View Form

Answer 41

Quick view forms have a simple structure. They are a single one-column tab with one or more one-column sections. You cannot add more tabs, but you can add more one-column sections. Only fields, spacers, and subgrids can be added to quick view forms. The ability to use subgrids is especially useful as when the quick view form is added to another form, the user can see the details of the parent record and other related records.

Question 42

Quick Create

Answer 42

A quick create form is not created when a custom entity is created. You need to create a new form. They have a single three-column tab, each with a single section. You cannot add further tabs or sections. Only fields and spacers can be added to quick create forms

Question 43

Card

Answer 43

``` In the streams in interactive dashboards On mobile devices As the read-only grid control for views For views instead of a grid when the width of the view is small – for example, on subgrids in on-column sections In the timeline control ```

Question 44

Fallback Forms

Answer 44

only available for main form and not for quick create, quick view or card forms

Question 45

Mobile phones

Answer 45

Tabs, sections, and fields can be turned on or off for phones. This property "Hide on phone" is off by default and all components are displayed. Web resources, IFrames, and dashboards have a similar property, Enable for mobile (refers to both phone and tablet). This property is off by default.

Question 46

View

Answer 46

A view definition consists of the following: The entity the view will display records for The fields to display as columns in the list The order of columns in the list The query (filter) to restrict which records will be displayed The sort order You cannot restrict public views with security. If you need to prevent users from accessing a view, you can either deactivate the view or remove it from entity assets in the app designer. 25 to 300 px - column width of the view You can only sort by fields that have been added to the view. You can only sort by columns for the entity and not columns from related entities.

Question 47

System Views

Answer 47

Quick Find: The view used when searches are performed using Search this view in the user interface of an app. This view defines which fields are searched in lookup fields and in the categorized search. Advanced Find: The default view for Advanced Find. Associated: The view that is used when a user clicks on Related in a form and selects the entity. Lookup: The view used when a user clicks on the search icon in a lookup field. It also defines which fields appear in the form when you click into a lookup field. System views cannot be deleted or deactivated. You cannot create new system views.

Question 48

Personal view

Answer 48

Personal views cannot be included in a solution and cannot be converted into a public view. Personal views cannot be exported or imported like charts.

Question 49

Editable grids

Answer 49

Can do below 1) Grouping: Group by a column. 2) Sorting: Sort by any column in the view. 3) Filtering: Users can filter the records in the view. 4) Support for business rules: Business rules can perform actions on the fields in the view. Limitations 1) Address composite fields 2) Calculated fields 3) Rollup fields 4) Status or status reasons 5) Fields from a related entity

Question 50

Charts

Answer 50

The Tag and Doughnut charts are used with interactive dashboards. No charts are created when you create a custom entity You cannot restrict charts with security. If you need to prevent users from accessing a chart, you can either deactivate the chart or remove it from the entity assets in the app designer. Charts are the only component you can convert from a personal component into a system component.

Question 51

Dashboards

Answer 51

A dashboard is a single pane showing components from one or more entities. The components are not linked and are not refreshed automatically. Dashboards can have the following components: Charts Lists (views) IFrames Web resources Relationship assistant cards (for Dynamics 365 Sales) Power BI tiles (personal dashboards only) * max 6 components that can be included on a dashboard. You can restrict dashboards by security role. By default, all users can see new dashboards. You can change which security roles are associated with a dashboard by clicking on the ellipses (…) next to the name of the dashboard in your solution and selecting Enable security roles. You can add and remove dashboards in the app designer. Dashboards are not available by default for mobile clients. You should edit the dashboard properties and set Enable for mobile

Question 52

Interactive experience dashboards

Answer 52

Interactive experience dashboards are linked to an entity. There are two field properties related to the interactive experience: Appears in the global filter Sortable

Question 53

Power BI Dashboard

Answer 53

A Power BI dashboard can be added as a personal dashboard. You can add a Power BI tile to a personal dashboard. You must enable the Power BI virtualization embedding option in the settings in the Power Platform admin center.

Question 54

Reporting options

Answer 54

1) Chart results cannot be exported or printed. The only option, if you want to share a picture of a chart, is to take a screenshot. Charts are not accessible except from within the app. 2) Dashboards cannot be exported or printed. Dashboards can only be accessed by a licensed user. Dashboards show current data, not trends. 4) For trend analysis, time series, and deeper analysis, you should consider the use of Power BI. 5) The data listed in a view can be exported to Excel. There is a limit to the number of rows that can be exported. That limit is currently 100,000 rows. 6) Word and Excel templates can be used to created formatted output.Word templates are used with a single record. Excel templates have the same limit as Export to Excel. If you need to create complex reports containing multiple tables, you should consider developing reports with SQL Reporting Services or using Power BI.

Question 55

PVA

Answer 55

Power Virtual Agents uses Power Platform environments. The selected environment must have a Common Data Service database. The user you share the bot with must have been assigned the Environment maker security role, which allows users to create apps in an environment.

Question 56

PVA in Teams

Answer 56

Manage->Channel->Microsoft Teams Turn on Teams Click open bot, can add chatbot to the team in the window. This will be available only for your user. To share it with your organization "Submit for Admin approval" button 1) Download a manifest file - zip file Team admin can upload manifest file to teams. 2) Submit for admin approval - will be listed in the Team Admin portal for a Teams admin to approve.

Question 57

Topic has 2 parts

Answer 57

1) trigger phrases - keywords, phrases or utterances that user will enter 2) Conversation nodes - How bot should respond

Question 58

Call an Action

Answer 58

Call an action: Calls a Power Automate flow or an authentication node to force the user to sign in.

Question 59

Go to another topic

Answer 59

Go to another topic: Switch to a different topic. Only available on the last node.

Question 60

End the conversation

Answer 60

End the conversation: There are two options. You can end with a survey or transfer to an agent. Only available on the last node.

Question 61

Suggest topics

Answer 61

You can only use online content. Files should be added to OneDrive or another cloud service to be used for suggested topics. If you are using Dynamics 365 Customer Service Insights, you can select the topics from within Customer Service Insights and add the topics and trigger phrases to your chatbot.

Question 62

Escalate topic

Answer 62

If the chatbot cannot determine which topic to use, then the chatbot will prompt the user again. If the chatbot still cannot determine the user's intent, then the chatbot will use the Escalate system topic.

Question 63

Fallback topic

Answer 63

You may want to handle the escalation differently by prompting the user with different questions to try and pinpoint their intent. To change the default escalation behavior, add a fallback topic

Question 64

Ways to create a Flow

Answer 64

Creating from a template: Use a pre-built flow template. Creating from a Visio template: Use a Visio diagram as a template. Creating from blank: Start with a blank canvas, adding connections, actions, and logic.

Question 65

CDS Connector for Flow

Answer 65

With the Common Data Service connector, you will need to provide the environment and entity, whereas Common Data Service (current environment) uses the same environment the flow is in, and you only need to provide the entity. The Common Data Service (current environment) connector is only available when creating flows from within a solution The Common Data Service connector can be useful when you are synchronizing data between two environments as you can specify each environment in each step of your flow.

Question 66

Triggers for CDS in Flow

Answer 66

The Common Data Service connector has the following triggers: When a record is created When a record is updated When a record is deleted When a record is selected The first three triggers are automated triggers. When a record is selected is an instant trigger that allows a user to select a record in a model-driven app and run the flow manually. ``` The Common Data Service (current environment) connector has a single trigger–when a record is created, updated, or deleted. In the trigger step, you have to specify the trigger condition: Create. Create or update. Create or delete. Create or update or delete. Delete. Update. Update or delete. ```

Question 67

Advantage of CDS (current Environment)

Answer 67

The advantage of having a single trigger with multiple trigger conditions is that it can have one flow that handles both the creation and update of records. With the Common Data Service connector, you need two separate flows for creation and update. This approach also allows you to change your flow from create to update without having to delete and recreate your steps. Common Data Service (current environment) does not have an instant trigger for when a record is selected

Question 68

Actions for CDS Connector

Answer 68

``` The Common Data Service (current environment) connector has the same actions but also many more: Create a new record. Get a record. List records. Update a record. Delete a record. Relate records. Unrelate records. Execute a changeset request. Get file or image content. Upload a file or image content. Perform a bound action. Perform an unbound action. Predict. The Common Data Service (current environment) connector can also allow the creation and use of child flows. ```

Question 69

Control connector

Answer 69

``` The Control connector contains actions that you can use to control your flow: Condition Apply to each Do until scope switch - if you need more than 2 paths terminate ```

Question 70

Monitoring Flows

Answer 70

Microsoft provides the ability to monitor the execution of flows with several tools: The Power Automate portal Microsoft Teams The Power Automate mobile app

Question 71

Owners of team flow

Answer 71

``` All owners of a team flow can do the following: View the flow's run history. Turn the flow on or off. Add other users as owners. Edit the flow. Delete the flow. ```

Question 72

Relationships in BPF

Answer 72

If there is a one-to-many (1:N) relationship available, then you should select that relationship. In this way, the business process flow will respect field mappings and relate the records correctly. Many-to-many (N:N) relationships are not supported by business process flows.

Question 73

Action Step in BPF

Answer 73

If you use an action step, then the process must be defined for the same entity as the stage. To use an action in a business process flow, you must set the action to be As a Business Process Flow action step

Question 74

Flow Step in BPF

Answer 74

1) If you use a flow step, the Power Automate flow must have an instant trigger. 2) You should use the Common Data Service connector and the 3)When a record is selected trigger. You must specify in the trigger the entity that was created when you created the business process flow, and not the primary entity, nor any of the entities used in the stages of the business process flow. Only solution-aware flows can be added as a flow step.

Question 75

Classic workflow in BPF

Answer 75

A workflow set to trigger on stage entry on the first stage in a business process flow, or a workflow set to trigger on stage exit on the final stage in a business process flow, will never be executed. Therefore, you should use a global workflow in such scenarios.

Question 76

Global Workflows

Answer 76

ends. There are four different triggers: Process applied: When a process business flow is started, which can be either when the record is created or when a user starts a new business process flow manually. Process abandoned: When the user abandons the business process flow. The business process flow will be shown under archived processes. Process reactivated: When a user restarts a previously abandoned business process flow. Process completed: When the user clicks on finished on the final stage of the business process flow to end the business process flow. You must use process applied to execute a workflow in place of a workflow triggered on stage entry of the first stage in the business process flow. You must use process completed to execute a workflow in place of a workflow triggered on stage exit of the final stage in the business process flow. When a user switches from one business process flow to another, the existing business process flow is abandoned, and a new business process flow is applied.

Question 77

Connectors in BPF

Answer 77

1. Select the Source stage, Set Due date. 2. Click on Connector and then click Disconnect. 3. Select the Source stage, Set Due date again. 4. Click on Connector and then click Connect. 5. Select the Target stage, the second point in the connection.

Question 78

BPF and JS/Business rules

Answer 78

If, in the field properties on the form, you uncheck the Visible by default box, then this does not affect the business process flow control. If you hide a field in a form, the corresponding step will also be hidden in the business process flow control. If you make a form field business-required, the corresponding step will be set to required. If you set a value in a form field, that value will be set in the corresponding data step within the business process flow.

Question 79

Field level security and BPF

Answer 79

You can use a combination of field-level security and a required data step to create an approval step for a stage. This is commonly called stage-gating. If a data step is marked as required, and the field that is used by the step has field-level security enabled, then users who do not have a field security profile that grants them write permissions to the field cannot complete the step and they cannot continue to the next stage. For example, you might have a field named Budget that is enabled for field security with the field security profile set so that only one group of managers can enter a value for the Budget field. This field security is applied to the data step in the business process flow. Therefore, a manager must enter a budget value before any user can continue to the next stage of the process. You must always ensure that all users have a field security profile that grants read privilege to the secured field. If a data step has field security enabled and the user does not have read permission on the field, then the value of the field cannot be viewed by the user or by the process. In this circumstance, the business process flow will treat the field as if it contained a value, and allows the user to move to the next stage.

Question 80

UI Flow softwares needed

Answer 80

1) Windows 10 Pro, Windows 10 Enterprise, Windows Server 2016, or Windows Server 2019. 2) A modern browser: The latest version of the Google Chrome browser or the latest version of Microsoft Edge. 3) Selenium IDE: An open source tool that records and plays back interactions on a website. Selenium IDE is a browser extension that is installed from the Chrome web store. 4) The Power Automate Desktop app: A Windows application to create, edit, and run UI flows. 5) An on-premises data gateway: This tool allows UI flows to be triggered by a Power Automate flow 6) UI flows require a Power Platform environment with a Common Data Service database. Note - The Power Automate desktop app is used for Windows desktop applications and Selenium is used for web applications

Question 81

Variables

Answer 81

Variables start and end with the % symbol. Variables can be internal variables, flow variables – such as counters, or input or output variables Input variables can be passed to the UI flow from a Power Automate flow. Output variables are passed from the UI flow to a Power Automate flow.

Question 82

Attended and Unattended

Answer 82

Run Mode is how the UI flow will be run. There are two modes: Attended: The UI flow runs while the user is sat watching the screen. Attended flows are used for a part of a process that is very repetitive. The user monitors the actions and can handle errors or complete additional steps such as providing credentials to access systems. Unattended: The UI flow runs on a separate computer, normally a virtual machine running in Azure. The UI flow will perform all the actions in a process. Use an instant flow, for example, a button flow, to call a UI flow run in Attended mode. The user can then manually start the UI flow processing. The advantage of unattended flows is that you can scale the number of machines and run many UI flows in parallel. An automated or scheduled flow is typically used to call the UI flow in unattended mode.