WEBVTT

1
00:00:02.000 --> 00:00:19.300
Your stores are maintained by a team of stewards, and you want a data
owner to check every change before it becomes master data. That is an
approval workflow. It takes three settings, in a fixed order, and then
two people: one who submits, and one who decides. Let's set it up on
Store.

2
00:00:19.801 --> 00:00:27.901
Approval rights start on the role, not on the entity. Open Settings,
Access Management, and the Roles tab.

3
00:00:28.410 --> 00:00:49.310
Open Data Owners. Under the name are two checkboxes: Administrator,
and Approver — can approve changes and requests. Tick Approver. Every
member of this role can now be picked as an approver on an entity.
Without this flag the approver list on every entity stays empty,
whatever else you set.

4
00:00:49.822 --> 00:00:54.022
Click Save. That is the first setting, and the one people forget.

5
00:00:54.528 --> 00:01:03.778
Now the entity. Open the Entities tab. Every entity carries a badge:
free, or approval. Store is free. Pick it.

6
00:01:04.278 --> 00:01:21.678
Step 1. Switch on Changes require approval. From now on a save on
Store creates a request instead of writing to the data. Leave Approver
may approve own changes off — that is the four-eyes rule: whoever
submits a change cannot approve it themselves.

7
00:01:22.187 --> 00:01:36.437
Step 2. Who can approve. Click Search and add approver, and pick Marta
Lindqvist. She is on the list because Data Owners carries the Approver
flag. The mail icon means she gets an email for every new request.

8
00:01:36.945 --> 00:01:46.045
The approval strategy: One approver is sufficient, or All approvers
must agree. Keep One approver. Click Save.

9
00:01:46.551 --> 00:02:00.501
Saved, and Store now reads approval in the list. One warning: approval
on with nobody assigned is a trap — stewards can still submit, but no
one can approve, and only an administrator can clear the queue.

10
00:02:01.004 --> 00:02:11.954
Now the steward's side. Aisha Rahman is in Data Stewards: she can edit
Store, but she cannot approve. Signed in as Aisha, open the Store
grid.

11
00:02:12.463 --> 00:02:18.113
Amsterdam took on staff. Set Employees to 12, and click Save.

12
00:02:18.628 --> 00:02:30.778
Instead of the usual save dialog, Submit changes for approval opens.
It lists what changed, and takes a note for the approver. Type the
note, then click Submit for approval.

13
00:02:31.289 --> 00:02:39.039
Submitted for approval, with a request number. Nothing has been
written to the master data yet. Close it.

14
00:02:40.073 --> 00:02:51.323
Back in the grid, Amsterdam still shows eight employees, and the row
is hatched with a padlock where the checkbox was. Nobody can edit that
row until the request is decided.

15
00:02:51.833 --> 00:03:00.883
Over to Marta. Signed in as her, the bell in the header is amber: one
submission awaiting your approval. Click it, then Go to Approvals.

16
00:03:01.397 --> 00:03:07.597
My Approvals lists the request: Store, submitted by Aisha, one edit,
Pending. Open it.

17
00:03:08.112 --> 00:03:21.312
Click the row to expand the change: Employees, eight to twelve, and
Aisha's note on the right. Three decisions: Approve all, Send back,
and Reject. Send back and Reject ask for a reason. Click Approve all.

18
00:03:23.374 --> 00:03:32.424
Approved: all changes have been applied to the master data. Close the
request, and the toast tells you Aisha has been notified by email.

19
00:03:32.935 --> 00:03:38.485
And in the grid, Amsterdam has twelve employees and the padlock is
gone.

20
00:03:38.987 --> 00:03:53.137
Aisha's bell turns green: your submission was approved. My Submissions
shows the request with Approved and the date. A rejected or returned
request shows up here too, with the reviewer's reason, so she knows
what to fix.

21
00:03:53.645 --> 00:04:12.545
Two corners. Administrators may review any request on any entity
without being assigned, and they have Force approve, which skips the
workflow and is written to the audit log. And with All approvers must
agree, every assigned approver votes before anything is applied — but
one rejection closes the request at once.

22
00:04:13.056 --> 00:04:28.306
That is approvals on Store: the flag on the role, the switch and the
approvers on the entity, and from then on every change waits for a
decision before it becomes master data. The written guide is in the
docs at primentra.com.