WEBVTT

00:00:00.079 --> 00:00:03.539
Record numbers help people find and distinguish documents during

00:00:03.539 --> 00:00:05.530
a handover or a data migration.

00:00:06.010 --> 00:00:09.750
This walkthrough starts on Records Settings in the fictional Firehouse

00:00:09.750 --> 00:00:11.300
fifty-one training department.

00:00:11.680 --> 00:00:16.690
We will inspect the numbering controls, save one change, verify what persisted

00:00:16.870 --> 00:00:18.520
and restore the original pattern.

00:00:19.030 --> 00:00:22.239
The department name and settings page should match the department

00:00:22.239 --> 00:00:23.569
you intend to administer.

00:00:23.680 --> 00:00:25.309
Scroll to Record numbering.

00:00:25.850 --> 00:00:29.940
Number pattern currently contains the prefix token, a hyphen, the

00:00:29.940 --> 00:00:33.789
four-digit year token, another hyphen and the sequence token.

00:00:34.320 --> 00:00:36.959
The help below explains what each token writes.

00:00:37.329 --> 00:00:41.839
Prefix uses the record type prefix, year includes the numbering year,

00:00:42.130 --> 00:00:43.880
and sequence supplies the counter.

00:00:44.329 --> 00:00:48.319
Changing this pattern does not renumber records that already have numbers.

00:00:48.700 --> 00:00:51.239
Read that impact before applying a new format.

00:00:51.440 --> 00:00:54.039
Sequence digits is four in this department.

00:00:54.469 --> 00:00:57.880
The help shows that four digits writes a zero-padded value

00:00:57.920 --> 00:01:00.099
such as zero one eight four.

00:01:00.519 --> 00:01:03.200
This control accepts three through eight digits.

00:01:03.610 --> 00:01:08.079
Changing the width keeps each sequence's next number; it is not the same as

00:01:08.079 --> 00:01:09.860
choosing a different next counter.

00:01:10.269 --> 00:01:13.419
Definitions that have their own numbering keep their own width.

00:01:13.829 --> 00:01:17.190
In this exercise, we leave the four-digit setting as it is.

00:01:17.389 --> 00:01:19.899
Numbering year starts has a month and day.

00:01:20.340 --> 00:01:22.340
January first is selected here.

00:01:22.780 --> 00:01:25.960
The displayed help explains how a fiscal-year start affects

00:01:25.960 --> 00:01:27.689
sequences that include the year.

00:01:28.099 --> 00:01:30.939
This setting is separate from call numbering, which has its

00:01:31.000 --> 00:01:32.830
own year start on Call Settings.

00:01:33.189 --> 00:01:37.099
Review the policy your department actually follows before changing either.

00:01:37.499 --> 00:01:40.890
This demonstration keeps the existing January-first value.

00:01:41.190 --> 00:01:46.790
Record type prefixes lists each type, its default and a Number prefix box.

00:01:47.170 --> 00:01:52.390
The visible defaults include Run, R U N; Training, T R N;

00:01:52.790 --> 00:01:56.659
Work, W R K; and Meeting, M T G.

00:01:57.099 --> 00:01:59.249
Leave a box blank to keep its default.

00:01:59.640 --> 00:02:04.150
The help explains that a new prefix starts its own sequence, and types given

00:02:04.150 --> 00:02:06.349
the same prefix share one sequence.

00:02:06.779 --> 00:02:10.630
Prefixes take effect when the number pattern includes the prefix token.

00:02:11.040 --> 00:02:14.390
Choose them deliberately rather than using a cosmetic change that

00:02:14.480 --> 00:02:16.410
accidentally joins two counters.

00:02:16.630 --> 00:02:20.190
For this local exercise, replace the two hyphens in Number

00:02:20.190 --> 00:02:21.750
pattern with underscores.

00:02:22.159 --> 00:02:25.730
Keep the same prefix, four-digit year and sequence tokens.

00:02:26.099 --> 00:02:29.099
The example beside the field now uses underscores too.

00:02:29.580 --> 00:02:31.940
This is still an unsaved form value.

00:02:32.320 --> 00:02:36.060
The format of the example is useful feedback, but it does not prove

00:02:36.060 --> 00:02:39.279
the department has saved the change or issued a new record number.

00:02:39.479 --> 00:02:43.659
Scroll to the bottom of Records Settings, where Save and Cancel are visible.

00:02:44.170 --> 00:02:46.999
Review your intended edit before choosing Save.

00:02:47.380 --> 00:02:51.290
This demonstration changes the number pattern only; it does not submit a

00:02:51.290 --> 00:02:55.389
record, raise a counter or request delivery to an external service.

