DiscoveryVIP / Apps Script AcademyHelp

71. Web application architecture

Module 15 · 20 minutes · Lesson 70; earlier service and JavaScript fundamentals

Open Interactive Lesson

Discover

How can you use web application architecture without changing the wrong data?

Predict

Which values or resources will change, and which should stay unchanged? Write your prediction before execution.

Understand

A web app separates browser UI, server validation and persistent storage. The client must never be trusted to enforce permissions. A server function should validate every argument even if the form also validates. The local bridge uses isolated runs and fictional data; exporting requires choosing a deployment identity and access policy.

Example 1: Working automation

The server validates text and appends a correctly shaped task row rather than trusting a client status.

function main() {
  console.log(addTask("Read deployment guide"));
}
function addTask(text) {
  if (typeof text !== "string" || !text.trim() || text.length > 100) throw new Error("Task must contain 1–100 characters");
  SpreadsheetApp.getActiveSpreadsheet().getSheetByName("Tasks").appendRow([text.trim(), "Open"]);
  return "Saved";
}
Important line explanations
Line 1: function main() {
Define a named block of instructions. Run Script calls main; helpers run only when called.
Line 2: console.log(addTask("Read deployment guide"));
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 3: }
Close the current block. Indentation makes scope and the function boundary visible.
Line 4: function addTask(text) {
Define a named block of instructions. Run Script calls main; helpers run only when called.
Line 5: if (typeof text !== "string" || !text.trim() || text.length > 100) throw new Error("Task must contain 1–100 characters");
Reject the current operation with an explicit error instead of silently continuing on invalid assumptions.
Line 6: SpreadsheetApp.getActiveSpreadsheet().getSheetByName("Tasks").appendRow([text.trim(), "Open"]);
Resolve the current workbook. A real standalone project needs openById with a configured ID instead.
Line 7: return "Saved";
End this function and pass its value to the caller; logging alone does not return a result.
Line 8: }
Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
  "logs": [
    "Saved"
  ],
  "error": null,
  "resource": "sheets",
  "value": {
    "People": [
      [
        "Name",
        "Status"
      ],
      [
        "Alex",
        "Pending"
      ],
      [
        "Jordan",
        "Pending"
      ],
      [
        "Morgan",
        "Pending"
      ]
    ],
    "Sales": [
      [
        "Customer",
        "Amount",
        "Approved"
      ],
      [
        "Alex",
        120,
        true
      ],
      [
        "Jordan",
        80,
        false
      ],
      [
        "Morgan",
        200,
        true
      ]
    ],
    "Tasks": [
      [
        "Task",
        "Status"
      ],
      [
        "Review invoice",
        "Open"
      ],
      [
        "Publish report",
        "Complete"
      ],
      [
        "Read deployment guide",
        "Open"
      ]
    ]
  }
}

Example 2: Investigate a reproducible failure

Predict the effect of [text.trim(), "Complete"] and identify the first mismatch. This example is intentionally faulty.

