For our final exercise, let's say you work in a company that typically works from 8:00 A.M. to 5:00 P.M. on the week days and that there's no one working on the weekends. This makes the weekend a very interesting time window for maintenance, and also for cutting costs on power consumption.

We're going to take this opportunity to archive logs and power down workstations on Friday at 11:30 P.M.

The idea of this exercise is for you to take it as a baseline for your own development and experience the nesting of Runbooks.

There's a lot you can then engage into this Runbook, such as updates maintenance, backups of important stuff, and so on. However, all this will really depend on your environment.

For now, let's focus on our Runbook; this is how it will look in the end:

You'll certainly recognize the second path of this Runbook, which is followed if the Checking Computer Status activity throws an error, gets logged, and ends in the Junction activity. This path...