Brainscape's Knowledge GenomeTM

Browse over 1 million classes created by top students, professors, publishers, and experts.


See full index

D > Design solutions > Flashcards

Design solutions Flashcards

1
Q

Power Apps Building Blocks

A

1) Power Apps Home Page (make.powerapp.com)
2) Power Apps Studio
3) Power Apps Mobile App
4) Power Apps Admin Center

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Types of App

A

1) Canvas App
2) Model-driven App
3) Portal

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Ways of creating App

A

1) Start from blank
2) Start from data - Generated apps are always based on a single list or table. But you can add more data to the app later.
3) Start from templates/ sample
4) From Dataverse source
5) via AppSource

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Power Apps Related Technologies

A

1) Data Sources
2) CDS/ Dataverse
3) Power Automate

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Flavors of RPA

A

1) Attended RPA
a) humans initiate tasks or respond to specific prompts—like providing a yes/no response. Boring, repetitive tasks like front-office activities can be easily automated.
b) When running attended, Power Automate uses an existing Windows user session.
2) Unattended RPA
a) bots handle the tedious, menial work for you by recording and playing back actions—without the need for anyone to be at their computer. With unattended RPA everything is fully automated, so you’re able to schedule and trigger events which accelerates end-to-end automation of high-volume tasks.
b) to run unattended desktop flows, the target machine needs to be available with “all users signed out”.
Locked Windows user sessions will prevent desktop flows from running.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Design Power Apps

A

1) Business Requirements
2) Data Model
3) UX (User Experience)
4) UI (User Interface)
5) Business Logic
6) Output

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Premium datasource

A

require each user who use app require
1) power apps “per app” plan or - allows individual users to run 2 applications and 1 portal for a specific business scenario in a specific environment based on full capabilities of Power Apps with access to premium connectors.
2) power app “per user” plan - allows users to run unlimited premium licensed apps.
eg 1) CDS/Dataverse
2) SQL

Note
Power Apps portals have their own licensing model and are not included in above licenses. You purchase a capacity based license to met business needs for that.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Access existing data

A

1) using connector
2) using dataflow (extract,load, transfer into CDS or Azure Data lake) - it fetches data in scheduled batch. Use power query data

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Types of Relationship in Dataverse

A

1) 1:N - lookup field on the child(related) entity.
2) N:N - special third entity which maps how the many records of one entity can be related to the many records of another entity.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Limitations of Virtual Entity

A

1) Only organization-owned entities are supported.
2) Auditing not supported
3) Change tracking not supported
4) cannot be enabled for queues.
5) offline caching of values is not supported
6) cannot represent an activity
7) do not support BPF
8) Once created, cannot be changed to be a standard (non-virtual) entity

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Why CDM (Common Data Model)?

A

1) Structural consistency
2) semantic consistency
3) simplified integration and disambiguation of data
4) unified shape
5) ability to extend the schema and CDM standard entities

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Principles of Reusable component

A

1) should offer a degree of customization and flexibility

2) interface of control should remain simple and clean

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Connector

A

wrapper around an API that allows the underlying service to talk to

1) MS Power Automate
2) MS Power Apps
3) Azure Logic Apps

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Connection Authentication Types

A

1) No authentication
2) Basic authentication
3) Api Key based authentication
4) Oauth 2.0

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

PVA

A

1) Define topics
2) Publish on different channels
3) Monitor performance

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Webpages

A

represents a particular URL in a portal’s website

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

Page templates

A

1) Rewrite templates

2) Web templates

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

Web template

A

1) use liquid templating language

2) define how content is processed and rendered

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

Web files

A

1) Provide access to inline or downloadable content
2) web files do not use templates
3) Content is stored as a Note with an attachment or in MS Azure Blob storage

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

Code snippets

A

Reusable fragments of editable content that can be placed within a web template.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
21
Q

Entity lists

A

Define how the list of CDS/Dataverse records is displayed on portal pages

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
22
Q

Entity forms

A

add the ability for portal pages to interact with records in a specific entity by using a model-driven Power Apps from definition as a layout template.
They can display most column types and subgrids but cannot display PCF controls at the moment

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
23
Q

Core components of Portals

A

1) Webpages
2) Page templates
3) Web templates
4) Web files
5) Content snippets
6) Entity lists
7) Entity forms
8) Web Forms

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
24
Q

