Unleash the Power of Build Agents in the #BuildWithBuildAgent Challenge

[laurentapia]

Our annual #BuildWith Challenge is back for the 4th year, and we can’t wait to see what you create using ServiceNow Build Agent. Build Agent is Now Assist’s agentic AI tool designed to do all the heavy lifting of building  a fully featured ServiceNow application via natural language. #BuildWithBuildAgent is your chance to vibe code with ServiceNow and see just how fast you can build an amazing app! 

Join the challenge to get recognized and inspire the ServiceNow Community with what you can build using Build Agent. 

Complete the Challenge

 

What is Build Agent? 

ServiceNow Build Agent is a smart AI tool that helps you build, edit, and deploy full-stack applications via a conversational interface. It’s designed to support developers of all backgrounds, whether you're just starting out or a veteran of the platform. 

Build Agent is what we’ve been calling an accelerating tool; it accelerates your build process so you can bring ideas to life faster. It writes the code, organizes your files, fixes errors as it goes, and takes care of both the core logic and the user interface components. 

Just describe a task using natural language, and the agent manages the entire build process. 

Why Join the #BuildWithBuildAgent Challenge? 

• Get hands-on with ServiceNow’s innovative agentic AI tool 
• Inspire others by sharing what you built 
• Earn recognition in the Community

How to Participate: 

1. Get Started: Go into your ServiceNow IDE in your instance. Once you have activated the Build Agent skill (pre-installed on Personal Developer Instances), you can create a new application or edit an existing ServiceNow IDE app using natural language prompts. Include the initial prompt that kicked off your Build Agent journey, and any standout prompts that helped bring your app to life. 
2. Document: Share your experience with others by submitting a description (300 words or more), a quick video, or an infographic about your app on social media with the hashtag #BuildWithBuildAgent. 
3. Share: Comment on this blog post and be sure to attach a link to your social post. Include a brief description of your experience using Build Agent!

For more information on how to get started, feel free to check out the FAQs at the bottom of this post or watch the video walkthrough below. 

Getting Started with Build Agent 

Need help getting started? Check out the video below to learn how to get started with ServiceNow Build Agent and how to enter the #BuildWithBuildAgent Challenge. 

https://devlink.sn/EarlBuildWithBlog 

We’ve also compiled a helpful list of resources in our FAQs to help you get started. Explore how to participate, content creation tips, and more below. You can also access our #BuildWithBuildAgent toolkit for comprehensive guidance and best practices here. 

Still have questions? Our Community is here to support you every step of the way. Feel free to ask a question on this blog or our Now Assist forum. You can also reach out to us at buildwith@servicenow.com. Please note that response times may vary! 

Get started today and show us what you can build with Build Agent! 

General FAQs

Where Do I Enter?  

To enter, please follow all official guidelines and submit your entry by replying to this Community blog post. Your response should include a description of what you created using Build Agent, along with a direct link to your social media post where you shared your creation! Make sure to include #BuildWithBuildAgent in your social media post to enter the challenge. 

How can I get started? 

Access Build Agent in Personal Development Instance on developer.servicenow.com and sign in or create a free account. Click "Request Instance," choose the latest release, and submit your request. You'll get a URL and admin credentials within minutes to start building. 

How many natural language prompts can I use? 

For this challenge, users with Now Assist for Creator licenses have no limit! For everyone else, your ServiceNow Instance will be limited to 25 prompts. PDIs on developer.servicenow.com have a limit of 10 prompts per instance. Want to keep building with Build Agent? Just back up your work, release your Personal Developer Instance, request a new one, and continue creating your application. 

Where and What Do I Post on Community?  

Post it right here! At the bottom of this blog, leave a comment with a link to your social post, along with a description of what you’ve built using Build Agent. 

Do You Have Any Tips for Content Creation? 

We have compiled resources to help guide you through the #BuildWithBuildAgent content creation process here! 

Where and What Do I Post on Social Media?  

You can post on any social media platform, whether it’s LinkedIn, YouTube, X, Instagram, or public forums such as Reddit or Stack Overflow. You’re also welcome to share what you built using Build Agent on a personal or company blog or website. Just make sure your post is publicly accessible and includes #BuildWithBuildAgent ! 

Here’s an example of a social post: 

What if I Don’t Have Social Media or Don't Want to Post Publicly?  

