WEBVTT

00:00.208 --> 00:02.877
In this demonstration,
we're going to take a look at how document

00:02.877 --> 00:06.423
relationships behave
when the target is version-specific,

00:06.715 --> 00:09.843
but we're also carrying forward
those target versions.

00:12.387 --> 00:15.807
So I'm starting here
with a 0.1 of my source,

00:16.224 --> 00:20.186
and we're pointing to a 0.1 of a target
through a supporting document

00:20.186 --> 00:22.230
relationship.

00:22.230 --> 00:25.859
If I go ahead
and create a new version of my source,

00:25.859 --> 00:28.862
which will create a 0.2.

00:30.113 --> 00:32.365
If I look at my relationships here,

00:32.365 --> 00:35.577
we've still got that relationship
to the target maintained.

00:36.453 --> 00:38.747
And if I were to look at the ‘Version
History’

00:38.747 --> 00:41.750
here,

00:42.876 --> 00:43.918
that relationship

00:43.918 --> 00:46.921
is maintained here as well.

00:47.756 --> 00:51.551
But in this scenario
we have target version specificity.

00:51.676 --> 00:54.304
So if I go to my target document,

00:54.304 --> 00:58.433
if we were to start here by looking at
the relationship from the other direction,

00:58.975 --> 01:03.480
when I go to ‘Where Used’, we're
going to see that 0.1 of the target

01:03.897 --> 01:06.691
is pointing
to the latest version of source.

01:08.234 --> 01:09.027
Now if I go

01:09.027 --> 01:12.238
create a new version of the target,

01:12.238 --> 01:16.201
so I'm going to upload a new document,
create a 0.2

01:16.201 --> 01:17.786
version.

01:19.662 --> 01:22.665
When I go to look at ‘Where Used’,

01:24.250 --> 01:25.168
we're going to see

01:25.168 --> 01:28.171
that the relationship here
is carried forward.

01:28.338 --> 01:31.800
So 0.2 of the target is looking

01:31.800 --> 01:34.803
at the latest version of the source.

01:35.678 --> 01:40.183
Now if I look at the source document
itself and go to the relationships

01:41.101 --> 01:44.104
we're actually going to see,
the target is listed twice here.

01:44.312 --> 01:49.609
So we're actually listing 0.1
and 0.2 separately here.

01:50.110 --> 01:54.989
So as that target is versioned up,
we're still maintaining version specificity

01:55.281 --> 01:57.951
We're listing out each version.

01:57.951 --> 02:02.455
But those versions are carrying forward
as the target moves up.