WEBVTT

1
00:00:00.000 --> 00:00:01.909
The training team needs to understand a

2
00:00:01.910 --> 00:00:04.882
review handover. We will use activity history

3
00:00:04.882 --> 00:00:06.722
to find a recorded action and connect

4
00:00:06.722 --> 00:00:08.819
it to the affected file. The page

5
00:00:08.898 --> 00:00:11.643
shows recorded actions, when they occurred, the

6
00:00:11.759 --> 00:00:14.021
person or system involved, and the affected

7
00:00:14.025 --> 00:00:16.621
item. These records are not edited on

8
00:00:16.626 --> 00:00:19.183
this page. Start with the period covering

9
00:00:19.186 --> 00:00:22.036
the event. A narrow range reduces unrelated

10
00:00:22.405 --> 00:00:24.376
activity, but widen it if the expected

11
00:00:24.489 --> 00:00:27.262
record may fall outside that window. Our

12
00:00:27.351 --> 00:00:29.140
training reviewer is looking for the action

13
00:00:29.140 --> 00:00:32.908
that requested co-sign on DEMO 001. Filter

14
00:00:32.918 --> 00:00:35.105
by an appropriate event type and inspect

15
00:00:35.105 --> 00:00:37.556
the affected item. The actor can be

16
00:00:37.564 --> 00:00:39.896
a person or a system. In this

17
00:00:39.904 --> 00:00:42.860
course all identities are fictional role labels,

18
00:00:42.868 --> 00:00:45.434
so no real names or emails appear.

19
00:00:45.569 --> 00:00:48.480
An upload, completed analysis and review action

20
00:00:48.484 --> 00:00:51.620
are distinct events. Their order provides context,

21
00:00:51.620 --> 00:00:53.498
but does not prove that every engineering

22
00:00:53.575 --> 00:00:56.290
issue was resolved. Open the relevant file

23
00:00:56.296 --> 00:00:58.281
or supporting record to read its current

24
00:00:58.671 --> 00:01:01.039
result. An old activity event should not

25
00:01:01.199 --> 00:01:03.666
replace checking the current state. If you

26
00:01:03.721 --> 00:01:06.751
have export permission, use the filtered CSV

27
00:01:06.765 --> 00:01:09.808
export for an appropriate audit task. Treat

28
00:01:09.808 --> 00:01:12.421
the exported activity information with the same

29
00:01:12.435 --> 00:01:15.965
care as the platform view. Pause here.

30
00:01:15.965 --> 00:01:18.924
Find a training review event, identify its

31
00:01:19.125 --> 00:01:22.173
affected file and explain what further evidence

32
00:01:22.193 --> 00:01:24.520
you need before concluding that the file

33
00:01:24.540 --> 00:01:25.693
was approved.