Not to worry! Please send an email to BuildWith@servicenow.com, and we will contact you to redeem your swag.  

When Will I Receive My Swag?  

To receive swag, you must have completed the challenge by November 23, 9:00 AM PST, and placed your swag order no later than November 24th, 9:00 AM PST. Swag was available only while supplies lasted.

You can expect your swag to arrive in late January or early February. If you’re located outside the United States, please allow additional time for shipping. 

Do I Need to Fill Out a Submission Form?  

No submission form is required! Just follow the guidelines above and you’re good to go!  

How do I get featured in the App Gallery? 

Include the initial prompt that kicked off your Build Agent journey, and any standout prompts that helped bring your app to life. 

These prompts give us insight into your creative process and will help the team behind Build Agent choose which apps to showcase in the App Gallery. 

When Does the Challenge End?  

While the challenge officially concluded on November 24th, we welcome you to continue sharing your apps past this date. 

Who is Eligible to Enter the Challenge?  

We invite everyone aged 18 and above to join us! Whether you're an absolute beginner or an experienced developer, your contribution is valued! 

I Have a Problem Who Do I Reach Out to? 

Please comment directly on this blog or email buildwith@servicenow.com with #BuildWithBuildAgent Challenge in the subject line. Please refrain from emailing your entries to this address! We are monitoring the comments for your submissions.  

Do you have an example of what I should share on this Community blog?  

Yes! Here is an example for you. Be sure to include a link to your social media post! 

Technical FAQs

What are the usage limits? 

For Personal Developer Instances (PDI), there is a limit of 10 prompts per instance per month. For customer instances that acquire Build Agent from the ServiceNow Store, there is a limit of 25 prompts per instance per month. For instances that are licensed for Now Assist for Creator, limits are based on your license. 

When are usage limits reset? 

PDI usage limits for Build Agent prompts reset every 30 days starting from the day on which the limit is set. 

What if I run out of usage or used all my prompts before this challenge? 

The limit is per instance, so you can elect to release your current PDI and request a new one, which will reset the usage count. Remember to back up any important work on your instance before you release it. 

How long can each prompt be? 

Very long. Feel free to be as simple or verbose as you want in each prompt. You can copy and paste large console logs, lengthy Product Requirement Documentation, or even huge error messages.  

What else does Build Agent handle besides writing the code? 

• Compiling and validating source files 
• Testing of its own files 
• Pushing builds into the instance 

How does Build Agent differ from AI Agents or Agentic AI? 

While both names share “Agent,” Build Agent focuses on dev automation, whereas AI Agent (Agentic AI) focuses on task automation within workflows. Build Agent is an AI Agent. 

What are the limitations of Build Agent? 

Generally speaking, Build Agent is currently limited to the following abilities: 

• ServiceNow Fluent via the ServiceNow SDK  
• React based web components for user interfaces 

To see what ServiceNow metadata that Build Agent is able to create and edit on your behalf (like business rules, client scripts, tables, etc.), check out the documentation for Fluent here:

https://www.servicenow.com/docs/bundle/zurich-application-development/page/build/servicenow-sdk/conc... 

That means Build Agent’s scope is currently explicit. If it is not part of the Fluent SDK, then it cannot build it. But that also means that the capabilities of Build Agent are constantly growing as more and more metadata types are being added to the Fluent framework. 

What that will look like as you build your applications: Build Agent will elect to write scripted code instead of building a Flow Designer action or flow. Or another example: telling Build Agent to build something that it doesn’t have access to and forcing it to move forward despite this might cause it to build it a different way or simulate that it built it. 

Always remember that Build Agent is utilizing generative AI and can hallucinate. 

Where can I learn more about Build Agent and how to acquire it for my company? 

Read more about the product of Build Agent and Enterprise Vibe Coding at https://www.servicenow.com/products/vibe-coding.html#faq, including questions regarding governance and how Build Agent relates to App Engine. 

Terms and Conditions  

No purchase is necessary. #BuildWithBuildAgent Challenge is open only to individuals at least eighteen (18) years old at the time of entry. The Challenge begins November 12, 2025, at 10:00 a.m. Pacific Daylight Time ("PDT") and ends on November 24, 2025, at 11:59 p.m. PDT.  

