Model Driven Apps Flashcards
Benefits of Model Driven Apps
1) Rich component-focused no-code design environments
2) Create complex responsive apps with a similar UI across a variety of devices from desktop to mobile
3) Rich design capability
4) Your app can be distributed as a solution
System Business Process Flows
1) Lead to Opportunity Sales Process
2) Opportunity Sales Process
3) Phone to Case Process
Conditions to run BPF in offline mode.
1) The business process flow is used from a Power Apps app
2) The Power Apps app is enabled for offline use.
3) he business process flow has a single entity.
Commands available for BPF in offline mode
1) Next stage
2) Previous stage
3) Set Active Stage
Building blocks of Model Driven App
Data 1) Table/Entity 2) Column/Field 3) Relationships 4) Choice Option Set UI 1) App 2) SiteMap 3) Forms 4) Views Logic 1) BPF 2) Business Rules ( business rules do not work on multi-select choice, A business rule may also not execute because a column referenced in the business rule is a composite column eg fullname) 3) Workflows 4) Actions 5) Power Automate/Flow Visualization 1) Charts 2) Dashboards 3) Embedded Power BI - tiles and dashboards
Requires the configuration of the Data Integrator to make your business data available within Common Data Service
1) Dynamics 365 Finance,
2) Dynamic 365 Supply Chain Management and
3) Dynamics 365 Retail currently
Can’t find entity while creating a BPF on step select Common Data Service Entity
make sure the “Business process flows (fields will be created) is set for the entity in the entity definition.
Minimap on BPF
1) lets you see the whole process
2) quickly go to a part of the process.
Add workflow to the BPF
Workflow should be on-demand active workflow
1) to specific stage -
* if the workflow should be triggered when the process enters or exits the stage.
* The workflow component must be based on the same primary entity as the stage.
2) Global workflow item -
* if the workflow should be triggered when the process is activated or archived (ie status changes to Completed or Abandoned).
* The workflow component must be based on the same primary entity as the process.
Security roles for BPF
By default, the System Administrator and System Customizer security roles have access to new BPF. Rest we need to give explicit access.
Snapshot of BPF
To take a snapshot of everything in the business process flow designer, select Snapshot on the action bar. This option is useful if you want to share and get comments about the process from a team member.
Set Process Flow Order in BPF
If you have more than one business process flow for an entity (record type), you must specify which process is automatically assigned to new records. On the action bar, select Order Process Flow. For new records or records that don’t already have a process flow associated with them, the first business process flow to which a user has access will be used.
Branching in BPF
Branching rules must be based on the steps in the stage that immediately precedes them.
You can combine multiple conditions in a rule by using the AND operator or the OR operator, but not both.
When branches are merged, either all the peer branches must be merged to a single stage, or each peer branch must end the process. A peer branch can’t merge with other branches and end the process at the same time.
Varieties of BPF
1) Embedded within a model-driven app
2) Immersive BPF - Stand-alone solution
Embedded
1) are visual representations of a series of work steps within an end-to-end process.
2) They always appear along the top of a model-driven app in their own control.
3) a component within the larger model-driven app
Immersive
1) Can exist on its own, and its built entirely within the Power Automate editor.
2) They will always exist within the default solution in an instance of CDS and are only accessible within Power Automate or the data tab that is associated with an entity in CDS.
3) simplified creation and streamlined management.
4) standalone solution.
A user always views and completes an embedded BPF within a model-driven app. An immersive BPF is a stand-alone app, and it is built solely for the purpose of completing the business process.
The immersive BPF exists as a the entire solution rather than a component of a larger model-driven app.
The main difference is how they are launched and the context that they are viewed in.
Steps to create Immersive BPF
1) Select None(Immersive Business Process) under entit drop-down list while creating the BPF.
2) New entity gets created automatically.
Form Event handlers
1) Form - OnLoad, OnSave
2) Tab - TabStateChange
3) Field -OnChange
4) IFrame - OnReadyStateComplete
Each element can have upto 50 separate event handlers configured.
Multiple forms
1) Can create more than 1 Quick Create form for an entity, but only the first one in order will be available for end users.
Charts available in model driven app
1) Column
2) Area
3) Bar
4) Line
5)Pie
6)Funnel
7)Tag
8) Donut
CABLPFTD
Editable subgrid
Editable grids support:
1) In-line editing of rows at the table or sub-grid level (includes custom tables)
2) System views and personal views
3) Web and mobile clients
4) Navigation with a keyboard or mouse
5) Grouping and sorting (you can group by/sort rows on the client-side by any column in the current view)
6) Filtering
7) Moving and resizing columns
8) Pagination
9) Saving changes from one session to another for grouping, sorting, filtering, pagination, and moving and resizing columns
10) Lookup configuration
11) Calculated columns and rollup columns
12) Business rules (Show error message, Set column value, Set business required, Set default value, Lock or unlock column)
13) JavaScript events
14) Enabling or disabling of cells based on security role
15) Users can continue to use search and charts, and can access the action bar as with read-only grids
Note -
Group by views
* work on client side only
* works only on one page of data.
* does not show you all options based on your complete data set on the server
* shows grouping only on the current page
Nested grid
Nested grids are only available for phones and tablets, not the web.
Editable grid within subgrid
To save an editable grid change within a sub-grid, the user must explicitly save before navigating out of the form.
1) Open solution explorer.
2) Open the form that contains the sub-grid.
3) Select the appropriate control, and then select Change Properties on the ribbon.
4) In the Set Properties dialog box, select Controls, select Add Control, and then follow the same steps as followed for editable subgrid on entity
Data types that aren’t editable in an editable grid
1) Customer and Partylist Lookup columns;
2) Composite (address) columns;
3) State/Status columns;
4) Lookup table-related columns (for example, the Account table includes a contact lookup, where the Contact column is editable but the EmailAddress(Contact) column is not editable).
Business rules on editable grids
- Business rules work only if conditional column is a column on the grid.
- If the column is not a column the business rules won’t work.
- Verify that each column referenced in the business rule is also included on the form.
- business rules on an editable grid do not fire if the editable grid is configured on a dashboard.
Classic Workflow
1) Stages - make the workflow logic easier to read, and explain the workflow logic. However, stages do not affect the logic or behavior of workflows. If a process has stages, all the steps within the process must be contained with a stage.
2) Steps - are a unit of business logic within a workflow. Steps can include conditions, actions, other steps, or a combination of these elements.
