1
00:00:00,250 --> 00:00:04,616
Conditional logic sends customers to the questions that apply to them.

2
00:00:04,616 --> 00:00:07,791
In this example, website projects go to Features,

3
00:00:07,791 --> 00:00:10,966
while mobile applications go to Type of application.

4
00:00:10,966 --> 00:00:14,538
We will inspect both routes, explain how the conditions

5
00:00:14,538 --> 00:00:18,110
work, and test the result from the customer’s side.

6
00:00:19,017 --> 00:00:22,075
In Steps manager, click the pencil on the

7
00:00:22,075 --> 00:00:24,751
line from Mobile or website to Features.

8
00:00:24,751 --> 00:00:27,427
The panel shows the origin and destination.

9
00:00:27,427 --> 00:00:31,250
Conditions belong to this connection: they decide whether the customer

10
00:00:31,250 --> 00:00:34,690
can follow this route when leaving the previous step.

11
00:00:35,617 --> 00:00:39,498
Click Add a condition when the connection has no rule yet.

12
00:00:39,498 --> 00:00:41,967
Choose the Website component as the element,

13
00:00:41,967 --> 00:00:44,437
then choose Is selected as the condition.

14
00:00:44,437 --> 00:00:49,023
This is a selection check, so you do not need a numeric value.

15
00:00:49,023 --> 00:00:51,846
Save the connection when the rule is correct.

16
00:00:52,750 --> 00:00:57,359
Open the other connection, from Mobile or website to Type of application.

17
00:00:57,359 --> 00:01:00,815
Its rule should check whether Mobile App is selected.

18
00:01:00,815 --> 00:01:05,808
The two choices are alternatives, so each route has its own clear condition.

19
00:01:05,808 --> 00:01:10,417
Avoid leaving an extra unconditional connection that competes with the intended branch.

20
00:01:11,350 --> 00:01:15,889
Use All conditions must be filled when every rule must be true.

21
00:01:15,889 --> 00:01:17,780
This is an AND relationship.

22
00:01:17,780 --> 00:01:20,806
Use One of the conditions must be filled

23
00:01:20,806 --> 00:01:23,832
when any single rule can allow the route.

24
00:01:23,832 --> 00:01:25,724
This is an OR relationship.

25
00:01:25,724 --> 00:01:29,506
With just one condition, both settings produce the same decision.

26
00:01:30,417 --> 00:01:33,454
You can branch again later in the journey.

27
00:01:33,454 --> 00:01:36,492
Here, a Game selection leads to Game Design.

28
00:01:36,492 --> 00:01:39,530
Other application types can continue toward Targeted devices.

29
00:01:39,530 --> 00:01:43,327
Keep the route map readable, and make sure every supported

30
00:01:43,327 --> 00:01:46,745
choice has a way to reach the final step.

31
00:01:47,650 --> 00:01:50,417
Open the form preview and choose Website.

32
00:01:50,417 --> 00:01:52,788
Continue and confirm that Features appears.

33
00:01:52,788 --> 00:01:57,926
Start again with Mobile App and confirm that Type of application appears instead.

34
00:01:57,926 --> 00:02:01,483
Test the actual navigation; a correctly drawn line alone

35
00:02:01,483 --> 00:02:05,040
does not prove that the conditions match your choices.

36
00:02:05,950 --> 00:02:11,143
Finally, test what happens when the customer goes back and changes a choice.

37
00:02:11,143 --> 00:02:15,537
Check the next step, the selected items, and the final total.

38
00:02:15,537 --> 00:02:17,534
Repeat this for each branch.

39
00:02:17,534 --> 00:02:20,729
A reliable conditional form stays coherent throughout the

40
00:02:20,729 --> 00:02:23,526
journey, including when customers change their minds.