WEBVTT

1
00:00:00.200 --> 00:00:05.809
A complete workflow connects the information you
collect with the work your team needs to finish.

2
00:00:05.989 --> 00:00:08.828
Our example is a volunteer application.

3
00:00:09.008 --> 00:00:15.225
The intended outcome is an approved applicant, a
completed agreement, and a clear record of what happened.

4
00:00:15.405 --> 00:00:17.424
Start by defining that outcome.

5
00:00:17.884 --> 00:00:20.947
Sketch the stages before configuring the workflow.

6
00:00:21.127 --> 00:00:23.347
The application provides the facts.

7
00:00:23.527 --> 00:00:25.566
An approver records a decision.

8
00:00:25.746 --> 00:00:29.938
An approved applicant receives the appropriate agreement for signature.

9
00:00:30.118 --> 00:00:33.489
A final handoff places the result where the team works.

10
00:00:33.669 --> 00:00:37.211
Name the person responsible when a stage needs attention.

11
00:00:37.671 --> 00:00:43.015
Describe the volunteer process to the AI builder, or start from a suitable template.

12
00:00:43.195 --> 00:00:47.218
Review the resulting fields and remove information you do not need.

13
00:00:47.398 --> 00:00:49.579
Set required answers deliberately.

14
00:00:49.759 --> 00:00:56.030
Preview the form with fictional information and check
that the submitted values support the later agreement.

15
00:00:56.490 --> 00:01:00.341
Add the approval step using the available workflow controls.

16
00:01:00.521 --> 00:01:03.943
Choose the appropriate approver and define both outcomes.

17
00:01:04.123 --> 00:01:06.758
An approval can continue to the agreement.

18
00:01:06.938 --> 00:01:09.725
A rejection should follow its own intended path.

19
00:01:09.905 --> 00:01:15.717
Confirm that the rejected application cannot
accidentally receive the next-stage document.

20
00:01:16.177 --> 00:01:21.990
Prepare the agreement using the approved submission
values, then review the generated document.

21
00:01:22.170 --> 00:01:25.732
Confirm the recipient before sending a signature request.

22
00:01:25.912 --> 00:01:29.912
A sent request still needs the required signing steps to finish.

23
00:01:30.092 --> 00:01:35.584
Continue to actions that need a completed agreement only after the completion result.

24
00:01:36.044 --> 00:01:39.344
Choose a handoff your workspace and destination support.

25
00:01:39.524 --> 00:01:43.919
A CRM action needs its own validated connector and mapping.

26
00:01:44.099 --> 00:01:47.309
Document attachment needs separate file support.

27
00:01:47.489 --> 00:01:55.188
If a required automated step is unavailable, define an approved
manual handoff and make its owner visible in the process.

28
00:01:55.648 --> 00:01:59.123
Run a fictional application through the complete process.

29
00:01:59.303 --> 00:02:04.441
Inspect the approval result, the agreement, the signing status, and the final handoff.

30
00:02:04.621 --> 00:02:07.841
Then test a rejection and one interrupted step.

31
00:02:08.021 --> 00:02:13.291
Keep the references together so you can follow
the same application throughout the rehearsal.

32
00:02:13.751 --> 00:02:18.678
Publish the version you have checked, using
the normal release process for your workspace.

33
00:02:18.858 --> 00:02:22.814
Tell the team who monitors unfinished work and who handles errors.

34
00:02:22.994 --> 00:02:27.430
Review the workflow when a form, document, or destination changes.

35
00:02:27.610 --> 00:02:31.258
A clear owner keeps a useful process useful after launch.