WEBVTT

00:00:00.029 --> 00:00:03.150
A department record form needs the right app availability

00:00:03.150 --> 00:00:05.050
before field staff can use it.

00:00:05.460 --> 00:00:08.770
On its definition page, scroll to Client surfaces.

00:00:09.210 --> 00:00:13.640
This existing training form has Responder selected and IC clear.

00:00:14.069 --> 00:00:16.120
Unit and Dispatch are also clear.

00:00:16.610 --> 00:00:20.200
Read this group of choices for the particular form you intend to offer.

00:00:20.590 --> 00:00:24.250
A form being available in one application does not tell you which

00:00:24.299 --> 00:00:26.209
other applications are selected here.

00:00:26.370 --> 00:00:30.210
For the practice change, we use a separate department-owned form called

00:00:30.339 --> 00:00:33.039
Training Only, IC coordination note.

00:00:33.470 --> 00:00:37.870
The heading identifies version one as Draft, and the creation notice says to

00:00:37.870 --> 00:00:40.639
edit the schema, validate, then publish.

00:00:41.099 --> 00:00:43.860
Lifecycle preset currently shows Quick Entry.

00:00:44.279 --> 00:00:48.440
Confirm the form name and version state before preparing its app choices.

00:00:48.750 --> 00:00:52.910
This keeps the availability decision tied to the intended definition version.

00:00:53.149 --> 00:00:58.679
In Client surfaces, clear Responder and select IC for this separate practice form.

00:00:59.150 --> 00:01:00.960
Unit and Dispatch remain clear.

00:01:01.340 --> 00:01:05.250
The pictured choices now target IC when this version is published.

00:01:05.649 --> 00:01:08.569
Allow offline is also clear for this exercise.

00:01:08.970 --> 00:01:13.169
Review the entire group before saving, rather than assuming that selecting one

00:01:13.169 --> 00:01:15.310
app automatically selects the others.

00:01:15.679 --> 00:01:18.169
These are prepared draft settings at this stage.

00:01:18.359 --> 00:01:21.720
At the bottom of the definition editor, choose Validate.

00:01:22.159 --> 00:01:25.430
The returned page displays The definition is valid.

00:01:25.930 --> 00:01:28.559
Read that result before moving toward publication.

00:01:29.049 --> 00:01:32.299
Validation is a useful checkpoint for the form definition you are

00:01:32.299 --> 00:01:36.529
preparing; it does not tell an operator which app choices you intended.

00:01:36.969 --> 00:01:40.729
Compare the configuration with the requested departmental use as well

00:01:40.729 --> 00:01:42.770
as checking that validation succeeds.

00:01:42.880 --> 00:01:46.159
Use Save draft to retain the prepared configuration.

00:01:46.530 --> 00:01:50.439
The returned page displays Draft saved, while the heading still

00:01:50.439 --> 00:01:52.319
identifies the version as Draft.

00:01:52.760 --> 00:01:54.579
Read that state before proceeding.

00:01:55.090 --> 00:01:58.590
Review impact and publish is the next action for deciding whether

00:01:58.590 --> 00:02:00.449
this version is ready to be offered.

00:02:00.849 --> 00:02:04.980
Keeping validation, saving and publication as explicit checkpoints

00:02:05.209 --> 00:02:08.859
makes it easier to explain where a form is in the setup process.

00:02:09.010 --> 00:02:13.490
Open Review impact and publish, then inspect Client readiness.

00:02:13.920 --> 00:02:18.109
The Enabled column and Client surfaces column answer different questions.

00:02:18.449 --> 00:02:22.390
Here every app is enabled, but only the Incident Command row

00:02:22.390 --> 00:02:24.600
has Yes under Client surfaces.

00:02:24.960 --> 00:02:29.369
Responder, Unit and Dispatch say this version is not offered to that app.

00:02:29.769 --> 00:02:34.939
The IC row says clients at records version one B or later can author this version.

00:02:35.369 --> 00:02:39.689
Read the complete row, including its capability requirement, before publishing.

00:02:39.919 --> 00:02:43.449
The impact page explains that publishing freezes the version.

00:02:44.019 --> 00:02:48.329
After reviewing the intended form and its app readiness, choose Publish.

00:02:48.680 --> 00:02:53.520
The resulting definition page identifies version one as Published and displays

00:02:53.520 --> 00:02:55.480
the published, read-only notice.

00:02:55.850 --> 00:02:59.680
Verify that returned state before telling staff the setup is complete.

00:03:00.120 --> 00:03:03.729
The separate IC record walkthrough shows this published form being

00:03:03.729 --> 00:03:05.380
selected and used in the app.

00:03:05.709 --> 00:03:09.019
Open new draft is available for the next definition change.

00:03:09.519 --> 00:03:12.839
Use the version heading to keep published forms and future work

00:03:12.839 --> 00:03:14.390
clear during administration.

00:03:14.940 --> 00:03:19.070
The same availability review can support a security handover form, a

00:03:19.070 --> 00:03:23.370
search-and-rescue coordination note, community paramedicine or mental health

00:03:23.370 --> 00:03:28.430
team documentation, wildland contractor records, industrial exercise forms,

00:03:28.690 --> 00:03:31.120
and fire or E M S department records.

00:03:31.659 --> 00:03:34.589
Choose app availability deliberately for the people who

00:03:34.589 --> 00:03:36.460
will actually fill out each form.