Entrants must respond to the official forum with a 1) Screenshot, graphic, or video showing their app built using Build Agent or 2) a 300 minimum word description of the app they built with a screenshot using Build Agent AND entrants must post their video or blog into the ServiceNow Community Developer forum here AND share it on LinkedIn or Twitter with #BuildWithBuildAgent Challenge on their post AND the social media post will be linked to their forum post.   

The Submission must be your own, original work; The Submission must contain a relevant reason/response to the prompt of Build Agent; The Submission must meet the format and size requirements of the social platform used to enter; The Submission must conform with any applicable social media platform terms.  

The prize includes the official 2025 #BuildWithBuildAgent tote bag, while supplies last. The brand of tote bag may vary. Tote bag may take up to 4 weeks or longer to arrive once ordered. Approximate Retail Value (“ARV”): $10 USD.  

The ServiceNow Community reserves the right to access email data provided by the entrant in order to reach out to individuals who have completed the challenge. Entrants who have met the guidelines and have successfully completed the challenge will receive an email from ServiceNow with instructions on how to redeem the prize. International country restrictions will apply.  

Except where prohibited, participation in the Challenge constitutes each entrant's consent to use submission’s name, and photograph (including, without limitation, entrant’s Twitter and LinkedIn profile photo), voice, opinions and/or hometown and state for promotional purposes in any media, worldwide, without further payment or consideration. 

[Joe Wong]

Hi All,

this is my second application build using #BuildWithBuildAgent.  After to not so smooth first build where I ran into build and deploy errors.  I made a more simple and straight forward application.  My prompt was:
"I want to create an application that will help a user build a robot. The application will ask the user to choose from 4 types of head, 6 types of body, 3 types of arms and 2 types of legs."

I was very impress by all the backend work that #BuildWithBuildAgent did.  It created a very interactive user build interface even with a live preview of the build.  Because my original prompt was very vague (done on purpose), BuildAgent created a lot of the specific data.  Like the parts of the robot, I only specified I wanted 4 types of head, it actually created 4 different types of head (some options was comical) 

This was the image given for a "Tracked body".

But I can definitely see this is a great starting point of an application allowing developers to concentrate their time on fine tuning to application to meet end user needs.

Very impressive indeed.

https://www.linkedin.com/posts/joe-wong-1aab348_servicenow-buildwithbuildagent-buildwithbuildagent-a...

[yana7]

Today, I explored the AI Agent, and I'm very excited to share my experience. #BuildWithBuildAgent

Step 1: Defining the App Concept

The goal was to build a modern, visual workspace to centralize all marketing campaign activities, providing clarity and real-time insights.

Here's what I asked Build Agent to create:

• A Campaign Request system for submitting and approving new marketing initiatives. Each request included:

  • Campaign Name (String)

  • Budget (Currency)

  • Target Go-Live Date (Date)

  • State (Submitted, Approved, Rejected, Complete)

• A visual Task Board to manage all tasks related to an approved campaign. Users should be able to drag and drop tasks between columns (Open, In Progress, Pending Review, Completed). Each task should be linked to a parent campaign.

• An Analytics Dashboard positioned above the task board to provide a high-level overview.

• Automation: When a Campaign Request is marked as "Approved," automatically generate a standard set of tasks (e.g., 'Create Brief', 'Design Assets', 'Write Copy').

• Access Control: A "marketing" role to grant access, with admins having full privileges.

Step 2: Build Agent in Action

Once I provided this detailed prompt to Build Agent, it produced a fully-scoped, ready-to-run application foundation within minutes.

• Tables & Structure

  • Campaign Request – for tracking high-level initiatives.

  • Campaign Task – for individual, actionable tasks.

• UI Components (JSX)

  • Generated a modern, component-based UI structure.

  • KanbanBoard.jsx for the main drag-and-drop interface.

  • TaskCard.jsx to represent individual tasks visually.

  • AnalyticsDashboard.jsx to house the key metrics.

• Automations

  • Flow 1: Triggers on Campaign Request approval, creating a default set of child tasks and assigning them.

• Access Control

  • Created a "marketing" role.

  • Generated foundational Access Control rules (ACLs) for both tables, ensuring users could only manage their own department's data.

Step 3: Results & Observations

The app was built successfully with all tables, roles, and the entire JSX component structure in place. It needed some refinement to connect the frontend components to live data and wire up the drag-and-drop state changes, but the overall result was incredibly promising. The Build Agent handled the complex request for a modern UI automatically, and the structure was solid enough to iterate on quickly.