function main() {
  console.log(addTask("Read deployment guide"));
}
function addTask(text) {
  if (typeof text !== "string" || !text.trim() || text.length > 100) throw new Error("Task must contain 1–100 characters");
  SpreadsheetApp.getActiveSpreadsheet().getSheetByName("Tasks").appendRow([text.trim(), "Complete"]);
  return "Saved";
}
Important line explanations
Line 1: function main() {
Define a named block of instructions. Run Script calls main; helpers run only when called.
Line 2: console.log(addTask("Read deployment guide"));
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 3: }
Close the current block. Indentation makes scope and the function boundary visible.
Line 4: function addTask(text) {
Define a named block of instructions. Run Script calls main; helpers run only when called.
Line 5: if (typeof text !== "string" || !text.trim() || text.length > 100) throw new Error("Task must contain 1–100 characters");
Reject the current operation with an explicit error instead of silently continuing on invalid assumptions.
Line 6: SpreadsheetApp.getActiveSpreadsheet().getSheetByName("Tasks").appendRow([text.trim(), "Complete"]);
Resolve the current workbook. A real standalone project needs openById with a configured ID instead.
Line 7: return "Saved";
End this function and pass its value to the caller; logging alone does not return a result.
Line 8: }
Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
  "logs": [
    "Saved"
  ],
  "error": null,
  "resource": "sheets",
  "value": {
    "People": [
      [
        "Name",
        "Status"
      ],
      [
        "Alex",
        "Pending"
      ],
      [
        "Jordan",
        "Pending"
      ],
      [
        "Morgan",
        "Pending"
      ]
    ],
    "Sales": [
      [
        "Customer",
        "Amount",
        "Approved"
      ],
      [
        "Alex",
        120,
        true
      ],
      [
        "Jordan",
        80,
        false
      ],
      [
        "Morgan",
        200,
        true
      ]
    ],
    "Tasks": [
      [
        "Task",
        "Status"
      ],
      [
        "Review invoice",
        "Open"
      ],
      [
        "Publish report",
        "Complete"
      ],
      [
        "Read deployment guide",
        "Complete"
      ]
    ]
  }
}

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() {
  console.log(addTask("Read deployment guide"));
}
function addTask(text) {
  if (typeof text !== "string" || !text.trim() || text.length > 100) throw new Error("Task must contain 1–100 characters");
  SpreadsheetApp.getActiveSpreadsheet().getSheetByName("Tasks").appendRow([text.trim(), "Open"]);
  return "Saved";
}
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: console.log(addTask("Read deployment guide"));
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 3: }
Close the current block. Indentation makes scope and the function boundary visible.
Line 4: function addTask(text) {
Define a named block of instructions. Run Script calls main; helpers run only when called.
Line 5: if (typeof text !== "string" || !text.trim() || text.length > 100) throw new Error("Task must contain 1–100 characters");
Reject the current operation with an explicit error instead of silently continuing on invalid assumptions.
Line 6: SpreadsheetApp.getActiveSpreadsheet().getSheetByName("Tasks").appendRow([text.trim(), "Open"]);
Resolve the current workbook. A real standalone project needs openById with a configured ID instead.
Line 7: return "Saved";
End this function and pass its value to the caller; logging alone does not return a result.
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": [
    "Saved",
    "Saved"
  ],
  "error": null,
  "resource": "sheets",
  "value": {
    "People": [
      [
        "Name",
        "Status"
      ],
      [
        "Alex",
        "Pending"
      ],
      [
        "Jordan",
        "Pending"
      ],
      [
        "Morgan",
        "Pending"
      ]
    ],
    "Sales": [
      [
        "Customer",
        "Amount",
        "Approved"
      ],
      [
        "Alex",
        120,
        true
      ],
      [
        "Jordan",
        80,
        false
      ],
      [
        "Morgan",
        200,
        true
      ]
    ],
    "Tasks": [
      [
        "Task",
        "Status"
      ],
      [
        "Review invoice",
        "Open"
      ],
      [
        "Publish report",
        "Complete"
      ],
      [
        "Read deployment guide",
        "Open"
      ],
      [
        "Read deployment guide",
        "Open"
      ]
    ]
  }
}

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() {
  console.log(addTask("Read deployment guide"));
}
function addTask(text) {
  if (typeof text !== "string" || !text.trim() || text.length > 100) throw new Error("Task must contain 1–100 characters");
  SpreadsheetApp.getActiveSpreadsheet().getSheetByName("Tasks").appendRow([text.trim(), "Open"]);
  return "Saved";
}
function main() {
  console.log("Start: Web application architecture");
  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: console.log(addTask("Read deployment guide"));
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 3: }
Close the current block. Indentation makes scope and the function boundary visible.
Line 4: function addTask(text) {
Define a named block of instructions. Run Script calls main; helpers run only when called.
Line 5: if (typeof text !== "string" || !text.trim() || text.length > 100) throw new Error("Task must contain 1–100 characters");
Reject the current operation with an explicit error instead of silently continuing on invalid assumptions.
Line 6: SpreadsheetApp.getActiveSpreadsheet().getSheetByName("Tasks").appendRow([text.trim(), "Open"]);
Resolve the current workbook. A real standalone project needs openById with a configured ID instead.
Line 7: return "Saved";
End this function and pass its value to the caller; logging alone does not return a result.
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: Web application architecture");
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: Web application architecture",
    "Saved",
    "Completed operation"
  ],
  "error": null,
  "resource": "sheets",
  "value": {
    "People": [
      [
        "Name",
        "Status"
      ],
      [
        "Alex",
        "Pending"
      ],
      [
        "Jordan",
        "Pending"
      ],
      [
        "Morgan",
        "Pending"
      ]
    ],
    "Sales": [
      [
        "Customer",
        "Amount",
        "Approved"
      ],
      [
        "Alex",
        120,
        true
      ],
      [
        "Jordan",
        80,
        false
      ],
      [
        "Morgan",
        200,
        true
      ]
    ],
    "Tasks": [
      [
        "Task",
        "Status"
      ],
      [
        "Review invoice",
        "Open"
      ],
      [
        "Publish report",
        "Complete"
      ],
      [
        "Read deployment guide",
        "Open"
      ]
    ]
  }
}

Build and test

Repair the supplied script so that: The server validates text and appends a correctly shaped task row rather than trusting a client status. Preserve other source data. Checks compare observable output and the named resource, not exact source text.

function main() {
  console.log(addTask("Read deployment guide"));
}
function addTask(text) {
  if (typeof text !== "string" || !text.trim() || text.length > 100) throw new Error("Task must contain 1–100 characters");
  SpreadsheetApp.getActiveSpreadsheet().getSheetByName("Tasks").appendRow([text.trim(), "Complete"]);
  return "Saved";
}

Graduated hints

Hint 1

Inspect the operation containing [text.trim(), "Complete"]. Compare it with the stated rule and the first mismatch.

Hint 2

The repair concerns [text.trim(), "Open"]. Change only the relevant argument, operator or method; rerun with fresh input.

Hint 3

The reference uses [text.trim(), "Open"] where the broken source uses [text.trim(), "Complete"]. Explain why before applying it.

Reference solution

function main() {
  console.log(addTask("Read deployment guide"));
}
function addTask(text) {
  if (typeof text !== "string" || !text.trim() || text.length > 100) throw new Error("Task must contain 1–100 characters");
  SpreadsheetApp.getActiveSpreadsheet().getSheetByName("Tasks").appendRow([text.trim(), "Open"]);
  return "Saved";
}

Explain and reflect

Which operation proves the intended result in web application architecture? Which wrong input would expose a weakness, and what would remain unchanged?

Adapt the input records and sheets 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 sheets 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.

Transfer to Google and authorization guide

Next lesson: Web applications with doGet