WEBVTT

00:00.333 --> 00:04.295
In this demonstration, we're
going to look at document relationships

00:04.295 --> 00:07.298
when the source is
set to be version-specific,

00:07.590 --> 00:10.719
but we're also carrying
forward relationships.

00:12.095 --> 00:15.098
So here I'll start with 0.1 of my source.

00:15.390 --> 00:19.644
And we have a target relationship
to 0.1 of my target document.

00:20.562 --> 00:23.565
So if I were to version the source,

00:27.360 --> 00:27.861
We'll see

00:27.861 --> 00:31.906
that the relationship
is maintained to 0.1 of the target.

00:32.741 --> 00:36.036
And if we were to look back at the 0.1

00:36.036 --> 00:39.039
version of the source.

00:39.372 --> 00:40.415
That relationship

00:40.415 --> 00:43.418
is maintained there as well.

00:44.252 --> 00:46.713
Now let's look at the target.

00:46.713 --> 00:49.716
So if I go to the target document 0.1,

00:50.633 --> 00:54.846
if I use ‘Where Used’ to see
what relationship this has going

00:54.846 --> 00:59.559
the other direction, you'll see that
it's actually listing the source twice.

00:59.559 --> 01:04.064
We're listing version 0.1 and 0.2.

01:04.814 --> 01:07.275
If I were to go back to the target here,

01:07.275 --> 01:10.070
and let's say that I version up
the target document,

01:13.031 --> 01:16.034
if I again go to ‘Where Used’ here,

01:18.495 --> 01:20.246
we'll see that nothing has changed.

01:20.246 --> 01:24.542
We're carrying forward those versions
as the target versions up, but we're

01:24.542 --> 01:29.547
listing out the specific versions
of the source as that is versioned up.

01:30.298 --> 01:33.510
But for the source itself,
this is always going to

01:33.510 --> 01:37.764
just maintain
showing the latest version of the target.