I can't wait to see how this tool gets better and faster over time.

 Lessons Learned

What stood out most was how Build Agent handled the creation of a modern, component-based user interface from a simple language prompt. It showed how Build Agent can translate a complex UI concept (a dashboard and an interactive Kanban board) into a structured set of JSX files, saving countless hours of manual boilerplate coding.

Summary

• App Name: Marketing Campaign Task Board

• Purpose: Track marketing campaigns, manage associated tasks visually, and generate high-level insights.

• Tables: Campaign Request, Campaign Task

• Automation: Auto-creation of tasks upon campaign approval.

• Access: Users with the "marketing" role can create and manage campaigns; admins oversee everything.

It took roughly 10-15 minutes for Build Agent to create the entire app structure — tables, roles, ACLs, and a complete JSX component framework. What started as an observation of marketing team chaos was transformed into a powerful, modern workspace for improving collaboration and visibility.

LINK : Medium

[Harsh_Deep]

🟢 As part of the #BuildWithBuildAgent challenge, I used ServiceNow’s Build Agent to create a scoped app called CSR Project Pulse, designed to manage, replicate, and analyse corporate social responsibility (CSR) initiatives across global company sites. Here’s a walkthrough of my build process:

Step 1: Define the App Concept

I started with a clear goal: track and manage CSR programs and their impact for globally distributed teams. I wanted:

• A form for CSR leads to submit new projects, including fields for site, budget, completion timeline, and description.

• Backend logic to replicate initiatives data across multiple regions.

• Dashboards to visualize CSR impact, project status, and regional trends.

• Role-based access for local managers and central CSR admins.

Step 2: Prompt Build Agent

I used the following prompt:

“Create a scoped application named CSR Project Pulse to manage, replicate, and analyse corporate social responsibility (CSR) initiatives across global company sites.

Build Agent responded with a fully scoped app:

• Global forms and workflows

• Data replication and analysis dashboards

• Automated notifications

• Role-based access controls

https://www.linkedin.com/feed/update/urn:li:activity:7394954738351394817/

#buildwithbuildagent #servicenow

[GUANYU LAI]

Hi everyone,

Over the years, I’ve been fascinated by how multi-store businesses manage their daily operations. Many managers still rely on spreadsheets and manual workflows to handle bookings, approvals, and customer feedback — effective, but cumbersome and error-prone.

That observation inspired my Build Agent project: a multi-store Appointment Management System. The app delivers a seamless, professional experience for both customers and managers:

• For customers: Intuitive store selection (Ginza, Tokyo, Shinjuku, Ikebukuro, Kyoto), real-time booking, appointment lookup, cancellations, surveys, and automated email notifications.

• For managers: One-click approve/reject workflow, daily summaries, advanced filtering, analytics dashboards, survey management, store calendar & time-slot configuration, and dynamic capacity management.

• Business intelligence: Interactive charts, KPIs, trends, and actionable insights across all stores.

• Professional design: Modern, responsive UI, status color coding, interactive elements, and mobile-ready accessibility.

Through this project, I aimed to transform a complex, manual workflow into a scalable, enterprise-ready system, demonstrating how thoughtful automation and intuitive design can empower businesses and elevate customer experiences.

https://www.linkedin.com/feed/update/urn:li:activity:7394967289797713920/

[RutuTeggi]

Hello Everyone!

Thanks @laurentapia for the details on the challenge.

As part of #BuildWithBuildAgent challenge, I'm excited to share that I have build an custom scoped application portal for "Wellness tracker for remote teams" entirely from Build Agent using natural language prompts.

Prompts:

1. Create a new application called Wellness Tracker for Remote Teams.

2. Weekly Challenges “Create a module for weekly wellness challenges to join the challenges".

3. Leaderboard “Add a leaderboard that ranks users based on completed challenges".

4. Manager Dashboard “Build a dashboard showing anonymized wellness trends for managers.”

5. Break Reminders for employees.

6. Daily Check-ins “Add a form where users can log their mood(Happy, Neutral, Stressed), energy level(1-10), and stress level(1-10) each day".

This challenge was a great hands-on way to explore the power of Al-driven app development and how Build Agent accelerates innovation on ServiceNow.

