>> Hi, everyone, my name is Jehona.
I'm a Program Manager in Azure IoT,
focusing on Industrial IoT Scenarios.
Today, I will be showing how you can manage your devices at
scale using the jobs feature on IoT Central.
The jobs feature you can do bulk updates to device and
clock properties and run commands
without using a single line of code.
As an Operator managing facilities,
I would like to decrease the room temperature and set it
to 70 degrees Fahrenheit as always,
regulate the humidity in the rooms.
After connecting the devices, which you can see here,
I find the "Jobs" tab in the "Mange
Section" and I'm provided with three different views.
The first one is the "Last 30 Days" tabs.
What you see here are all jobs that ran in the past 30 days.
Under the "Schedule" tab,
you can find all jobs that were configured,
but they were said to start sometime in the near future,
like for example, next week.
The "Last" tab shows all jobs
that were configured but not finished.
I can go back and open it up to edit,
but it's not running yet.
To configure a job, I click on "New",
here in the upper left corner and provide all the information,
starting with the name and the description.
Description's optional,
I use it to provide some more information.
Next we choose an organization to associate the job to.
In this case I only have one option,
which is Contoso main campus I and move on to the device group.
Depending on how many organizations you have to choose from,
the device groups might change.
I choose the "Thermostat" and I can see that I have 1,116 devices.
The next one is the job properties.
We can choose between three job types.
That's Cloud Property,
Property, or Command.
Properties are a point in time value.
For example, the target temperature the device is trying to reach.
Cloud Property values are never exchanged for
the device and commands can be called on the device,
for example, to reboot it.
I select "Property" and set the wanted values.
I'll start for the temperature,
which is supposed to be 70.
You can set multiple properties by clicking "Add".
The other one that I have as an option is
the humidity and the value is 40.
I click "Next" and go to the "Delivery Option" page.
Batches register standard jobs for large numbers of devices.
We don't want to update all Thermostats at the same time,
so we select a specific amount of the devices and create a Batch.
This can be, for example,
10 percent of all devices.
If you have 1,000 devices,
100 will be updated.
You can also choose a number instead of a percentage.
I'll go with 10 percent and
then I enable the "Cancellation Threshold",
which means that you can automatically cancel
a job if the number of errors exceeds the set limit.
The Threshold can apply to other devices in
the job or to an individual Batch.
I again choose a percentage,
which is 15 per Batch.
That means if a job fails on 50 percent of the devices per Batch,
the job will be canceled.
Next, get to the "Schedule" page.
If I enable it, I can schedule the job to run in the near future,
like for example, tomorrow or the next week.
You can choose the "Recurrence" and the "Start" and "End Time".
But in this case, I want the job to start immediately,
so I disable it again.
Now, you're on the Review page
so you can make sure that all the information is
correct and then when clicking on "Run", the job starts.
Here you are provided with further information.
You can stop the job whenever you want
to and resume again when you're ready.
Here you can also see that 245 devices were updated,
zero have failed, and 742 are still pending.
This is constantly updating as the job runs.
That wraps it up. Thank you for watching this video,
I hope it was really useful.
If you would like to learn more,
here are some things to check out.