Low-Code Apps For Dummies®, ServiceNow Special Edition (Chuck Tomasi Brad Tilton) (Z-Library)

【One-Line Pitch】 A practical guide for anyone—from business users to professional developers—who wants to build digital workflow apps quickly using ServiceNow's low-code Creator Workflows platform, without writing traditional code. 【Book Arc】 - **Opening (~0%–10%)**: Introduces the low-code concept and why it matters—IT teams are overwhelmed, and empowering more people to build apps accelerates digital transformation. Sets up the book's promise: anyone can automate, extend, and build digital workflows. - **Early (~10%–23%)**: Covers the critical planning phase—asking the right questions before building, understanding app design principles, and identifying prerequisites like getting a free ServiceNow instance. Emphasizes starting with the end in mind. - **Early-to-Middle (~23%–39%)**: Dives into data modeling fundamentals—naming tables and fields correctly (labels can change, internal names cannot), choosing between creating tables from scratch, extending existing ones, or uploading spreadsheets, and understanding the trade-offs of each approach. - **Middle (~39%–48%)**: Explores the ServiceNow toolbox in depth—App Engine Studio (AES) for guided app creation, Studio for deeper customization, UI Builder for drag-and-drop interfaces, and Flow Designer for automating approvals and tasks without code. Discusses when to extend the common "task" table. - **Late (~48%–end)**: Moves into advanced capabilities—building chatbots with Virtual Agent, testing apps with Automated Test Framework (ATF), sending surveys, adding intelligence with Performance Analytics, and concludes with ten expert tips for successful low-code development. 【Key Takeaways】 - **Planning is non-negotiable** (Early): Before building, define your business problem, success metrics, data sources, and user interactions. Walking through "day in the life" scenarios reveals requirements you'd otherwise miss. - **Naming conventions matter long-term** (Early): Table and field labels can be edited later, but internal database names cannot be changed after creation. Use singular, non-redundant table names and concise field labels to avoid maintenance headaches. - **Extending tables accelerates development** (Middle): The most common approach is extending the "task" table, which already includes assignment fields for groups and users. When in doubt, extend—you can't "unextend" later, and you can always ignore unused fields. - **Spreadsheet upload is your fastest path** (Middle): If your app is based on a spreadsheet, each worksheet maps to a table, columns become fields, and rows become records. AES provides a simple drag-and-drop import process. - **Choose field types wisely** (Middle): Plain-text fields invite inconsistent data. ServiceNow offers many field types with built-in validation—select the one that best fits your data to ensure quality. - **Flow Designer enables no-code automation** (Middle): Process owners can use natural language to automate approvals, tasks, notifications, and record operations—no scripting required. - **Test early and often** (Late): The Automated Test Framework (ATF) helps you validate your app before rollout, preventing costly fixes later. Testing is one of the ten expert tips emphasized in the final chapter. - **Leverage existing resources** (Early): Check for existing ServiceNow apps or templates before building from scratch—many processes are more common than you think, and reinventing the wheel wastes time. 【Reading Tips】 - **Skim the planning chapter (Chapter 1) if you're experienced**, but don't skip the naming conventions section—it's the most practical advice in the book and will save you hours of rework. - **Deep-read the data modeling chapter (Chapter 2)** if you're new to ServiceNow—understanding tables, fields, and the three creation methods is foundational to everything else. - **Pay special attention to the "extend vs. create from scratch" discussion**—this decision is hard to reverse, and the book offers clear guidance on when each approach makes sense. - **Use the final chapter's ten tips as a checklist** when you start building your first app—they're distilled from real-world experience and cover everything from naming to testing. - **Skip the legal/copyright front matter** (first ~5%)—it's standard boilerplate with no content value. 【Coverage Limits】 The excerpts focus primarily on the planning and data storage phases (Chapters 1–2). Detailed how-to instructions for chatbots, testing, surveys, and Performance Analytics (Chapter 5) are only outlined, not fully covered in the available material.