WEBVTT

00:00:01.300 --> 00:00:04.817
Access means that the app allows you to use an offering under

00:00:04.817 --> 00:00:08.333
the applicable requirements. Activation is a separate choice about whether its decision

00:00:08.333 --> 00:00:11.850
engine is enabled. In between, there can also be a configuration step

00:00:11.850 --> 00:00:15.367
that selects the strategy for a mode. Understanding these stages helps you

00:00:15.367 --> 00:00:18.883
avoid two mistakes: assuming a subscription has started trading, and assuming that

00:00:18.883 --> 00:00:22.400
adding a card to a workspace has already turned its engine on.

00:00:22.900 --> 00:00:26.491
In the current strategy detail view, an eligible strategy that has not

00:00:26.491 --> 00:00:30.083
been configured for Paper can show Add to Paper. In our isolated

00:00:30.083 --> 00:00:33.674
demonstration, selecting that action adds it to the Paper setup with the

00:00:33.674 --> 00:00:37.265
decision engine off. This gives you a chance to review its settings.

00:00:37.265 --> 00:00:40.857
Read the returned label. Adding and enabling are separate steps here; do

00:00:40.857 --> 00:00:43.550
not assume that the first click authorizes new entries.

00:00:44.050 --> 00:00:47.927
Once the strategy is configured, the mode control can display Decision engine

00:00:47.927 --> 00:00:51.805
Off or Decision engine On. The Trading card and its settings also

00:00:51.805 --> 00:00:55.682
show enabled or disabled state. These labels concern that strategy in that

00:00:55.682 --> 00:00:59.559
mode. They do not establish the state of another strategy, another mode,

00:00:59.559 --> 00:01:03.436
or every exchange connection. Always keep the mode label in the same

00:01:03.436 --> 00:01:05.375
mental sentence as the engine state.

00:01:05.875 --> 00:01:09.684
Some offerings require a subscription or another form of access. Read the

00:01:09.684 --> 00:01:13.493
current price, billing interval, and terms before any real purchase. A checkout

00:01:13.493 --> 00:01:17.302
may take you through a separate payment flow. Starting that flow is

00:01:17.302 --> 00:01:21.111
not proof that it finished successfully. When you return, verify the access

00:01:21.111 --> 00:01:24.920
status actually shown. Our lesson uses existing example access and does not

00:01:24.920 --> 00:01:26.825
require you to buy a subscription.

00:01:27.325 --> 00:01:31.608
Access can also be affected by the offering's availability, an account restriction,

00:01:31.608 --> 00:01:35.891
or a version or lifecycle notice. If the control gives a reason

00:01:35.891 --> 00:01:40.173
instead of an available action, read that reason first. An access restriction

00:01:40.173 --> 00:01:44.456
and a connection problem call for different investigations. Clicking repeatedly or increasing

00:01:44.456 --> 00:01:48.025
a budget does not resolve every kind of unavailable state.

00:01:48.525 --> 00:01:52.504
Imagine that you have an active subscription but the Paper decision engine

00:01:52.504 --> 00:01:56.482
is off. There is no contradiction. You have access, but you have

00:01:56.482 --> 00:02:00.461
not currently authorized that engine to make new entry decisions in Paper.

00:02:00.461 --> 00:02:04.440
Now imagine that Paper is enabled while Live remains unavailable. Those labels

00:02:04.440 --> 00:02:08.418
can also be consistent because the two modes have separate requirements and

00:02:08.418 --> 00:02:08.750
states.

00:02:09.250 --> 00:02:13.140
For your checkpoint, describe the path as access, add or configure, review

00:02:13.140 --> 00:02:17.030
settings, then enable and verify. Do not compress it into subscribe and

00:02:17.030 --> 00:02:20.920
trade. In the next page, we will inspect the mode, account, and

00:02:20.920 --> 00:02:24.811
resource settings before changing the enabled state. That ordering gives you a

00:02:24.811 --> 00:02:28.701
chance to understand the limits before the strategy is allowed to use

00:02:28.701 --> 00:02:29.025
them.