Here's my Linkedin Post URL:

https://www.linkedin.com/posts/rutu-teggi-7162a41a2_buildwithbuildagent-buildwithbuildagent-servicen...

[Sreeram Nair]

Meet Onboarding Central - a smart app I built in record time using ServiceNow Build Agent for #BuildWithBuildAgent Challenge.
It streamlines the employee onboarding process by tracking tasks, progress, and department responsibilities in one intuitive dashboard.

All I had to do was describe what I wanted:
“Create an employee onboarding dashboard with task tracking, progress visualization, and a form to add new hires.”

In minutes, Build Agent generated the data tables, built UI components, and connected the logic automatically. I iterated through prompts to adjust visuals, update workflows, and fix validations, all in natural language.

What makes Build Agent truly impressive is how collaborative and intuitive it feels. Instead of coding line-by-line, I focused on the experience and business logic, letting AI handle the complexity.

https://www.linkedin.com/posts/sreeramnat_buildwithbuildagent-servicenow-nowassist-activity-73949245... 

[Utkarsh7]

LinkedIn- post 

Proud to share my latest build — a complete Hospital Experience Portal built end-to-end on ServiceNow!

Designed a unified, role-based portal for City General Hospital using Fluent 4.x, UI Pages, Vanilla JS, and responsive UI architecture — delivering a modern, fast, and intuitive experience for Doctors, Nurses, Receptionists & Admins.

What I built:
✅ Role-specific dashboards
✅ Dynamic JS-driven content switching
✅ Mobile-first responsive design
✅ Real-time statistics & actionable widgets
✅ Scalable, future-ready architecture
✅ Fully integrated with ServiceNow platform

What this solved:
🔹 Unified one-stop portal for all hospital operations
🔹 Zero-training intuitive workflows
🔹 Faster access, better visibility, simple navigation
🔹 Ready for future enhancements — appointment calendar, vitals input, bed management & more

This project is a strong foundation toward a full-scale hospital management ecosystem — and a great experience building on ServiceNow without using heavy frameworks.

#BUILDWITHBUILDAGENT #ServiceNow #DeveloperJourney #UIDesign #PortalDevelopment #Innovation #HealthcareTech #ProductThinking #ServiceNowDeveloper #FluentUI #DigitalTransformation

[devanshsing]

🚀 Just wrapped up my Discovery Monitoring Dashboard build — and wow, this is a game changer for IT teams managing ServiceNow Discovery!

Using a modern UI + smart analytics, this dashboard helps teams monitor infrastructure, track alerts, and improve discovery success — all from one place.

In minutes, the dashboard provides:

📊 Smart Analytics
✅ Real-time discovery run monitoring
✅ Automated success rate tracking
✅ Comprehensive infrastructure metrics
✅ Interactive performance dashboards

🚨 Intelligent Alerting
✅ Severity-based alert classification
✅ Device-specific issue tracking
✅ Guided resolution workflow
✅ Critical issue prioritization

🎯 Modern Interface
✅ React-powered responsive UI
✅ Mobile-friendly dashboards
✅ Color-coded health indicators
✅ One-click data refresh

🔧 Enterprise Ready
✅ REST API integration
✅ Automated business rules
✅ Secure authentication
✅ Comes with sample data for demo/testing

No complex setup. No manual tracking. Just powerful insights.

Link of My Social media post ---  https://www.linkedin.com/posts/devansh-singh-60a75121a_buildwithbuildagent-servicenow-discovery-shar...

💡 Want to see the dashboard in action or know how I built it? Happy to share more!

#BuildWithBuildAgent #ServiceNow #Discovery #ITManagement #Dashboard #InfrastructureMonitoring 

[Gaurav Vaze]

Completed the #BuildWithBuildAgent Challenge!

Hello everyone,

I’m super excited to share that I’ve successfully completed the #BuildWithBuildAgent Challenge! It’s been an incredible experience exploring the future of low-code and pro-code development on the platform. Huge thanks to @Laurent Apia for introducing this challenge and inspiring us all.

I was blown away by the power of Build Agent in the ServiceNow IDE. With just a few well-crafted prompts, I generated a fully functional, role-secured custom application. It’s fast, intuitive, and a total game-changer for developers.

Video Demo: Code Library 
LinkedIn Post: Code Library_ Gaurav Vaze

App Name: Code Library