Portal Security - Authentication

A

1) Local - common forms- based authentication with user name and pwd are stored in CDS contact row internally . Pwd are hashed.
2) External - handled by other identity providers, google account, ms account , twitter account etc for eg.
OAuth2 (Microsoft, Twitter, Facebook, Google, LinkedIn, Yahoo)
Open ID (Azure Active Directory, Azure Active Directory B2C)
WS-Federation and SAML 2.0 (used for integration with on-premises Active Directory and other identity services)
Azure Active Directory B2C is the recommended identity provider for authentication

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
25
Q

“Tree View” in Canvas Apps

A

1) On left hand side

2) anything that you add to your app will appear over here.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
26
Q

“Properties” in Canvas Apps

A

1) on right hand side

2) Shows the properties that you can change for the element(control) of your app.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
27
Q

OnSelect

A

Specify what happens when you press that button for eg.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
28
Q

Preview Canvas App

A

1) Need not be saved
2) Preview button on top right
3) or Press F5
4) or Press Alt key and click the controls on the canvas app

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
29
Q

Share the App

A

1) Save by pressing Ctrl+s or File menu -> Save

2) Publish button

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
30
Q

Types of Forms in Power Apps

A

1) Edit

2) Display

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
31
Q

“Default Mode” of the Form in Power Apps

A

1) New
2) Edit
3) View
NEV

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
32
Q

Types of Entity in CDS/Dataverse

A

1) Standard - base entities created for every instance of CDS/Dataverse, out of box.
Add more fields but only delete fields from custom entity.
2) Complex - contains server side business logic including real time workflows or plugins.
- some care needed to ensure users have functionality by giving them license.
3) Custom - extend the functionality.
4) Restricted - tied to specific D365 application functionality. User needs additional licenses to the corresponding D365 application to create, update or delete records within restricted entity.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
33
Q

Business Rules in Canvas Apps & Model-driven apps

A

1) Set Field values
2) Clear Field Values
3) Validate data and show error messages

Additionally in Model-driven apps

4) Show or hide fields
5) Enable or disable fields
6) Create business recommendation based on business intelligence.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
34
Q

PPAC

A

1) Environment
2) DLP (Data Policies)
3) Data Integration
4) Analytics- Power Automate, Power Apps, Dataverse

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
35
Q

Why different environments?

A

1) Business Requirement for different legal entities or departments
2) Geographical
3) Support ALM (Application lifecycle management)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
36
Q

New environment in PPAC

A

1) Name,
2) Type - Sandbox, Trial, Production, Trial (subscription- based)
3) Region
4) Purpose
5) Create a database option?
6) Default language
7) url for dataservice
8) default Currency
9) Enable Dynamics 365 apps? (can be enabled only for default region)
10) Optionally deploy sample apps and data?
11) Security Group

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
37
Q

Lifecycle of a solution

A

Create > update > upgrade > patch a solution

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
38
Q

Types of Default solution

A
  • are unmanaged solutions
    1) CDS Default solution - available for makers to use by default for their customizations in an environment to try out.
    2) Default solution - contains all components in the system.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
39
Q

Type of solution to be checked in source control?

A 
unmanaged solution.
Note - 
1) Cannot import managed solution in the environment where environment has unmanaged solution which was used to export it.
2) Cannot export managed solution
3) Cannot export Default solution.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
40
Q

Solution Checker

A 
checks
1) performance 
2) stability issues
it analyzes these solution components
1) CDS plug- ins
2) CDS custom workflow activities
3) CDS web resources (HTML and JS)
4) CDS configurations, such as SDK message steps.
* Solution checker works with unmanaged solutions that can be exported from an environment.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
41
Q

Security Roles

A

Team is owned by BU
BU has a default team created automatically
Default team members are managed by CDS

Owning teams
Access teams

42
Q

Security Roles privileges

A

1) Record - level privileges
define which task a user can do with access to the record
Create, Read, Write, Delete, Append, Append To, Assign, Share
Append (Note), Append To (opportunity) for allowing to append note to Opportunity
2) Task - based privileges
eg publish articles

