WEBVTT
00:00:00.000 --> 00:00:02.310
>> Hi, my name is Eray.
00:00:02.310 --> 00:00:05.250
I'm a Program Manager working
on Microsoft Planner.
00:00:05.250 --> 00:00:06.810
I'm excited to tell you all about
00:00:06.810 --> 00:00:07.980
the Planner APIs that we've
00:00:07.980 --> 00:00:10.485
exposed on the Microsoft Graph.
00:00:10.485 --> 00:00:12.500
Today, we're going to go and
00:00:12.500 --> 00:00:13.640
do a little bit of an overview
00:00:13.640 --> 00:00:16.430
on Planner and then
talk about the APIs.
00:00:16.430 --> 00:00:17.720
I'm also going to cover some of
00:00:17.720 --> 00:00:19.155
the recent API updates we've
00:00:19.155 --> 00:00:22.040
made in the past couple
of months, and then from there,
00:00:22.040 --> 00:00:23.030
I'd spent a bunch of time
00:00:23.030 --> 00:00:24.440
demoing just to
give you a sense of
00:00:24.440 --> 00:00:29.370
how the API works and walk
through some simple examples.
00:00:30.410 --> 00:00:33.825
For those of you who are not
that familiar with Planner,
00:00:33.825 --> 00:00:36.810
Planner is a collaborative
task management tool
00:00:36.810 --> 00:00:39.365
that's included as
part of Office 365.
00:00:39.365 --> 00:00:41.370
Any time that you're
working with a team of
00:00:41.370 --> 00:00:43.680
people and want to
go and track work,
00:00:43.680 --> 00:00:45.045
know who's doing what,
00:00:45.045 --> 00:00:46.230
what needs to get done,
00:00:46.230 --> 00:00:47.310
and are we on track,
00:00:47.310 --> 00:00:50.970
Planner is a great tool
for you to go and use.
00:00:50.970 --> 00:00:53.445
Whenever you use Planner,
you create a plan,
00:00:53.445 --> 00:00:56.040
and within that plan, you
have a collection of tasks.
00:00:56.040 --> 00:00:58.320
We provide a couple of
different visualizations
00:00:58.320 --> 00:00:59.520
for each of these tasks.
00:00:59.520 --> 00:01:01.260
We have a task
board where you can
00:01:01.260 --> 00:01:03.945
see all of the tasks
organized by buckets.
00:01:03.945 --> 00:01:06.345
We also provide
some out-of-the-box charts
00:01:06.345 --> 00:01:08.805
as well as a schedule view.
00:01:08.805 --> 00:01:11.040
One of the recent
changes that we've
00:01:11.040 --> 00:01:13.320
made with Planner
during the past year
00:01:13.320 --> 00:01:17.595
is doing deeper integration
across Office 365.
00:01:17.595 --> 00:01:19.560
And so, any time
that you're thinking
00:01:19.560 --> 00:01:21.905
about a collaboration experience,
00:01:21.905 --> 00:01:23.415
Planner should be there for you.
00:01:23.415 --> 00:01:25.490
So in addition to
the Planner clients,
00:01:25.490 --> 00:01:27.010
we have now integrated
Planner into
00:01:27.010 --> 00:01:30.305
Microsoft Teams as
well as to SharePoint.
00:01:30.305 --> 00:01:32.450
Now, let's go and
step into some of
00:01:32.450 --> 00:01:34.550
the core concepts of Planner.
00:01:34.550 --> 00:01:40.340
So as I noted in
the previous slide,
00:01:40.340 --> 00:01:45.720
Planner has built off of
the Group Service in Office 365.
00:01:45.800 --> 00:01:48.600
What Groups are is
that Groups go and
00:01:48.600 --> 00:01:51.610
define a named
collection of members.
00:01:51.950 --> 00:01:56.550
Each Group owns
a collection of plans,
00:01:56.550 --> 00:01:58.980
and then within
the plans themselves,
00:01:58.980 --> 00:02:01.980
you also have buckets
as well as the tasks.
00:02:01.980 --> 00:02:03.900
I'll go and walk
00:02:03.900 --> 00:02:06.090
through all of these
during the API later.
00:02:06.090 --> 00:02:09.525
That's kind of the basic
concepts of all Planner is.
00:02:09.525 --> 00:02:11.770
When you'd go and drill
into any of the tasks,
00:02:11.770 --> 00:02:15.070
you also have the notion
of task details.
00:02:15.070 --> 00:02:16.470
This is where we store additional
00:02:16.470 --> 00:02:18.330
metadata about the task.
00:02:18.330 --> 00:02:19.620
So you can have things like
00:02:19.620 --> 00:02:22.570
a description as
well as checklists.
00:02:22.930 --> 00:02:25.850
Next is that you also have
the ability to attach
00:02:25.850 --> 00:02:27.980
files and attach links to a task.
00:02:27.980 --> 00:02:29.390
This is also associated on
00:02:29.390 --> 00:02:32.090
task details and then
finally having comments
00:02:32.090 --> 00:02:34.310
and conversations on a
task and these are all
00:02:34.310 --> 00:02:36.980
powered by Outlook
Group Conversations.
00:02:36.980 --> 00:02:39.290
The cool thing about all
of these things is that
00:02:39.290 --> 00:02:41.270
Planner itself is
also built using
00:02:41.270 --> 00:02:43.190
the Microsoft Graph
and we go and call
00:02:43.190 --> 00:02:44.570
the very same API that you
00:02:44.570 --> 00:02:47.905
call to go and power
these experiences.
00:02:47.905 --> 00:02:50.950
And if you're not that familiar
with the Microsoft Graph,
00:02:50.950 --> 00:02:52.690
I'm glad that you're here
watching this video.
00:02:52.690 --> 00:02:54.565
So, the Microsoft Graph
00:02:54.565 --> 00:02:57.010
is the unified REST
API that we use to
00:02:57.010 --> 00:02:58.920
access all of the data
that's stored within
00:02:58.920 --> 00:03:01.880
Office 365 as well as
its other services.
00:03:01.880 --> 00:03:04.180
As I noted, Planner itself uses
00:03:04.180 --> 00:03:07.165
a lot of the Graph APIs
to build its experiences.
00:03:07.165 --> 00:03:08.590
You can see on this slide that
00:03:08.590 --> 00:03:10.030
any of the items
that are highlighted
00:03:10.030 --> 00:03:12.845
green are actual APIs
that Planner uses.
00:03:12.845 --> 00:03:15.810
In addition to the other
services we integrate with,
00:03:15.810 --> 00:03:17.170
we also expose all of
00:03:17.170 --> 00:03:19.855
the Planner data via
the Graph itself,
00:03:19.855 --> 00:03:22.240
and so you could actually
go and build an app as rich
00:03:22.240 --> 00:03:25.145
as Planner using
just the Graph APIs, too.
00:03:25.145 --> 00:03:26.860
Some of the key APIs that we've
00:03:26.860 --> 00:03:28.690
exposed related to
Planner are around
00:03:28.690 --> 00:03:32.440
the tasks and plans that
Planner stores and its service.
00:03:32.440 --> 00:03:34.810
Some of the key things are
just getting all of the tasks
00:03:34.810 --> 00:03:37.030
that belong to me as a user,
00:03:37.030 --> 00:03:39.325
getting all the tasks
in a particular plan,
00:03:39.325 --> 00:03:40.930
and of course, seeing
all the plans that are
00:03:40.930 --> 00:03:43.670
associated with
a particular group.
00:03:44.780 --> 00:03:48.000
A couple of the main
API updates that we've
00:03:48.000 --> 00:03:51.180
made since exposing plans across
00:03:51.180 --> 00:03:52.545
a lot of these
different contexts and
00:03:52.545 --> 00:03:53.640
these different collaboration
00:03:53.640 --> 00:03:55.845
experiences wanted to provide
00:03:55.845 --> 00:03:58.170
additional capabilities
to help make it easier
00:03:58.170 --> 00:04:01.230
for you and users to
manage the plans.
00:04:01.230 --> 00:04:02.760
Some of the new APIs that we've
00:04:02.760 --> 00:04:04.770
recently released onto
the beta endpoint
00:04:04.770 --> 00:04:06.350
from Microsoft Graph include
00:04:06.350 --> 00:04:08.395
Favorite Plans and Recent Plans.
00:04:08.395 --> 00:04:10.590
So now, you have
the ability to specify
00:04:10.590 --> 00:04:12.330
specific plans that you want to
00:04:12.330 --> 00:04:14.535
favorite and see that in your UI.
00:04:14.535 --> 00:04:17.055
This is a slight change
from the past where
00:04:17.055 --> 00:04:21.640
you were leveraging
favorite groups as that proxy.
00:04:21.820 --> 00:04:24.255
In addition to Favorite Plans,
00:04:24.255 --> 00:04:26.950
now that with the plans
show up in different spots,
00:04:26.950 --> 00:04:28.270
we also expose the notion of
00:04:28.270 --> 00:04:31.270
a planned context on
plan details and this gives you
00:04:31.270 --> 00:04:31.810
a little bit of
00:04:31.810 --> 00:04:33.490
additional information
of where that plan's
00:04:33.490 --> 00:04:36.890
being used or where
that plan is being created.
00:04:37.400 --> 00:04:41.220
And with that, let me go
and show you on a demo.
00:04:41.220 --> 00:04:42.825
We'll start the demo from
00:04:42.825 --> 00:04:44.790
the Planner web
browser experience.
00:04:44.790 --> 00:04:47.040
So what you're seeing
here is the Planner hub,
00:04:47.040 --> 00:04:49.830
and you can see all of the
Favorite Plans that I have as
00:04:49.830 --> 00:04:52.890
well as my Recent Plans and
a list of all the plans.
00:04:52.890 --> 00:04:55.665
Whenever I click into
any of these plans,
00:04:55.665 --> 00:04:57.150
you can go and see that I
00:04:57.150 --> 00:04:59.220
have my different buckets
like engineering,
00:04:59.220 --> 00:05:00.825
manufacturing, and so on,
00:05:00.825 --> 00:05:03.600
as well as each of the
task cards themselves.
00:05:03.600 --> 00:05:05.955
And then as before,
when I click through,
00:05:05.955 --> 00:05:07.830
I can go and see all the metadata
00:05:07.830 --> 00:05:09.940
associated with that given task.
00:05:09.940 --> 00:05:12.500
In addition to the board, charts,
00:05:12.500 --> 00:05:13.670
and schedules that I mention,
00:05:13.670 --> 00:05:16.080
we also have another view
called My Tasks.
00:05:16.080 --> 00:05:18.390
My Tasks shows you all of
the tasks that are assigned
00:05:18.390 --> 00:05:21.150
to you across all of
your different plans.
00:05:21.150 --> 00:05:22.890
Let me show you what
that looks like
00:05:22.890 --> 00:05:24.405
within the Graph API.
00:05:24.405 --> 00:05:27.480
So, I'm going to hop over
to the Graph Explorer
00:05:27.480 --> 00:05:30.360
here and then the whole structure
00:05:30.360 --> 00:05:31.790
for Planner's pretty
straightforward.
00:05:31.790 --> 00:05:33.930
In order to go and
see any of the tasks
00:05:33.930 --> 00:05:36.120
that are assigned to me,
I can just go and say,
00:05:36.120 --> 00:05:39.970
"me/planner/tasks" and hit "Run"
00:05:39.970 --> 00:05:42.030
and that shows me all
of the same tasks
00:05:42.030 --> 00:05:43.980
that are currently
assigned to me below.
00:05:43.980 --> 00:05:45.660
If I want to see the tasks
00:05:45.660 --> 00:05:47.490
that belong to a specific plan,
00:05:47.490 --> 00:05:49.605
I can do that pretty
easily as well.
00:05:49.605 --> 00:05:51.795
Just from Planner,
I'll go and grab
00:05:51.795 --> 00:06:00.910
the plan ID and then if
I go back over here,
00:06:06.040 --> 00:06:08.975
I can go and see all of the tasks
00:06:08.975 --> 00:06:10.650
for that particular plan,
00:06:10.650 --> 00:06:14.940
and I can also do things
like see all the buckets.
00:06:16.850 --> 00:06:19.080
And then as I noted before,
00:06:19.080 --> 00:06:21.250
one of the newer
features that we have is
00:06:21.250 --> 00:06:25.755
adding more details and
context to each of the plans.
00:06:25.755 --> 00:06:29.100
And so, this particular plan
is actually also
00:06:29.100 --> 00:06:30.510
used within the context of
00:06:30.510 --> 00:06:32.460
SharePoint as well as in Teams.
00:06:32.460 --> 00:06:35.565
And so, when I go and look
at the details of it,
00:06:35.565 --> 00:06:37.365
off of the beta endpoint,
00:06:37.365 --> 00:06:38.280
you'll see some of
00:06:38.280 --> 00:06:40.840
the additional information
associated there.
00:06:40.840 --> 00:06:43.485
And so, if you look down here,
00:06:43.485 --> 00:06:45.345
you can actually see that it has
00:06:45.345 --> 00:06:47.565
the notion of contact details,
00:06:47.565 --> 00:06:49.020
and so, it can say that here,
00:06:49.020 --> 00:06:54.100
this is one that we created
from the Teams context,
00:06:54.100 --> 00:06:55.590
and here's another one
that we created
00:06:55.590 --> 00:06:57.080
from the SharePoint context.
00:06:57.080 --> 00:06:58.380
And in each of these cases,
00:06:58.380 --> 00:07:00.780
we also store a URL
that gives you access
00:07:00.780 --> 00:07:04.760
to that particular plan
within that context.
00:07:04.760 --> 00:07:06.120
And so, for example,
00:07:06.120 --> 00:07:08.399
if I wanted to open
this in Teams,
00:07:08.399 --> 00:07:10.680
you can just go and
access that URL and the
00:07:10.680 --> 00:07:13.080
same with the URL that
you have for SharePoint.
00:07:13.080 --> 00:07:16.370
Next, I'm going to go and show
00:07:16.370 --> 00:07:20.390
you actually going and
creating a plan from scratch.
00:07:20.390 --> 00:07:22.450
There's a couple of steps
involved in doing this.
00:07:22.450 --> 00:07:24.625
And so, let me go and walk
through each of these.
00:07:24.625 --> 00:07:28.340
As I noted in
the presentation before,
00:07:28.340 --> 00:07:30.345
every plan today is
owned by a group.
00:07:30.345 --> 00:07:32.000
And so, the first step
that you need to do is
00:07:32.000 --> 00:07:34.370
to actually go and
create that group.
00:07:34.370 --> 00:07:36.380
In order to create a group,
00:07:36.380 --> 00:07:39.680
all you have to do is post
to the groups endpoint.
00:07:39.680 --> 00:07:41.320
There are some basic metadata
00:07:41.320 --> 00:07:42.490
that you need to fill out about
00:07:42.490 --> 00:07:43.540
a group and I've kind of copied
00:07:43.540 --> 00:07:45.455
over some of it here already,
00:07:45.455 --> 00:07:47.140
and you can see that you can name
00:07:47.140 --> 00:07:48.400
the group whatever you want,
00:07:48.400 --> 00:07:50.905
so I'll just name it API Group,
00:07:50.905 --> 00:07:53.230
and then you can specify a couple
00:07:53.230 --> 00:07:55.465
of other things like
the mail nickname and so on.
00:07:55.465 --> 00:07:57.010
When I go and run this query,
00:07:57.010 --> 00:07:58.630
that'll go and create the group.
00:07:58.630 --> 00:08:02.460
So let me do that. Okay, great.
00:08:02.460 --> 00:08:04.755
And so, now that I
have my group below,
00:08:04.755 --> 00:08:07.105
I'm going to grab
the ID for that group
00:08:07.105 --> 00:08:08.140
because I'm going to use it for
00:08:08.140 --> 00:08:10.700
a couple of the remaining steps.
00:08:12.080 --> 00:08:14.260
After I've created the group,
00:08:14.260 --> 00:08:15.595
it's important to go and add
00:08:15.595 --> 00:08:18.655
the current user to be a member
of that group as well.
00:08:18.655 --> 00:08:20.965
So by default, whenever
you create a group,
00:08:20.965 --> 00:08:22.030
the person who created it, is
00:08:22.030 --> 00:08:23.465
added as an owner of that group.
00:08:23.465 --> 00:08:25.130
But we also want to make
sure that they're a member,
00:08:25.130 --> 00:08:26.260
so they can participate in
00:08:26.260 --> 00:08:27.670
the actual collaboration there.
00:08:27.670 --> 00:08:30.460
In order to add
a member to a group,
00:08:30.460 --> 00:08:34.235
you post to that navigation.
00:08:34.235 --> 00:08:37.415
And then in this case, I'm
going to add the current user.
00:08:37.415 --> 00:08:38.590
And so, I happened to copy
00:08:38.590 --> 00:08:41.650
over the current users
ID previously,
00:08:41.650 --> 00:08:43.690
but you could always use
the samples here just
00:08:43.690 --> 00:08:46.430
get that user's ID
and add that in.
00:08:46.430 --> 00:08:49.670
So when I go and run that query,
00:08:50.540 --> 00:08:53.290
now, I've succeeded
and I've added
00:08:53.290 --> 00:08:55.790
that user to the group.
00:08:55.790 --> 00:08:58.780
To check that everything
worked out correctly,
00:08:58.780 --> 00:09:00.400
you can always go and do quick
00:09:00.400 --> 00:09:05.715
read on that same group and
look at the members list.
00:09:05.715 --> 00:09:06.870
And if it all went well,
00:09:06.870 --> 00:09:09.090
I should see myself in that list.
00:09:09.090 --> 00:09:10.560
And so, correct, I see
00:09:10.560 --> 00:09:14.330
Alex Wilbur is now a member
of that same group.
00:09:14.420 --> 00:09:16.800
Next, I'm going to
go and show creating
00:09:16.800 --> 00:09:19.490
a plan for that given group.
00:09:22.870 --> 00:09:25.130
In order to create a plan,
00:09:25.130 --> 00:09:26.855
you need to just specify a title
00:09:26.855 --> 00:09:28.895
and then the group
that it's owned by.
00:09:28.895 --> 00:09:31.370
This is a common question
that people have,
00:09:31.370 --> 00:09:33.235
is that when they
see the owner field,
00:09:33.235 --> 00:09:34.660
they think that, "This should be
00:09:34.660 --> 00:09:36.300
the owner like a user for it."
00:09:36.300 --> 00:09:37.430
But in this particular case,
00:09:37.430 --> 00:09:39.470
because we're talking
at the API level,
00:09:39.470 --> 00:09:42.320
this is the owner from
a group perspective,
00:09:42.320 --> 00:09:44.725
and so it's the group that's
containing that plan.
00:09:44.725 --> 00:09:47.240
And so, what I'm going
to do here is copy
00:09:47.240 --> 00:09:50.750
over the ideas specified before,
00:09:50.750 --> 00:09:55.425
and then I'm going to have
a plan called "API Demo Plan",
00:09:55.425 --> 00:09:58.710
and then I'm going to run-
make sure this is the post.
00:09:58.710 --> 00:10:02.380
And I'm going to go and
create that now as well.
00:10:05.450 --> 00:10:08.750
Okay. And now that
I've completed that,
00:10:08.750 --> 00:10:10.250
you can see that it does say
00:10:10.250 --> 00:10:13.770
success and I have a plan
ID that I can use.
00:10:14.420 --> 00:10:17.020
The next thing I'm going to
00:10:17.020 --> 00:10:18.910
show is actually adding
that plan to "My
00:10:18.910 --> 00:10:23.780
Favorites" collection for
easier access going forward.
00:10:23.880 --> 00:10:27.890
So let me go and copy that over.
00:10:27.890 --> 00:10:32.530
So, the first thing I want to do
00:10:32.530 --> 00:10:34.115
is actually look at all of
00:10:34.115 --> 00:10:36.820
the favorites that I have so far.
00:10:36.820 --> 00:10:42.005
And so, if you go to
Beta/me/planner/favoritePlans,
00:10:42.005 --> 00:10:43.555
you could see all
of the favorites
00:10:43.555 --> 00:10:46.220
that I currently
have for this user.
00:10:48.200 --> 00:10:50.945
This basically maps to
that same call that
00:10:50.945 --> 00:10:53.850
you saw on the hub previously.
00:10:55.680 --> 00:11:00.065
You can also look at
all of these both the
00:11:00.065 --> 00:11:02.140
"Favorites" and
"Recent"in one call by
00:11:02.140 --> 00:11:04.285
just removing that last segment.
00:11:04.285 --> 00:11:05.500
So if I go like this,
00:11:05.500 --> 00:11:08.530
you could see kind of
an abbreviated version of "My
00:11:08.530 --> 00:11:12.540
Favorites" as well as
my "Recent Plans".
00:11:12.540 --> 00:11:14.200
This is actually useful if
00:11:14.200 --> 00:11:16.000
you want to go and
render just the list of
00:11:16.000 --> 00:11:18.370
plans in one quick call
00:11:18.370 --> 00:11:20.345
without a lot of
the extra amount of data.
00:11:20.345 --> 00:11:24.130
Okay. So, in order to go
and add something to this,
00:11:24.130 --> 00:11:27.220
what I'm going to do is
do a "Patch" and let me
00:11:27.220 --> 00:11:31.400
grab the stuff I
want to patch here.
00:11:32.300 --> 00:11:38.610
And then I'm also going to
add the request header for-.
00:11:41.320 --> 00:11:44.820
So, I need to grab the "ETag".
00:11:46.160 --> 00:11:48.710
Then, I'll grab the
00:11:48.710 --> 00:11:52.320
"ETag" just to make sure
I have the most recent.
00:11:54.070 --> 00:11:57.080
Okay. Then going back
to the "Request".
00:11:57.080 --> 00:11:59.340
I need to go and actually take
00:11:59.340 --> 00:12:03.570
the plan ID and add
that to "My Favorites".
00:12:03.570 --> 00:12:05.150
So this is the plan
ID from the plan I
00:12:05.150 --> 00:12:07.920
had in the previous step.
00:12:09.470 --> 00:12:12.450
And then, I'm going to
have an "Order Head",
00:12:12.450 --> 00:12:15.305
this is specifying that it
should be the last one there.
00:12:15.305 --> 00:12:16.820
And then finally, I'm going
00:12:16.820 --> 00:12:18.500
to have the "Plan Title" here.
00:12:18.500 --> 00:12:20.420
And so, one thing
that you'll notice is
00:12:20.420 --> 00:12:22.700
that while you
specify a plan title,
00:12:22.700 --> 00:12:24.350
when you go set the
00:12:24.350 --> 00:12:26.810
"Favorites" the plan or
clients will always go and
00:12:26.810 --> 00:12:28.820
fix this up whenever
you navigate to
00:12:28.820 --> 00:12:29.930
those plans to make sure
00:12:29.930 --> 00:12:31.465
that the plan titles
are up to date.
00:12:31.465 --> 00:12:32.810
And so in this case,
00:12:32.810 --> 00:12:35.190
I do have the API demo plan,
00:12:35.190 --> 00:12:38.760
and let me just go and run that.
00:12:39.350 --> 00:12:41.910
Okay. So that succeeded.
00:12:41.910 --> 00:12:46.710
So now, when I go back to
the planner side of things,
00:12:46.710 --> 00:12:49.370
do click "Refresh" because
it might take a second.
00:12:49.370 --> 00:12:52.000
I can see that that new
API demo plan that I
00:12:52.000 --> 00:12:55.815
created is now included in
my "Favorites" as well.
00:12:55.815 --> 00:12:58.450
Next, I can show a little bit
of how to go and
00:12:58.450 --> 00:13:01.285
add "Buckets" and "Tasks"
to that same plan.
00:13:01.285 --> 00:13:03.340
So I start back over here,
00:13:03.340 --> 00:13:05.500
and then grab the plan ID,
00:13:05.500 --> 00:13:08.160
and then I'm going to
00:13:08.160 --> 00:13:11.535
now start posting to
create the buckets.
00:13:11.535 --> 00:13:14.350
So, creating buckets is pretty
straightforward as well.
00:13:14.350 --> 00:13:16.750
Let me switch back to "V1".
00:13:19.580 --> 00:13:26.895
Sorry.
00:13:26.895 --> 00:13:30.235
Okay. So if I want to go
and create "Buckets" now,
00:13:30.235 --> 00:13:33.020
all they do is specify
for each "Bucket",
00:13:33.020 --> 00:13:38.270
what the order is and then
the plan that belongs to,
00:13:38.270 --> 00:13:41.310
as well as the name
of the bucket itself.
00:13:41.310 --> 00:13:42.950
And so, I'm going to do
that a couple of times.
00:13:42.950 --> 00:13:47.220
So grabbing that plant idea
again, click over here.
00:13:48.580 --> 00:13:50.870
So, that's "Bucket One".
00:13:50.870 --> 00:13:55.650
Let me run this. I'm going
to do this two more times,
00:13:55.650 --> 00:14:01.680
"Bucket Two" and
then "bucket Three".
00:14:01.680 --> 00:14:02.970
Okay.
00:14:02.970 --> 00:14:05.885
And I'm going to now
grab the bucket ID
00:14:05.885 --> 00:14:07.010
for that last bucket,
00:14:07.010 --> 00:14:10.350
and we can put a couple
of tasks into it too.
00:14:13.160 --> 00:14:15.840
Okay. So, if I click over
00:14:15.840 --> 00:14:17.805
here I should see
my three buckets.
00:14:17.805 --> 00:14:19.230
Great. And so now,
00:14:19.230 --> 00:14:21.710
I'm going to go out some
task it that last bucket.
00:14:21.710 --> 00:14:23.715
So the add tasks,
00:14:23.715 --> 00:14:26.505
you just post to planner/tasks.
00:14:26.505 --> 00:14:36.520
And then in this case, you have
00:14:36.520 --> 00:14:37.710
to specify the title,
00:14:37.710 --> 00:14:39.890
the plan, the bucket
of that task,
00:14:39.890 --> 00:14:41.360
and you can also
assign it to people
00:14:41.360 --> 00:14:42.950
if you want to as well.
00:14:42.950 --> 00:14:44.570
And so for example, if
I wanted that assign it
00:14:44.570 --> 00:14:46.970
to the user early on,
00:14:46.970 --> 00:14:48.455
you can go and do that too.
00:14:48.455 --> 00:14:51.180
I'm just actually just
remove that for now.
00:14:51.440 --> 00:14:55.160
And then go and update all
of these to the right info.
00:14:55.160 --> 00:14:57.270
So, I grabbed my plan ID
from earlier.
00:14:57.270 --> 00:15:03.740
Now, I'm going to
grab my bucket ID.
00:15:06.770 --> 00:15:10.950
Then task from API
one, run the query,
00:15:10.950 --> 00:15:19.200
do that one or two more
times and then three.
00:15:19.200 --> 00:15:20.910
Okay. And so now,
if I hop back to
00:15:20.910 --> 00:15:22.740
"Planner", it might
take a second,
00:15:22.740 --> 00:15:24.700
but you should be able
to see that I don't have
00:15:24.700 --> 00:15:27.190
three tasks pumping
and then "Refresh".
00:15:27.190 --> 00:15:30.935
And I have my three tasks
from the API there as well.
00:15:30.935 --> 00:15:34.440
And now you can go and start
planning as you see "Fit".
00:15:34.500 --> 00:15:36.970
That was just a
really quick overview
00:15:36.970 --> 00:15:38.790
of what you can do with the API.
00:15:38.790 --> 00:15:40.270
You know, one of
the common things that we
00:15:40.270 --> 00:15:41.890
see a lot is that if you want to
00:15:41.890 --> 00:15:44.830
go and set up a plan to
match your structure,
00:15:44.830 --> 00:15:46.540
a lot of folks have
been using the API
00:15:46.540 --> 00:15:48.370
to go and specify a set of
00:15:48.370 --> 00:15:50.230
tasks on a set of buckets to
00:15:50.230 --> 00:15:52.645
use to go and create
new plans with.
00:15:52.645 --> 00:15:56.020
Other common scenarios
people also used is to try
00:15:56.020 --> 00:15:58.959
to go and create task from
other systems within planner,
00:15:58.959 --> 00:16:00.310
and then you can easily go and
00:16:00.310 --> 00:16:02.590
collaborate them within
the planner experiences
00:16:02.590 --> 00:16:06.570
as well as our experiences
within teams and SharePoint.
00:16:06.570 --> 00:16:08.410
Well, thanks for
taking the time to
00:16:08.410 --> 00:16:10.930
hear a little bit about
planner API today.
00:16:10.930 --> 00:16:13.390
Hope you liked what you
saw and want to go and
00:16:13.390 --> 00:16:17.110
start trying out the
API. Happy planning.