45. Human-reviewed communication workflows
Module 9 · 20 minutes · Lesson 44; earlier service and JavaScript fundamentals
Open Interactive LessonDiscover
How can you use human-reviewed communication workflows without changing the wrong data?
- Explain human-reviewed communication workflows in your own words
- Trace the actual drafts 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
Separate preparing a draft from permission to send it. Approval should include recipient, subject and content, and be tied to a specific version. A Boolean flag alone is not a complete identity or audit system. This sample prepares approved rows only; Google delivery remains a separate manual action.
Example 1: Working automation
Only the approved record produces a draft; the unapproved person receives no prepared message.
function main() {
const records = [{email: "alex@example.com", approved: true}, {email: "jordan@example.com", approved: false}];
records.filter(row => row.approved === true).forEach(row => GmailApp.createDraft(row.email, "Reviewed notice", "Ready for your review."));
}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 records = [{email: "alex@example.com", approved: true}, {email: "jordan@example.com", approved: false}];
- Initialize a local binding. const prevents reassignment of that binding, but does not freeze a referenced object.
- Line 3: records.filter(row => row.approved === true).forEach(row => GmailApp.createDraft(row.email, "Reviewed notice", "Ready for your review."));
- Create a new array containing only records that satisfy the predicate; this does not delete source rows.
- Line 4: }
- Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
"logs": [],
"error": null,
"resource": "drafts",
"value": [
{
"id": "draft-1",
"to": "alex@example.com",
"subject": "Reviewed notice",
"body": "Ready for your review.",
"htmlBody": ""
}
]
}Example 2: Investigate a reproducible failure
Predict the effect of row.approved === false and identify the first mismatch. This example is intentionally faulty.
function main() {
const records = [{email: "alex@example.com", approved: true}, {email: "jordan@example.com", approved: false}];
records.filter(row => row.approved === false).forEach(row => GmailApp.createDraft(row.email, "Reviewed notice", "Ready for your review."));
}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 records = [{email: "alex@example.com", approved: true}, {email: "jordan@example.com", approved: false}];
- Initialize a local binding. const prevents reassignment of that binding, but does not freeze a referenced object.
- Line 3: records.filter(row => row.approved === false).forEach(row => GmailApp.createDraft(row.email, "Reviewed notice", "Ready for your review."));
- Create a new array containing only records that satisfy the predicate; this does not delete source rows.
- Line 4: }
- Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
"logs": [],
"error": null,
"resource": "drafts",
"value": [
{
"id": "draft-1",
"to": "jordan@example.com",
"subject": "Reviewed notice",
"body": "Ready for your review.",
"htmlBody": ""
}
]
}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 records = [{email: "alex@example.com", approved: true}, {email: "jordan@example.com", approved: false}];
records.filter(row => row.approved === true).forEach(row => GmailApp.createDraft(row.email, "Reviewed notice", "Ready for your review."));
}
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 records = [{email: "alex@example.com", approved: true}, {email: "jordan@example.com", approved: false}];
- Initialize a local binding. const prevents reassignment of that binding, but does not freeze a referenced object.
- Line 3: records.filter(row => row.approved === true).forEach(row => GmailApp.createDraft(row.email, "Reviewed notice", "Ready for your review."));
- Create a new array containing only records that satisfy the predicate; this does not delete source rows.
- Line 4: }
- Close the current block. Indentation makes scope and the function boundary visible.
- Line 5: function main() {
- Define a named block of instructions. Run Script calls main; helpers run only when called.
- Line 6: lessonAction();
- Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
- Line 7: lessonAction();
- 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": "drafts",
"value": [
{
"id": "draft-1",
"to": "alex@example.com",
"subject": "Reviewed notice",
"body": "Ready for your review.",
"htmlBody": ""
},
{
"id": "draft-2",
"to": "alex@example.com",
"subject": "Reviewed notice",
"body": "Ready for your review.",
"htmlBody": ""
}
]
}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 records = [{email: "alex@example.com", approved: true}, {email: "jordan@example.com", approved: false}];
records.filter(row => row.approved === true).forEach(row => GmailApp.createDraft(row.email, "Reviewed notice", "Ready for your review."));
}
function main() {
console.log("Start: Human-reviewed communication workflows");
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 records = [{email: "alex@example.com", approved: true}, {email: "jordan@example.com", approved: false}];
- Initialize a local binding. const prevents reassignment of that binding, but does not freeze a referenced object.
- Line 3: records.filter(row => row.approved === true).forEach(row => GmailApp.createDraft(row.email, "Reviewed notice", "Ready for your review."));
- Create a new array containing only records that satisfy the predicate; this does not delete source rows.
- Line 4: }
- Close the current block. Indentation makes scope and the function boundary visible.
- Line 5: function main() {
- Define a named block of instructions. Run Script calls main; helpers run only when called.
- Line 6: console.log("Start: Human-reviewed communication workflows");
- Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
- Line 7: try { lessonAction(); console.log("Completed operation"); }
- Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
- Line 8: 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 9: }
- Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
"logs": [
"Start: Human-reviewed communication workflows",
"Completed operation"
],
"error": null,
"resource": "drafts",
"value": [
{
"id": "draft-1",
"to": "alex@example.com",
"subject": "Reviewed notice",
"body": "Ready for your review.",
"htmlBody": ""
}
]
}Build and test
Repair the supplied script so that: Only the approved record produces a draft; the unapproved person receives no prepared message. Preserve other source data. Checks compare observable output and the named resource, not exact source text.
function main() {
const records = [{email: "alex@example.com", approved: true}, {email: "jordan@example.com", approved: false}];
records.filter(row => row.approved === false).forEach(row => GmailApp.createDraft(row.email, "Reviewed notice", "Ready for your review."));
}Graduated hints
Hint 1
Inspect the operation containing row.approved === false. Compare it with the stated rule and the first mismatch.
Hint 2
The repair concerns row.approved === true. Change only the relevant argument, operator or method; rerun with fresh input.
Hint 3
The reference uses row.approved === true where the broken source uses row.approved === false. Explain why before applying it.
Reference solution
function main() {
const records = [{email: "alex@example.com", approved: true}, {email: "jordan@example.com", approved: false}];
records.filter(row => row.approved === true).forEach(row => GmailApp.createDraft(row.email, "Reviewed notice", "Ready for your review."));
}Explain and reflect
Which operation proves the intended result in human-reviewed communication workflows? Which wrong input would expose a weakness, and what would remain unchanged?
Adapt the input records and drafts 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 drafts 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.