Append and Append To is to think of ‘Append Me’ and ‘Append Me To What’.
Append: When an entity has the lookup of another entity on its form. It is important that the user have the “Append” privilege on this entity so that it can set the values for the lookups on this entity. For eg: Contact has the lookup of Account on its form so here the user needs to have the “Append” privilege to be able to set the parent account.

Append To: When an entity is available as a lookup on another entity form. It is important that the user have the “Append to” privilege on the entity that is referred to in the lookup so that it can set the values for the lookups of this entity on any other form. For eg: Account has the lookup of primary contact. So here the user needs to have the “Append To” privilege to be able to set the Primary Contact for the Account.

43
Q

Canvas App vs Model-driven apps

A

Canvas Apps

1) start with user experience
2) WYSIWYG designer
3) Task-based & role-based apps
4) Mash-up data from 300+ sources
5) can be built with or without CDS.
6) They use connectors to access data and services. Integration spanning multiple systems by using connectors

Model- driven. app

1) Built on CDS
2) Start with a data model, relationships and business processes
3) Build E2E business applications.
4) Responsive design
5) More consistent look and feel from one screen to the next without requiring much effort from the app creator.
6) Good for scenarios where the business logic is complex like sophisticated data models, Business process management, Tracking activities associated with data.

Consider creating a model-driven app unless your users have a specific need for a canvas app. Model-driven apps enable you to make your app quickly because they don’t require you to build out the UI yourself.

44
Q

App maker tools

A

1) Power Apps Studio - Canvas apps
2) App designer - Model - driven apps define sitemap and add components
3) Power Apps portals Studio - WYSIWYG design tool to add and configure webpages, components, forms and lists.

45
Q

Creating Canvas App

A

1) From SharePoint
2) From a sample/template
3) From a Dataverse source
4) From a blank canvas
5) Via AppSource

46
Q

Screens auto created when Canvas App is created from Data

A

1) Browse Screen - Gallery - list of records to display from a datasource
2) Detail Screen - Detail Form
3) Edit Screen - Edit Form
(BED)

47
Q

Form

A

contains cards - select visualization of the data field. combine together few controls like label, validations, etc hence called card.
* they are locked - > unlock to change properties.

48
Q

Imperative vs Declarative Development

A

Imperative
1) focus on how to achieve the goal
2) provides more flexibility because you control every step in the process
3) more code and
4) more complexity
5) Focus is on pushing data
Declarative
1) focus is on getting the result
2) much simpler and straightforward to use
3) can lack the ability to have the complete control that you might want
4) Focus is on pulling data

49
Q

Types of Variables in Power Apps

A

1) Global variables - app
2) Context variables - screen
3) Collections - app
* temporary , only available to current user in current session.
* if you give a context var the same name as global var or a collection, the context var takes precedence
* Context variables are also preserved when a user navigates between screens.

50
Q

Context Variables in Power Apps

A

is only available on the screen where you create it using the UpdateContext function.
eg on popup screens
* you can declare more than one variable at a time using UpdateContext. This is not possible with Set function.
eg
UpdateContext({varCount: 1, varActive: true, varName: User().FullName})
Set(varCount, 1);Set(varActive, true);Set(varName, User().FullName)

51
Q

Collection

A

special type of variables for storing a table of data or special type of datasource

  • created dynamically using collect
  • cleared using ClearCollect
  • available in the entire app like global variable.
  • are local to the canvas app and not backed by a connection to the service in cloud.
  • therefore, info cannot be shared across devices for the same user or between users.
  • Collections can be loaded and saved locally.
  • The one exception where Collections vary from tabular data sources is you cannot use them with the Form control.
52
Q

Component Library

A

1) share one or more components with other app makers
2) Discover and search components
3) Publish updates
4) Notify app makers of available component updates.

53
Q

UI in Model- driven app

A

1) App
2) Sitemap
3) Form
4) View

54
Q

Logic in Model-driven app

A

1) BPF
2) Workflow
3) Actions
4) Business Rule
5) Flows/Power Automate

55
Q

Visualizations in Model-driven app

A

1) Charts - in a view or form or dashboard
2) Dashboard
3) Embedded MS Power BI - tiles to your dashboard

56
Q

Components in Sitemap Designer

A

Area
Group
Subarea - Dashboard, entity, webresource, url

57
Q

Type of Forms in Model-driven App

A