00:02:55.800 --> 00:02:59.700
Use Save once, then verify the returned settings page instead

00:02:59.700 --> 00:03:03.009
of assuming that typing in the field completed the configuration.

00:03:03.250 --> 00:03:06.569
The returned page displays Records settings saved.

00:03:06.959 --> 00:03:09.500
This confirms that the settings form was accepted.

00:03:09.939 --> 00:03:13.670
We still need to verify the particular value we intended to change.

00:03:14.090 --> 00:03:17.399
A general success notice is useful, but reading the saved

00:03:17.399 --> 00:03:21.130
field and its effect gives an administrator a more complete check.

00:03:21.270 --> 00:03:24.830
Reopening Records Settings shows the underscore-separated pattern

00:03:24.830 --> 00:03:27.930
in Number pattern, with the matching example alongside it.

00:03:28.410 --> 00:03:30.779
This is a fresh page load after saving.

00:03:31.290 --> 00:03:34.679
Compare the full pattern, including each token and separator,

00:03:34.739 --> 00:03:36.040
with your intended format.

00:03:36.500 --> 00:03:40.950
The result confirms persistence of this local setting; the example is still an

00:03:40.950 --> 00:03:43.519
example rather than a newly issued record.

00:03:43.750 --> 00:03:47.199
The saved pattern changes Next numbers for twenty twenty-six.

00:03:47.690 --> 00:03:52.839
The Run and Training previews now have underscores and end in zero zero zero one.

00:03:53.360 --> 00:03:56.209
The text around the sequence token changed, so this

00:03:56.209 --> 00:03:58.079
format has its own sequence.

00:03:58.499 --> 00:04:01.880
Raise next to is a separate control for carrying on from

00:04:01.880 --> 00:04:03.440
previously issued numbers.

00:04:03.850 --> 00:04:06.720
Leave it alone when you do not intend to raise a counter.

00:04:07.220 --> 00:04:10.200
Viewing this table does not issue the previewed numbers.

00:04:10.450 --> 00:04:14.559
After the exercise, the original hyphen-separated pattern was restored.

00:04:15.030 --> 00:04:19.570
Record numbering now shows the original prefix, year and sequence arrangement.

00:04:20.089 --> 00:04:23.979
Restore a practice change only when that is your intended configuration.

00:04:24.400 --> 00:04:27.920
Changing separators back is a format decision; it is not a

00:04:27.920 --> 00:04:31.449
way to erase previously issued numbers or reset a counter.

00:04:31.670 --> 00:04:35.599
The original format now shows Training ending in zero zero zero

00:04:35.630 --> 00:04:39.549
three, the same next-number preview it had before the demonstration.

00:04:40.030 --> 00:04:42.599
Run ends in zero zero zero one.

00:04:43.139 --> 00:04:46.829
Restoring the earlier format resumed its existing sequence rather

00:04:46.829 --> 00:04:48.489
than restarting Training at one.

00:04:48.899 --> 00:04:51.479
No new records were issued during this exercise.

00:04:51.989 --> 00:04:55.960
When importing from another system, review Raise next to against the

00:04:55.960 --> 00:04:59.559
numbers already issued before applying a higher starting point.

00:04:59.679 --> 00:05:04.080
Other record numbers has separate rows for Records requests, Occupancies,

00:05:04.210 --> 00:05:07.250
Inspections, Permits and Investigations.

00:05:07.600 --> 00:05:12.469
Each visible row has a Number pattern, Sequence digits and a next-number area.

00:05:12.879 --> 00:05:16.159
The help explains that blank patterns keep the built-in numbers

00:05:16.399 --> 00:05:19.700
and that these types follow the record-numbering year start above.

00:05:20.130 --> 00:05:22.880
Review the particular row you intend to administer.

00:05:23.280 --> 00:05:26.540
This recording inspects those controls without saving a custom

00:05:26.540 --> 00:05:28.489
pattern for these other record types.

00:05:28.669 --> 00:05:32.730
A consistent numbering policy helps security teams find post reports,

00:05:33.000 --> 00:05:36.770
wildland contractors distinguish crew-support work, and industrial

00:05:36.770 --> 00:05:38.820
teams coordinate equipment records.

00:05:39.200 --> 00:05:43.060
Community paramedicine and mental health teams can organize appropriate

00:05:43.060 --> 00:05:46.719
service documentation, while search-and-rescue teams can distinguish

00:05:46.719 --> 00:05:48.330
training and support records.

00:05:48.719 --> 00:05:52.090
Fire and E M S departments can use the same pattern review.

00:05:52.539 --> 00:05:56.859
Agree on the format, inspect the correct controls, save deliberately

00:05:56.889 --> 00:06:00.129
and verify both persistence and the next-number preview.
