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
Copy file name to clipboardExpand all lines: docs/sp-add-ins/incident-manager-a-cloud-business-add-in-tutorial.md
+39-45Lines changed: 39 additions & 45 deletions
Original file line number
Diff line number
Diff line change
@@ -1,9 +1,3 @@
1
-
---
2
-
title: Incident manager: A cloud business add-in tutorial
3
-
ms.prod: SHAREPOINT
4
-
ms.assetid: 8dec09e6-e197-4f68-bcc2-ca41105c5d61
5
-
---
6
-
7
1
8
2
# Incident manager: A cloud business add-in tutorial
9
3
By using the **Cloud Business Add-in** template in Visual Studio, you can create a SharePoint hosted in which mobile users can view, add, and update data from remote locations by using modern, touch-oriented devices such as phones and tablets. In this tutorial, you'll create an add-in for a fictional Contoso Fire Department to handle on-scene incident management. The walkthrough covers the core concepts of building a Cloud Business Add-in as well as more advanced concepts such as integrating SharePoint lists and document libraries.
@@ -56,7 +50,7 @@ You will build the mobile add-in that will be used to enter basic information ab
56
50
57
51
58
52
59
-
53
+
60
54
61
55
62
56
@@ -152,7 +146,7 @@ You will build the mobile add-in that will be used to enter basic information ab
152
146
153
147
154
148
155
-
149
+
156
150
157
151
158
152
@@ -215,7 +209,7 @@ You will build the mobile add-in that will be used to enter basic information ab
215
209
216
210
217
211
218
-
212
+
219
213
220
214
221
215
@@ -252,7 +246,7 @@ You will build the mobile add-in that will be used to enter basic information ab
252
246
253
247
254
248
255
-
249
+
256
250
257
251
258
252
This creates a zero or one to many relationship between incidents and patients. An incident record doesn't have to have a patient, but every patient has to have a related incident record.
@@ -294,7 +288,7 @@ You will build the mobile add-in that will be used to enter basic information ab
Browse, View Details, and Add/Edit screens are added to the HTMLClient project. The Browse screen is automatically set as the home screen for the application, and the necessary commands for launching the View and Add/Edit screens are automatically provided.
@@ -342,7 +336,7 @@ You will build the mobile add-in that will be used to enter basic information ab
@@ -690,7 +684,7 @@ The first step is to add a couple of pre-populated list templates to your develo
690
684
691
685
692
686
693
-
687
+
694
688
695
689
696
690
@@ -705,7 +699,7 @@ The first step is to add a couple of pre-populated list templates to your develo
705
699
706
700
707
701
708
-
702
+
709
703
710
704
711
705
The entities are added to a new **Developer Data** node under the **Data Sources** node in **Solution Explorer**, and the **ContosoApparatus** entity opens in the entity designer.
@@ -745,7 +739,7 @@ The first step is to add a couple of pre-populated list templates to your develo
@@ -885,7 +879,7 @@ On the scene of an incident the Incident Commander has to document many things,
885
879
886
880
887
881
888
-
882
+
889
883
890
884
891
885
@@ -918,7 +912,7 @@ On the scene of an incident the Incident Commander has to document many things,
918
912
919
913
920
914
921
-
915
+
922
916
923
917
924
918
In order to associate the document library with your add-in, the document library must contain a custom column that maps to a unique field in your entity. In this case the **IncidentNumber** column maps to the **IncidentNumber** field in the **Incidents** entity.
@@ -943,7 +937,7 @@ On the scene of an incident the Incident Commander has to document many things,
943
937
944
938
945
939
946
-
940
+
947
941
948
942
949
943
An **IncidentDocuments.lsml** node is added to Solution Explorer.
@@ -971,7 +965,7 @@ On the scene of an incident the Incident Commander has to document many things,
971
965
972
966
973
967
974
-
968
+
975
969
976
970
977
971
@@ -989,7 +983,7 @@ On the scene of an incident the Incident Commander has to document many things,
@@ -1328,7 +1322,7 @@ So far you've only run the add-in in Debug mode, which uses SharePoint to provid
1328
1322
1329
1323
1330
1324
1331
-
1325
+
1332
1326
1333
1327
1334
1328
@@ -1343,7 +1337,7 @@ So far you've only run the add-in in Debug mode, which uses SharePoint to provid
1343
1337
1344
1338
1345
1339
1346
-
1340
+
1347
1341
1348
1342
1349
1343
@@ -1358,7 +1352,7 @@ So far you've only run the add-in in Debug mode, which uses SharePoint to provid
1358
1352
1359
1353
1360
1354
1361
-
1355
+
1362
1356
1363
1357
1364
1358
The add-in opens in the browser and looks exactly the same as when you ran the add-in in Debug mode. Notice that the data you entered during development is gone. When deploying the add-in, the database is deployed but not the data.
@@ -1373,7 +1367,7 @@ So far you've only run the add-in in Debug mode, which uses SharePoint to provid
1373
1367
1374
1368
1375
1369
1376
-
1370
+
1377
1371
1378
1372
1379
1373
You can also verify your add-in on a mobile device. Sign in to your SharePoint site from the web browser on your device, and then start the add-in.
@@ -1385,7 +1379,7 @@ So far you've only run the add-in in Debug mode, which uses SharePoint to provid
1385
1379
1386
1380
1387
1381
1388
-
1382
+
0 commit comments