1) Main Form -
* except on Dynamics 365 for phones. is also used for D365 for Outlook and D365 for tablets.
2) Quick Create -
* full support by form scripts and business rules. Create button from navigation bar, +New from lookup or sub-grid.
* App mobile uses quick create forms. If entity doesn’t have a configured quick create form, D365 generates a quick create form for creating records in the mobile apps based on the main form definition.
* Entity definition should have Allow Quick create set.
3) Quick View
* If lookup field is not set, the quick view control will not be visible.
* Data in quick view cannot be edited
* Quick view forms do not support form scripts.
4) Card
* used in interactive dashboards and placed on forms of related entities.

58
Q

Appchecker

A

1) Formula errors
2) Accessibility warnings
3) performance optimization tips.

59
Q

Building Blocks of Flow

A

1) Trigger
2) Action
3) Conditional Logic

60
Q

Types of Trigger for Power Automate

A

1) Manual Action (Button eg)
2) Scheduled Trigger
3) Run based on an event that happens in a cloud or on-prem service

61
Q

Dynamic Content in Power Automate

A

attributes from previous steps and trigger available to be used in the following steps….?

62
Q

Expressions in Power Automate

A

are a set of simple functions that enable you to return data.
for eg converting date in required timezone.

63
Q

Flow Run page

A

Shows history of execution

64
Q

BPF Components

A 
Flow
1) Stage
2) Condition
Composition
1) Data Step
2) Workflow
3) Action Step
4) Flow Step
65
Q

Business Rules components

A 
Flow
1) Condition
Actions
1) Recommendations
2) Lock/Unlock
3) Show Error Message
4) Set Field Value
5) Set Default Value
6) Set Business Required
66
Q

Details to be provided while creating Canvas App from blank

A

1) App Name
2) Format (Tablet/phone)
3) skip Welcome to Power Apps Studio prompt

67
Q

User() function in Power Apps

A
  • can retrieve
    1) Email
    2) FullName
    3) Image
68
Q

App Checker

A
  • checks
    1) Formulas
    2) Runtime
    3) Rules
    4) Accessibility
    5) Performance
69
Q

Settings page of Power Apps

A 
Name + icon
1) Change the app name
2) Select app icon
3) Select Background color for the icon
4) Description - to describe what people can do with this app.
Screen Size + Orientation
1) Landscape/Portrait
2) Change the aspect ratio
Advanced setting
Change the preview and experimental feature settings.
70
Q

How is canvas app made available to others?

A

1) Save - automatically publishes only for yourself and anyone else who has permission to edit the app.
2) Publish - when you finish making changes, you must explicitly publish them to make it available to everyone with whom the app is to be shared.

71
Q

Components of Gallery in Canvas Apps

A

1) Gallery Control
2) Template cell (first cell)
3) controls within the template cell

72
Q

Controls on the Card in the form (Canvas Apps)

A

1) StarVisible1 - label control that has an asterisk (*).
- Visible property set to true or false depending on whether the field is required or not.
2) ErrorMessage1 - label that is just below the main data entry field which displays error messages.
3) DataCardValue1 - text input control where you can enter the field value.
4) DataCardKey1 - label that displays the title of the field.

73
Q

Datacard in the form can be hidden on the form

A

1) Select the datacard
2) Goto properties pane
3) Set the visible toggle to off
eg Request Date - you can default it to today’s date and have it included as part of the form which will update the field as part of the form submit.

74
Q

Multiple functions in Canvas app formula bar.

A

‘;’ is used a separator when multiple functions are called one after the other. If you are in a locale where ‘;’ is used as

a comma-separator, then use a double ‘;’ here (without the single-quotes).

75
Q

data sources vs connector

A
  • Data is stored in Datasource
  • you bring that data to app by creating connection.
    connection uses specific connector to talk to data source.
  • connector may provide tables of data or actions.
76
Q

Types of Power App connector

A

1) Standard - out of box , no configuration needed, no special license needed for eg SharePoint, OneDrive, GoogleDrive,Twitter, Github
2) Premium - only available if you subscribe to premium license plan - eg Salesforce, Docusign, Amazon, Survey Monkey etc.
3) Custom - used to connect to external webservices, where you define
* authentication it needs,
* the triggers and
* actions that it supports
* parameters and
* outputs for each of these actions.

Standard Premium Custom 1) Available in all only with premium available in
license licenses all license.
2) No config No config Config req