🧭 Application Summary This app creates a centralized hub for technical teams. It acts as a single source of truth, storing both key scripts from across the platform and essential technical documentation. It's designed to break down knowledge silos and make technical information accessible and reviewable.

Key Features

• One-Click Script Capture: A "Save to Code Library" UI Action allows users to instantly save a copy of any Business Rule, Script Include, Client Script, or Portal Widget.

• Dedicated Documentation Warehouse: A separate module for creating, managing, and categorizing rich-text technical documentation—like "how-to" guides, architectural decisions, and best practices.

• Unified Workspace UI: A modern, dark-themed workspace with two distinct parts, allowing users to seamlessly switch between the 'Script Repository' and the 'Documentation Library'. Ability to switch beteen light and dark theme

• Role-Based Access: The entire application is secured to a custom x_snc_code_lib_user role, ensuring only authorized technical staff can view or contribute.

Business Impact

• Reduces Knowledge Silos: Prevents critical scripts and institutional knowledge from being lost or hard to find.

• Accelerates Developer Onboarding: New team members can review curated "gold standard" code examples and essential documentation in one place.

• Improves Consistency: Promotes code and process consistency by providing a central repository for best practices.

🧠 My Prompt "Create a centralized 'Code Library' application with a dark, code-focused theme and a custom role x_snc_code_lib_user. The app must have two functions: 1) A repository to save read-only copies of key scripts from the instance using a UI Action on tables like sys_script and sp_widget. 2) A documentation warehouse to create, categorize, and store rich-text technical articles..."

This challenge was a brilliant showcase of what’s possible with GenAI in ServiceNow. Can’t wait to build more!

#ServiceNow #BuildWithBuildAgent #BuildAgent #GenAI 

[J Siva]

Hi All,
Good day...
Just wrapped up building the Community Emergency Response Network (CERN) application using the ServiceNow Build Agent and I’m amazed at how much low-code velocity it delivered! 🚀

This idea originally came out of last month’s Hacktoberfest Hack4Good initiative. Now, I’ve taken the first step by implementing the core app using Build Agent

Community Emergency Response Network (CERN) is a custom application built for real-time emergency coordination. 

The primary purpose of the CERN application is to provide a comprehensive, real-time platform for efficient and secure coordination during emergency and disaster events.

It achieves this through four main objectives:

 * Real-Time Incident Management: To quickly log, triage, and track the status of emerging emergency events (like floods, fires, or medical crises) from initial reporting until resolution.

 * Intelligent Volunteer & Resource Deployment: To automatically match and assign available, skilled volunteers to specific tasks based on their proximity to the incident location, ensuring the fastest and most relevant deployment of personnel and logistics items.

 * Proactive Vulnerable Person Safety: To enforce strict security protocols around sensitive data while actively monitoring the welfare of vulnerable individuals via automated check-in tracking, ensuring they receive priority intervention when contact is lost during a disaster.

 * Coordinated Public Alerting: To integrate external hazard warnings and instantly convert them into internal, actionable tasks with pre-determined priority levels, facilitating a unified and color-coded response across all operational teams.

Specifications:

• 🧠 Intelligent Assignment Engine: Auto-assigns volunteers to emergency events (like bushfires or floods) based on skills and proximity.
• 🛡️ Security & Welfare Checks: Monitors a secured Vulnerable Persons Registry and escalates tasks if someone hasn’t checked in within 24 hours.
• ⚠️ Automated Incident Creation: Converts public hazard notices into Emergency Event Records with dynamic priority.
• 📊 Self-Service Portal & Dashboard: Mobile-friendly portal for public reporting and a real-time dashboard for coordinators.
• ✅ ATF Test Cases: The Build Agent even created simple ATF test cases to validate core workflows

🚀 App Development Summary

I successfully developed this application by dividing the project into three phases.

Phase 1: App Foundation

The initial phase focused on establishing the core foundation of the application. This involved creating the necessary custom tables, defining the relationships between them, and implementing security measures such as user roles and ACLs.

Phase 2: Process Definition and Logic

Phase 2 concentrated on defining the application's process flow and implementing the business logic. Key activities included the creation of business rules, defining scheduled jobs, and developing necessary UI actions for user interaction.

Phase 3: User Experience and Analytics

