You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
| Item Demo | How to app is designed to help new makers learn how to make Power Apps. This table is provided as an example of the table the users will create to store items that are available to be checked out. |
47
+
| Item Checkout Demo | How to app is designed to help new makers learn how to make Power Apps. This table is provided as an example of the table that the users will create to store item checkout records. |
48
+
| Item Type Demo | How to app is designed to help new makers learn how to make Power Apps. This table is provided as an example of the table that the users will create to store item types for classification of items. |
49
+
| Item Checkout App Stage | As the user goes through the lessons in the app, the app will store the status of their progress through the app, enabling the user to pick back up where they left off. |
50
+
| Item Checkout Instructions | The instructions for proceeding through the How to app are stored in the item checkout instructions table. |
34
51
35
-
> [Skills Match Screen 15](#_Toc74830297)
36
52
37
-
> [Connect with someone by skills 15](#_Toc74830298)
38
53
39
-
> [Expert Match Screen 16](#_Toc74830299)
54
+
## Architecture model
55
+
The following diagram illustrates the way that people, systems and data interact in the How to app solution
40
56
41
-
> [Connect with an Expert 16](#_Toc74830300)
57
+
![How to app sample app architecture model](media/how-to-architecture/architecture-model.png"How to app sample app architecture model")
42
58
43
-
> [About Screen 17](#_Toc74830301)
59
+
### Connectors
44
60
45
-
> [Navigation 17](#_Toc74830302)
61
+
The following connectors are used in the How to app:
46
62
47
-
> [Body 17](#_Toc74830303)
63
+
-**Microsoft Dataverse** - Used to read and write data in Dataverse.
64
+
-**Office 365 Users** - Used to read Microsoft 365 user profile data.
48
65
49
-
[Collections 18](#_Toc74830304)
50
66
51
-
[Global Variables 19](#_Toc74830305)
52
67
53
-
# Document Objective
68
+
## Collections
69
+
The following collection is used in the How to app solution:
54
70
55
-
This document covers the following pertaining to the How-to solution:
56
-
57
-
- Data model and purpose of the various entities used.
58
-
59
-
- List of all collections and variables used.
60
-
61
-
- Detailed breakdown of each functionality.
62
-
63
-
# Introduction
64
-
65
-
How-to app in Teams offer an easy-to-use experience to create the app easily.
66
-
67
-
Benefits of using the How to app:
68
-
69
-
- Understand the basics of Power Apps
70
-
71
-
- Design the app
72
-
73
-
- Share it with colleagues in Teams
74
-
75
-
Become a Maker
76
-
77
-
# Data Model
78
-
79
-
## Entities
80
-
81
-
-**Item Demo**
82
-
83
-
A table to store Items. Details such as Name, Item type, Quantity,
84
-
Description, Created on and when was it created or modified by are stored
85
-
under the Item Demo entity.
86
-
87
-
-**Item Checkout Demo**
88
-
89
-
Item Checkout Demo stores items that are added to checkout with the checkout
90
-
status.
91
-
92
-
Details such as Name, Item, Checkout Status, Checkout Duration, Checkout
93
-
Option, Checkout Reason when the items checkout was created on, modified on
@@ -119,26 +111,24 @@ Benefits of using the How to app:
119
111
|**gblCurrUserEmail**| - global variable to store the current user email address |
120
112
| gblCurrUser | - global variable to store the current user record |
121
113
122
-
#### Detailed Steps
114
+
###OnStart execution details
123
115
124
-
1. When a user accesses the app, **gblAppLoaded** is set to false. The user’s
125
-
language code is stored in **gblUserLanguage**, with English - US being the
126
-
default one.
116
+
1. When a user accesses the app, **gblAppLoaded** is set to false. The user’s language code is stored in **gblUserLanguage**, with English - US being the default one.
127
117
128
-
2. The user’s language is then used to collect localized text used throughout
129
-
the app (e.g. label and button text) in **colLocalization**.
118
+
2. The user’s language is then used to collect localized text used throughout the app ( label and button text) in **colLocalization**.
130
119
131
120
## Welcome Screen
121
+
This section explains the collections, variables, and execution details used in the welcome screen:
132
122
133
-
134
-
135
-
#### Collections involved
123
+
### Welcome screen collections
124
+
The following collections are used in the welcome screen:
@@ -152,32 +142,25 @@ Benefits of using the How to app:
152
142
| gblAppSetting_inputMobile | - global variable to scale fonts for mobile-oriented apps. |
153
143
| gblAppSetting_inputScaleFontsBy | - global variable for scaling all fonts by a fixed amount. |
154
144
155
-
#### Detailed steps
156
-
157
-
1. If **gblAppStyles** is not blank (which means the styling variable has been
158
-
loaded),
145
+
### Welcome screen execution details
159
146
160
-
2. The loading screen will initialize all the global variables like
161
-
**gblAppStyles, gblAppSizes,** gblAppColors to show the screen and color
162
-
settings as per the user setup like dark mode or high contrast mode in Teams
163
-
desktop or in browser
147
+
1. If **gblAppStyles** is not blank (which means the styling variable has been loaded).
164
148
165
-
3. In this screen you will find **Preview App**. Click on it which will
166
-
redirect to Assets Screen
149
+
2. The loading screen will initialize all the global variables like **gblAppStyles, gblAppSizes,** gblAppColors to show the screen and color settings as per the user setup like dark mode or high contrast mode in Teams desktop or in browser.
167
150
168
-
## Items Screen
151
+
3. In this screen you will find **Preview App**. Click on it which will redirect to Assets Screen.
169
152
170
-
171
-
172
-
#### Collections involved
153
+
## Items screen
154
+
This section explains the collections, variables, and execution details used on the items screen.
173
155
156
+
### Items screen collections
157
+
The following collections are used on the items screen:
| gblAppStyles | global variable to store styling properties for all controls |
@@ -217,30 +193,22 @@ Variables involved
217
193
| gblAppColors | global variable to store the app design colors |
218
194
| gblThemeHiCo | global variable to store if Teams is running in contrast mode. |
219
195
| locSelectedItem | global variable to store the current user email address |
196
+
### Checkout screen execution details
220
197
221
-
#### Detailed steps
222
-
223
-
1. When user selects any of the item which are needed, they can click on
224
-
checkout based on availability of the item which are stored in
225
-
locSelectedItem item.
198
+
1. When user selects any of the item which are needed, they can click on checkout based on availability of the item which are stored in locSelectedItem item.
226
199
227
-
2. Once the item is checked out the confirmation message will be shown from
228
-
locShowCheckoutConfirmation.
200
+
2. Once the item is checked out the confirmation message will be shown from locShowCheckoutConfirmation.
229
201
230
202
## My Checkout Screen
231
-
232
-
233
-
234
-
235
-
236
-
#### Collections involved
237
-
203
+
This section explains the collections, variables, and execution details used on the my checkout screen.
204
+
### My checkout collections
205
+
The following collections are used on the my checkout screen:
0 commit comments