77
Q

Tip

A

If a column in your table of excel contains images, include” image” in the name of that column. This keyword will bind that
column to an image control in a gallery

78
Q

Error in Canvas App

A

If an error occurs when the value of a field is not valid, a required field is blank, you’re disconnected
from the network etc , Error property of the Edit Form control contains an error message to show the user.
* On Edit and Create screen , add a Label control and set the Text property to Form1.Error

79
Q

Power Apps with Power BI tile

A

When you share an app that contains Power BI content, you must share not only the app itself but also the
dashboard where the tile comes from. Otherwise, the Power BI content won’t appear even for users who open the
app.
Not recommended to have more than 3 tiles loaded as the same time within an app.

80
Q

Portal creation step

A

1) Portal Name
2) url Address (.powerappsportals.com)
3) Language

81
Q

Can power app portal start from blank?

A

No. Power Apps portals apps are always started from a template instead of a blank application

82
Q

Data Loss Prevention Policy (DLP) - Scope

A

1) Environment level
2) Tenant Level
a) All environments in the tenant
b) Specified environment
c) All except excluding the specified env
* DLP affect Power Automate and Power Apps
* tenant admin or environment admin role

83
Q

DLP - Classification of connectors

A

1) Business - business -use data
2) Non Business - personal- use data (default when a new policy is created)
3) Blocked - cannot use in one or more env.

84
Q

BPF Rules

A

1) 5 entities
2) 5 levels of condition
3) max 10 active bpf on an entity
4) 30 stages
5) 30 data steps
6) Workflow on the stage exit for “Final Stage” will never execute , as process will not transition out of the final stage.

85
Q

Miscellaneous form details

A

1) Each entity must have a designated fallback form
2) Only Main forms can be assigned to security role.
3) Form selector available to the user if more than 1 form available to him.
4) can designate a main form as inactive. This will make it not visible to all users, regardless of security roles.
5) You cannot create new records via editable grid, you may only use it to update existing records.
6) Data changes made within Editable Grid will have same impact on Workflows and Business Rules with a scope of Entity or All Forms as if the same data changes were made on the form.

86
Q

Bing map

A

can be added to

1) Contact
2) Account
3) lead
4) quote
5) order
6) invoice
7) competitor
8) system user

87
Q

Types of Views

A

1) System - added to solution
2) Public - automatically created for custom entities . Can be modified but not deleted.
*Additional public views can be created and deleted.
eg
a) Advanced Find - only 1 per entity.
b)Associated View
c) Lookup View - first three columns of the lookup view are visible when a user clicks on the magnifying glass icon on the related lookup field.
d) Quick Find - only 1 per entity.
3) Personal - defined by user themselves and can share.

88
Q

Chart

A

1) can display upto 5 series group by 1 category or
2) 1 series group by 1 or 2 category
cannot display multiple series group by more than 1 category
* Personal charts cannot be added in solution package for deployment but can be exported as xml file and imported into target solution.

89
Q

Dashboard

A

Interactive Experience Dashboard -
Multi stream - Data on one stream can be from only 1 entity but different stream can be based on a different entity.
Single stream - more used by tier 2 - complex issues but fewer queues.

90
Q

Test Plan components

A

1) Environmental needs
2) Features tested
3) Features not tested
4) Testing Items
a) Related Business Requirement
b) Steps to test
c) Expected result
d) Item pass or fail
e) Time and date tested
f) Tester name
g) Testing Notes
5) Testing Schedule
a) Dependencies
b) Timelines
c) Schedule risks
6) Process for fixing and retesting failed test items

91
Q

Quick Search

A

When the user searches for records within a view, Dataverse performs a query that searches only predefined fields.
Which field is searched is defined by the Find Column settings in the system Quick View.

92
Q

Dynamics 365 Diagnostic tool

A

1)Network bandwidth
2) Latency
use Dynamics 365 diagnostic tool available at
https://.crm.dynamics.com/tools/diagnostics/diag.aspx where .crm.dynamics.com is the URL of your Dynamics 365 organization

93
Q

Data performance logs

A