The final phase addressed user experience and data visualization. I created a dedicated portal to allow users to easily submit incidents and register as volunteers, then developed an interactive dashboard to visualize key operational data and provide valuable analytics.

🛠️ Development Tools and Testing

I leveraged a build agent to create an application menu for each custom table and the portal, which it executed successfully.

During manual testing, I identified a few errors. I provided the error information to the build agent, which subsequently ran diagnostics and fixed the issues.

Finally, with two prompts remaining out of my quota of ten, I used one to request the creation of simple ATF test cases, which the agent also completed.

Overall, the development experience using BuildAgent was exceptionally good.

Video & LinkedIn Post link: https://www.linkedin.com/posts/activity-7395060038907826176-ATOw?utm_source=share&utm_medium=member_...

Prompts:

Please proceed with building the custom application according to the provided specifications.

Make sure to run diagnostics once the artifacts are created /modified.

Application Setup and Security

 * Create Application: Name it Community Emergency Response Network (CERN).

 * Create Roles: Define the cern_authority role and the cern_coordinator role.

 * Set Public Access: Allow the public to Read and Create CERN Incident records via the Portal.

 * Set Security: Apply strict access controls to restrict CERN Vulnerable Person and CERN Check-in Log records to the cern_authority role only.

Data Model (7 Custom Records)

Create these seven data records with their fields and choices:

 * CERN Incident:

   * Fields: Incident Name, Location, Reported By.

   * Choices: Status (New, Triaging, Active, Resolved), Priority (Immediate, High, Medium, Low), Type (Flood, Fire, Medical, Shelter, Infrastructure).

 * CERN Volunteer:

   * Fields: User Reference, Skills, Preferred Service Area.

   * Choice: Status (Available, Assigned, Offline).

 * CERN Resource:

   * Fields: Category, Status, Quantity/Capacity, Current Location.

   * Choices: Category (Food, Water, Shelter, Medical, Equipment), Status (Pledged, En Route, Deployed).

 * CERN Vulnerable Person:

   * Fields: Name, Address, Specific Needs, Last Check-in Date/Time.

 * CERN Task:

   * Fields: Parent Incident (Reference), Assigned To Volunteer (Reference), Priority, Status.

   * Logic: The Priority must inherit the value from the Parent Incident.

 * CERN External Alert:

   * Fields: Alert Type, Warning Level, Geographic Area, Call to Action.

   * Choices: Alert Type (Bushfire, Cyclone, Flood, Severe Weather, Extreme Heat), Warning Level (Advice, Watch and Act, Emergency Warning).

 * CERN Check-in Log:

   * Fields: Vulnerable Person Reference.

   * Choice: Check-in Type (Automated Alert, Manual Call, In-Person Visit).

Feature and Automation Implementation

 * Incident Record Producer: Create a Record Producer on the Portal for CERN Incident reporting. Automation: If the user selects Immediate Priority, automatically create a CERN Task for triage.

 * "Activate Incident" UI Action: Create a UI Action on CERN External Alert visible only to cern_coordinator. When clicked, it must create a new CERN Incident record, copying the Alert Type and Location, and setting the Priority based on the Alert's Warning Level (Emergency Warning = Immediate, Watch and Act = High, Advice = Low).

 * Volunteer Assignment Logic: Automatically assign Available volunteers to CERN Tasks by matching their Skills and choosing the closest volunteer based on proximity to the Incident's location.

 * Scheduled Check-in Job: Create a scheduled job that runs daily during active disasters. Logic: If a Vulnerable Person has not checked in within 24 hours, automatically create a high-priority CERN Task titled "VP Check-in Required" and assign it to the local authority group.

User Interface and Analytics

 * Build Portal: Create a mobile-responsive CERN Self-Service Portal.

 * Home Page Banner: The Home Page must feature a scrolling banner showing the top 3 active CERN External Alerts. Color-code the alerts: Yellow for Advice, Orange for Watch and Act, and Red for Emergency Warning.

 * Portal Forms: Include forms for Incident Reporting and Volunteer Registration.

Create Dashboard: Name the dashboard "CERN Response Overview" and include these five widgets:

 * Open Incidents Resolved

 * Incidents by Type

 * Volunteer Status Distribution 

 * Task Completion Rate 

 * Total Available Resources

“Disclaimer: Co-pilot and Gemini helped to build the streamlined 

prompts for me as per my original requirement.”