60. Automated educational presentations
Module 12 · 20 minutes · Lesson 59; earlier service and JavaScript fundamentals
Open Interactive LessonDiscover
How can you use automated educational presentations without changing the wrong data?
- Explain automated educational presentations in your own words
- Trace the actual presentations state change from the source
- Repair the supplied failing operation and verify the result
Predict
Which values or resources will change, and which should stay unchanged? Write your prediction before execution.
Understand
Design generated slides around a teaching sequence, not a pile of raw records. Each slide needs a purpose and an actionable prompt. Separate content arrays from rendering logic so an educator can review the lesson before generation. Keep generated slides editable and check readability in Google Slides before sharing.
Example 1: Working automation
The sequence labels steps one through three and makes the learning actions explicit.
function main() {
const deck = SlidesApp.create("Automation mini-lesson");
const topics = ["Predict the result", "Run the code", "Explain the changed cell"];
topics.forEach((topic, index) => {
const slide = index === 0 ? deck.getSlides()[0] : deck.appendSlide();
slide.insertTextBox((index + 1) + ". " + topic);
});
}Important line explanations
- Line 1: function main() {
- Define a named block of instructions. Run Script calls main; helpers run only when called.
- Line 2: const deck = SlidesApp.create("Automation mini-lesson");
- Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
- Line 3: const topics = ["Predict the result", "Run the code", "Explain the changed cell"];
- Initialize a local binding. const prevents reassignment of that binding, but does not freeze a referenced object.
- Line 4: topics.forEach((topic, index) => {
- Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
- Line 5: const slide = index === 0 ? deck.getSlides()[0] : deck.appendSlide();
- Initialize a local binding. const prevents reassignment of that binding, but does not freeze a referenced object.
- Line 6: slide.insertTextBox((index + 1) + ". " + topic);
- Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
- Line 7: });
- Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
- Line 8: }
- Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
"logs": [],
"error": null,
"resource": "presentations",
"value": {
"slides-1": {
"name": "Automation mini-lesson",
"slides": [
{
"elements": [
{
"text": "1. Predict the result",
"left": 20,
"top": 20,
"width": 500,
"height": 80
}
]
},
{
"elements": [
{
"text": "2. Run the code",
"left": 20,
"top": 20,
"width": 500,
"height": 80
}
]
},
{
"elements": [
{
"text": "3. Explain the changed cell",
"left": 20,
"top": 20,
"width": 500,
"height": 80
}
]
}
]
}
}
}Example 2: Investigate a reproducible failure
Predict the effect of index - 1 and identify the first mismatch. This example is intentionally faulty.
function main() {
const deck = SlidesApp.create("Automation mini-lesson");
const topics = ["Predict the result", "Run the code", "Explain the changed cell"];
topics.forEach((topic, index) => {
const slide = index === 0 ? deck.getSlides()[0] : deck.appendSlide();
slide.insertTextBox((index - 1) + ". " + topic);
});
}Important line explanations
- Line 1: function main() {
- Define a named block of instructions. Run Script calls main; helpers run only when called.
- Line 2: const deck = SlidesApp.create("Automation mini-lesson");
- Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
- Line 3: const topics = ["Predict the result", "Run the code", "Explain the changed cell"];
- Initialize a local binding. const prevents reassignment of that binding, but does not freeze a referenced object.
- Line 4: topics.forEach((topic, index) => {
- Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
- Line 5: const slide = index === 0 ? deck.getSlides()[0] : deck.appendSlide();
- Initialize a local binding. const prevents reassignment of that binding, but does not freeze a referenced object.
- Line 6: slide.insertTextBox((index - 1) + ". " + topic);
- Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
- Line 7: });
- Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
- Line 8: }
- Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
"logs": [],
"error": null,
"resource": "presentations",
"value": {
"slides-1": {
"name": "Automation mini-lesson",
"slides": [
{
"elements": [
{
"text": "-1. Predict the result",
"left": 20,
"top": 20,
"width": 500,
"height": 80
}
]
},
{
"elements": [
{
"text": "0. Run the code",
"left": 20,
"top": 20,
"width": 500,
"height": 80
}
]
},
{
"elements": [
{
"text": "1. Explain the changed cell",
"left": 20,
"top": 20,
"width": 500,
"height": 80
}
]
}
]
}
}
}Example 3: Separate setup from execution and inspect repeat behavior
Call the same named operation twice. Compare outputs and resource counts to learn whether this operation is idempotent. Repeated creation is deliberately visible; real exports require a rerun policy.
function lessonAction() {
const deck = SlidesApp.create("Automation mini-lesson");
const topics = ["Predict the result", "Run the code", "Explain the changed cell"];
topics.forEach((topic, index) => {
const slide = index === 0 ? deck.getSlides()[0] : deck.appendSlide();
slide.insertTextBox((index + 1) + ". " + topic);
});
}
function main() {
lessonAction();
lessonAction();
}Important line explanations
- Line 1: function lessonAction() {
- Define a named block of instructions. Run Script calls main; helpers run only when called.
- Line 2: const deck = SlidesApp.create("Automation mini-lesson");
- Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
- Line 3: const topics = ["Predict the result", "Run the code", "Explain the changed cell"];
- Initialize a local binding. const prevents reassignment of that binding, but does not freeze a referenced object.
- Line 4: topics.forEach((topic, index) => {
- Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
- Line 5: const slide = index === 0 ? deck.getSlides()[0] : deck.appendSlide();
- Initialize a local binding. const prevents reassignment of that binding, but does not freeze a referenced object.
- Line 6: slide.insertTextBox((index + 1) + ". " + topic);
- Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
- Line 7: });
- Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
- Line 8: }
- Close the current block. Indentation makes scope and the function boundary visible.
- Line 9: function main() {
- Define a named block of instructions. Run Script calls main; helpers run only when called.
- Line 10: lessonAction();
- Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
- Line 11: lessonAction();
- Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
- Line 12: }
- Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
"logs": [],
"error": null,
"resource": "presentations",
"value": {
"slides-1": {
"name": "Automation mini-lesson",
"slides": [
{
"elements": [
{
"text": "1. Predict the result",
"left": 20,
"top": 20,
"width": 500,
"height": 80
}
]
},
{
"elements": [
{
"text": "2. Run the code",
"left": 20,
"top": 20,
"width": 500,
"height": 80
}
]
},
{
"elements": [
{
"text": "3. Explain the changed cell",
"left": 20,
"top": 20,
"width": 500,
"height": 80
}
]
}
]
},
"slides-2": {
"name": "Automation mini-lesson",
"slides": [
{
"elements": [
{
"text": "1. Predict the result",
"left": 20,
"top": 20,
"width": 500,
"height": 80
}
]
},
{
"elements": [
{
"text": "2. Run the code",
"left": 20,
"top": 20,
"width": 500,
"height": 80
}
]
},
{
"elements": [
{
"text": "3. Explain the changed cell",
"left": 20,
"top": 20,
"width": 500,
"height": 80
}
]
}
]
}
}
}Example 4: Add a diagnostic boundary around the operation
Observe start, successful completion or a rethrown failure. This optional professional pattern adds error context without swallowing the error or rolling back changes.
function lessonAction() {
const deck = SlidesApp.create("Automation mini-lesson");
const topics = ["Predict the result", "Run the code", "Explain the changed cell"];
topics.forEach((topic, index) => {
const slide = index === 0 ? deck.getSlides()[0] : deck.appendSlide();
slide.insertTextBox((index + 1) + ". " + topic);
});
}
function main() {
console.log("Start: Automated educational presentations");
try { lessonAction(); console.log("Completed operation"); }
catch(error) { console.error("Failed operation: " + error.message); throw error; }
}Important line explanations
- Line 1: function lessonAction() {
- Define a named block of instructions. Run Script calls main; helpers run only when called.
- Line 2: const deck = SlidesApp.create("Automation mini-lesson");
- Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
- Line 3: const topics = ["Predict the result", "Run the code", "Explain the changed cell"];
- Initialize a local binding. const prevents reassignment of that binding, but does not freeze a referenced object.
- Line 4: topics.forEach((topic, index) => {
- Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
- Line 5: const slide = index === 0 ? deck.getSlides()[0] : deck.appendSlide();
- Initialize a local binding. const prevents reassignment of that binding, but does not freeze a referenced object.
- Line 6: slide.insertTextBox((index + 1) + ". " + topic);
- Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
- Line 7: });
- Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
- Line 8: }
- Close the current block. Indentation makes scope and the function boundary visible.
- Line 9: function main() {
- Define a named block of instructions. Run Script calls main; helpers run only when called.
- Line 10: console.log("Start: Automated educational presentations");
- Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
- Line 11: try { lessonAction(); console.log("Completed operation"); }
- Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
- Line 12: catch(error) { console.error("Failed operation: " + error.message); throw error; }
- Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
- Line 13: }
- Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
"logs": [
"Start: Automated educational presentations",
"Completed operation"
],
"error": null,
"resource": "presentations",
"value": {
"slides-1": {
"name": "Automation mini-lesson",
"slides": [
{
"elements": [
{
"text": "1. Predict the result",
"left": 20,
"top": 20,
"width": 500,
"height": 80
}
]
},
{
"elements": [
{
"text": "2. Run the code",
"left": 20,
"top": 20,
"width": 500,
"height": 80
}
]
},
{
"elements": [
{
"text": "3. Explain the changed cell",
"left": 20,
"top": 20,
"width": 500,
"height": 80
}
]
}
]
}
}
}Build and test
Repair the supplied script so that: The sequence labels steps one through three and makes the learning actions explicit. Preserve other source data. Checks compare observable output and the named resource, not exact source text.
function main() {
const deck = SlidesApp.create("Automation mini-lesson");
const topics = ["Predict the result", "Run the code", "Explain the changed cell"];
topics.forEach((topic, index) => {
const slide = index === 0 ? deck.getSlides()[0] : deck.appendSlide();
slide.insertTextBox((index - 1) + ". " + topic);
});
}Graduated hints
Hint 1
Inspect the operation containing index - 1. Compare it with the stated rule and the first mismatch.
Hint 2
The repair concerns index + 1. Change only the relevant argument, operator or method; rerun with fresh input.
Hint 3
The reference uses index + 1 where the broken source uses index - 1. Explain why before applying it.
Reference solution
function main() {
const deck = SlidesApp.create("Automation mini-lesson");
const topics = ["Predict the result", "Run the code", "Explain the changed cell"];
topics.forEach((topic, index) => {
const slide = index === 0 ? deck.getSlides()[0] : deck.appendSlide();
slide.insertTextBox((index + 1) + ". " + topic);
});
}Explain and reflect
Which operation proves the intended result in automated educational presentations? Which wrong input would expose a weakness, and what would remain unchanged?
Adapt the input records and presentations output to a second realistic case. Write its expected result before running. Demonstrate one invalid case and explain whether the side effects should be rolled back or retried.
Troubleshooting
If the console is empty, inspect the presentations preview: this script may work through state changes. If the function is missing, select main. For a service error inspect the first failed timeline entry and its arguments. Use Manual unless investigating a trigger. Changing input data also changes the expected result; restore sample data before the authored checks.
Knowledge check
Explain the key method or operator. Give an exact output for a second input, plus one invalid case. Verify the result in the interactive lesson; written explanations need self or educator review.
Optional AI practice
Explain this concept using the source above. Help implement one small extension and define its tests. Review/debug the source using its actual expected output; cite real method references and never claim execution.