Data Performance Logs via Settings -> Administration -> Data Performance.
You can analyze and optimize query performance using the Data Performance view, which provides an aggregated list of entities with long-running queries. A long running query is defined as a query that takes three seconds or longer to complete. Typical examples of a component that can have a long running query is a plug-in with custom FetchXML or a sub-grid or view.
With the most recent advances in Azure SQL database self-tuning capabilities you may no longer see any long running queries reported in the Data Performance view. Slow queries are automatically detected and optimized at the database level.

94
Q

Collect

A

Use collect to create collection

1) The Collect function is not delegable. This means by default only the first 500 records from the data source will be retrieved and stored in the collection.
2) Collections are not linked to the data source after you create them. This means changes to the data in the collection do not automatically save to the data source. If you want to update the data source based on your changes to the collection, you will need to build formulas to do so.
3) Collections are temporary. When you close the app, the collection and all of its contents are removed. If you need to store collection data, you need to write it to a data source before closing the app.

95
Q

Default value of variable

A

default value of a variable will vary based on the variable type if you do not set the default property.

Text variables are “”

Number variables are 0

Boolean variables are false

96
Q

Functional vs Non Functional

A

Functional - what the system needs to do or its behavior
Who , What and Why
Non Functional - non behavior aspects of the solution for eg performance requirements.

97
Q

Fit-gap analysis

A

identifies difference between known requirements and the proposed (or current) solution.
You should look at each requirement/user story and note at least the following for each:
1) Severity of the gap or category - fit, configured, custom or other
2) Level of effort - low, medium high, or could be 1-10, or some teams even uses things like t-shirt sizes or planning cards
3) Priority - Often this comes from the business, but the architect often needs to have some prioritized higher to help with the architecture foundation being put in place.
4) Implementation notes - This describes the work to close the gap identified and backs up your assumptions you made in the other columns.

98
Q

Types of demos

A

1) Out of the box - An out of the box demo simply shows off one or more of the apps without any customizations.
This is often performed by pre-sales resources and doesn’t involve the solution architect. This is a good way to get customers up to speed with the core product features. The negative of this approach is it doesn’t help the customer envision their solution on the app. You can mitigate some of this by including relevant sample data to their business.

2) Pre-built demo – Many partners specialize in particular verticals or solution areas and invest in building up pre-built demos containing their own intellectual property that tailors the out of box base solution with their designed value-add. This approach helps the customer see their particular problem area because often it uses the vertical language in the app. Often it also hides things that aren’t appropriate for the solution area that might distract the customer.
3) Prototype – This takes the out of the box state and with the customer needs in minds does the minimal tailoring of the app to reflect the customer’s needs. The main benefit of this is to allow telling a story during the demo that the customer can relate to solving their particular objectives.
4) Proof of concept – Proofs of concept should be built to prove a concept works and typically involves a very specific component or activity in the proposed solution. Unlike a prototype that usually has a straightforward path to completion, proofs of concept may try multiple approaches to reach the desired goal.

99
Q

Unattended mode of Desktop Power Automate

A

Power Automate performs the following:

1) Power Automate creates, manages, and then releases the Windows user session on the target devices.
2) Unattended desktop flows run on devices with the screen locked so that no one can see the flow while it runs.
3) Windows 10 devices cannot run unattended if there are any active Windows user sessions present (even a locked one). You will receive this error: Cannot execute desktop flow. There is a locked or an inactive Windows user session on the target device.
4) On Windows Server, if you have a locked Windows user session open with the same user as the desktop flow is supposed to run as, you will receive the same error: Cannot execute desktop flow. There is a locked or inactive Windows user session on the target device.

100
Q

Attended mode of Desktop Power Automate

A

To run an attended desktop flow, you need to have an active Windows user session that matches the name of the user configured for your connection. The session must not be locked.

When an attended desktop flow starts on the target machine, we recommend that you avoid interacting with your device until the run completes.

101
Q

Multiple desktop flows on the same device sequentially

A

You can schedule multiple desktop flows to run on one or more devices. If more than one desktop flow is triggered to run on the same device, Power Automate follows these rules:

The first desktop flow runs on the target device.

Queues other desktop flows and then displays them as Waiting in the desktop flows and gateway details page.

Picks the next Waiting desktop flow when each run completes.

If there are too many desktop flows in the execution queue a timeout might occur. Desktop flows runs will fail if they don’t run within 30 minutes after being triggered.

D (11 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2024 Bold Learning Solutions. Terms and Conditions