All Developer blog posts

Re: JulAI Wrap Up

est-sn-qa4 — Thu, 29 May 2025 15:20:44 GMT

https://www.servicenow.com/

Re: JulAI Wrap Up

est-sn-qa4 — Thu, 29 May 2025 15:19:50 GMT

test

Re: JulAI Wrap Up

est-sn-qa4 — Thu, 29 May 2025 14:39:43 GMT

yrdt

Re: JulAI Wrap Up

itd-dave7 — Thu, 15 May 2025 19:19:06 GMT

A fine link out

https://www.sony98.com/

Re: JulAI Wrap Up

itd-dave7 — Thu, 15 May 2025 19:05:37 GMT

Interesting link

https://www.sony97.com/

Re: JulAI Wrap Up

itd-dave7 — Thu, 15 May 2025 18:46:16 GMT

How about this? 96.

Re: JulAI Wrap Up

itd-dave7 — Thu, 15 May 2025 18:45:34 GMT

Another blog comment.

Re: JulAI Wrap Up

itd-dave7 — Thu, 15 May 2025 18:44:25 GMT

Blog comment test 95.

new blog 042925

LawrenceE — Tue, 29 Apr 2025 17:41:40 GMT

test post

test blog post ITSM

martinknyaz — Wed, 15 Jan 2025 17:39:50 GMT

dweded

Re: This is a test post

test-update — Tue, 10 Dec 2024 19:44:27 GMT

test comment

This is a test post

Career Journey Stories — Wed, 04 Dec 2024 19:48:42 GMT

This is a test post

JulAI Wrap Up

davesulliva — Fri, 27 Sep 2024 18:25:26 GMT

And that's a wrap! JulAI (July + AI) is at its end but it doesn't mean the ServiceNow Generative AI Prompt Library is over, you can still browse, vote, comment, and contribute!

The Prompt Library had 3300+ views with 50 contributions across 19 people!

Thank you so much to our contributors:

🥇Rampriya Sundaramoorthy (23 votes)
🥈Nia McCash (14 votes)
🥉Joshua Oliphant (8 votes)
Earl Duque
Lauren McManamon
Linda Kirkpatrick
Adam Celli
Astrid Sapphire
Saura Sambit
Paul Pradap Chandru
Jaspal Singh
Patrick Fedigan
Selva Arun
Shamma Negi
Stefan Taitano
Ashutosh Munot
Gujjuru Ramana Murthy
Raunak Mohanty
Sanjiv Meher

Here are some of the best prompts submitted:

(And remember, you can just hit the "Copy prompt" button and paste it right into ChatGPT, Gemini, Claude, or any other Generative AI provider, to get started)!

From Earl Duque: A prompt that generates a short description, YouTube description, and a blog post based on a provide...
From Lauren McManamon: A prompt that generates a cruise packing list
From Nia McCash: A prompt to generate LinkedIn post ideas for each day of the week tailored to the day of the week.
From Linda Kirkpatrick: Generate a large dataset of realistic incident records for a ServiceNow-like system, tailored to edu...
From Rampriya Sundaramoorthy: A prompt to summarize incident history for major incident managers.
From Astrid Sapphire: A prompt for creating interview questions to understand HR users' experience with ServiceNow Employe...
From Joshua Oliphant: A prompt for providing career advice and strategic planning to users.
From Stefan Taitano: A prompt to create 50 records in a specific table with priority and short description fields.
From Adam Celli: A prompt for generating ice breaker questions for a ServiceNow developer Meetup.
From Shamma Negi: A prompt to create a social media post promoting the new release of ServiceNow, detailing new functi...
From PaulPradap Chandru Prabudass: A prompt for brainstorming new Agile workflows in ServiceNow to improve the HR onboarding process.
From Selva Arun: Act as an AI career advisor for ServiceNow job opportunities and benefits.
From Patrick Fedigan: A prompt for mentoring and guiding new ServiceNow developers to build confidence and share knowledge...

What next?

Think you can improve on a submitted prompt? Click the "Fork" button and show us your improvement
Inspired? Tell us how you plan on using these prompts to improve your work
Contribute! Do you have prompts that help you and think others could benefit from it? We would love for you to submit it!

This prompt library was a fun little pilot. We will see how this performed and improve on it for next year. We'll likely include this app as part of Hacktoberfest, which is rapid approaching us!

Unknown Issues of Clone in ServiceNow with Examples

davesulliva — Fri, 27 Sep 2024 18:16:58 GMT

Cloning instances in ServiceNow is a crucial part of maintaining development, test, and production environments. It allows administrators to replicate production data and configurations to non-production instances for development or testing. While the cloning process is generally straightforward, there are several lesser-known issues that can arise, potentially causing disruptions. Understanding these unknown issues is essential to ensure smooth cloning operations.

1. Unintended Overwrite of Configuration Data

Issue: When cloning a production instance to a development or test instance, custom configurations or specific settings that only exist in the target environment can get overwritten, leading to unexpected behavior.

Example: Suppose a development instance has custom business rules or integrations not yet deployed to production. During a clone from production to development, these customizations may be overwritten by production configurations, resulting in lost work. For example, an integration with a third-party service in the development instance could stop functioning after the clone because the integration configurations were overwritten with production settings that don’t account for the third-party service.

Solution: Use the "Exclude Tables" feature to prevent overwriting specific configurations that are unique to the development or test environment. Make sure to document any changes in your development environment and regularly back up custom configurations.

2. Data Inconsistencies Between Environments

Issue: Data inconsistencies can occur when certain tables are excluded from the cloning process, either intentionally or unintentionally. This can lead to broken workflows or inaccurate testing conditions.

Example: If tables related to incident management workflows are excluded during a clone from production to development, the incident-related data may not be synchronized. This can result in discrepancies when testing new incident workflows in the development environment, as they won’t reflect the production environment's conditions.

Solution: Review the "Exclude Tables" list carefully before cloning to ensure that critical data tables are included. Avoid excluding tables that are essential to the processes or workflows being tested.

3. Loss of Personal or Development Data

Issue: Cloning a production instance can lead to the loss of personal or development data, including developer notes, test records, or personal task lists that are unique to non-production instances.

Example: Developers might store personal work-in-progress data, such as active test cases or prototype configurations, in the development instance. When a clone is performed from production, this data can be overwritten, causing loss of important development work. For instance, a developer may have created test records for a new feature, but after the clone, these records are replaced with production data, leading to unnecessary rework.

Solution: To prevent loss of personal data, developers should export any critical data before a clone and re-import it afterward. Another approach is to create snapshots or backups of the data using update sets.

4. Impact on Integrations and External Connections

Issue: Integrations that are configured in a non-production instance may stop functioning after a clone, as they may rely on instance-specific credentials, tokens, or URLs that are overwritten by production values.

Example: A test environment may be connected to a different external API for testing purposes, with specific tokens or credentials. After cloning from production, the development environment may inherit the production tokens or API URLs, which can cause failures when attempting to connect to the external service.

Solution: Use the "Exclude Tables" functionality to prevent integration-specific tables from being overwritten. Alternatively, after the clone, be sure to update any API credentials or tokens to match the non-production environment.

5. Notification Storms

Issue: Notifications configured in production, such as email alerts or SMS messages, may inadvertently trigger in the non-production environment after a clone, leading to a flood of unnecessary messages.

Example: Suppose email notifications for incident updates are active in production. After cloning the production instance to development, these notifications may remain active, leading to test users or administrators receiving hundreds of unnecessary incident emails when testing in the development instance.

Solution: Always deactivate email notifications and outbound email in non-production environments before cloning. ServiceNow provides a post-clone script that can be customized to turn off outbound emails after a clone.

6. Security Role Misalignment

Issue: Clone processes can disrupt role-based access controls (RBAC) in the target environment. Custom security roles or assignments that exist in the development or test instance but not in production might be overwritten, leading to security inconsistencies.

Example: In a development environment, a custom security role might grant access to specific tables or workflows for testing purposes. After a production-to-development clone, this role may be overwritten or lost, leading to permission errors for developers or testers.

Solution: Document and back up custom security roles. Use the post-clone process to manually restore roles and access settings that were specific to the target environment.

7. Post-Clone Script Failures

Issue: ServiceNow allows administrators to configure post-clone scripts that automatically execute after a clone to perform tasks such as disabling notifications, resetting credentials, or updating configurations. However, if these scripts fail, they may leave the instance in an inconsistent state.

Example: A post-clone script designed to disable outbound email might fail due to a syntax error or outdated API references, resulting in active email notifications in the development instance. This could lead to unintended emails being sent from a test environment, causing confusion or disrupting workflows.

Solution: Regularly test and update post-clone scripts to ensure they run correctly. Consider automating a validation step after a clone to verify that key configurations (such as notifications and integrations) have been properly adjusted.

Conclusion

Cloning in ServiceNow is a powerful tool for maintaining consistency across environments, but it comes with potential risks. By being aware of the lesser-known issues such as configuration overwrites, data loss, and integration failures, administrators can mitigate the impact of these issues. Proactive planning, careful use of exclusion lists, and thorough post-clone validation can help ensure successful and smooth cloning processes across all ServiceNow environments.

OMG! You've outgrown email and spreadsheets: Now let's do this right

davesulliva — Wed, 11 Oct 2023 15:16:34 GMT

Session ID: CCL1054-K22 | Session Level: Beginner

Stop emailing spreadsheets to co-workers and external team members and create a single source of authority for your information. In this lab, you will learn how to import and store data, build forms and lists for easy access, and add a workflow for automation! See how fast and easy it is to unlock productivity in your organization with an app!

Application/Capabilities:

Flow Designer
App Engine Studio

Target Personas:

Builder

8 Sections

Introduction
Getting Started
Exercise 1: Create a new App with App Engine Studio
Exercise 2: Import data and create tables
Exercise 3: Configure List & Form Layout
Exercise 4: Start the process from the Parents Portal
Exercise 5 - Create a Teachers Workspace
Summary & Outlook

Introduction

OMG! You've outgrown email and spreadsheets - Now let's do this right

Welcome to CreatorCon Lab CCL1054-K22!

If you found your way here - you are absolutely at the right place!

In this lab, you will learn how to set up a new App in ServiceNow using App Engine Studio.

Starting with adding tables to your app, you will also add different user interfaces to make the app shine. Additionally, you do not need to write a single line of code for this.

This lab is the foundation for other labs you can attend at CreatorCon. Look for CCL1055-K22 through CCL1060-K22 to go even further.

Outline for this Lab

Time	Task
10 Minutes	Getting Started
5 Minutes	Exercise 1: Create a new app with App Engine Studio
15 Minutes	Exercise 2: Import data and create tables
15 Minutes	Exercise 3: Configure list & form layout
15 Minutes	Exercise 4: Start the process from the Parent Portal
10 Minutes	Exercise 5: Create a teacher workspace
5 Minutes	Summary & Outlook

Story and Overall process

Imagine a school that wants to plan students activities (e.g. a summer camp). The Activities need to be stored in a central location, where the teacher leading the activity needs to collect the Approvals from the students' parents, so that the students are allowed to attend the given activity.

As soon as the teacher received all responses to the Approvals, he/she can set the activity to a Planned state.

Workflow

The app will:

offer the option to capture Student Activities from a central location.
Provide people a request for new activities using the ServiceNow Service Portal.
The new activities requested are be assigned to a teacher in charge, who then adds the list of students/attendees for this specific activity.
The teacher then sets the Activity record to In Approval where the system creates an approval and sends a Notification the the student's parent(s), to ask for permission to attend.
The parent(s) respond to the notification by approving or rejecting
As soon as the teacher has collected all approvals, the Activity Record is set to Planned - at which point the current progress of the workflow is visible.
Provide different user inferfaces for the different persona involved (Requester, Teacher and Parents).

The Diagram below shows the overall process that we are about to implement with the Student Permission App.

Note: This lab focuses on the base tables needed and the user interfaces, to present.

Back to Table of Contents

Getting Started

(view in My Videos)

Back to Table of Contents

Exercise 1

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.

Back to Table of Contents

Exercise 2

Back to Table of Contents

Exercise 3

Back to Table of Contents

Exercise 4

Back to Table of Contents

Exercise 5

Back to Table of Contents

Summary & Outlook

Back to Table of Contents

Sample Blog Article 83

davesulliva — Tue, 03 Oct 2023 16:55:47 GMT

This is the body for Sample Blog Article 83. This is the body for Sample Blog Article 83. This is the body for Sample Blog Article 83. This is the body for Sample Blog Article 83. This is the body for Sample Blog Article 83. This is the body for Sample Blog Article 83. This is the body for Sample Blog Article 83. This is the body for Sample Blog Article 83. This is the body for Sample Blog Article 83. This is the body for Sample Blog Article 83. This is the body for Sample Blog Article 83.

Sample Blog Article 82

davesulliva — Tue, 03 Oct 2023 16:55:11 GMT

This is the body for Sample Blog Article 82. This is the body for Sample Blog Article 82. This is the body for Sample Blog Article 82. This is the body for Sample Blog Article 82. This is the body for Sample Blog Article 82. This is the body for Sample Blog Article 82. This is the body for Sample Blog Article 82. This is the body for Sample Blog Article 82. This is the body for Sample Blog Article 82. This is the body for Sample Blog Article 82. This is the body for Sample Blog Article 82. This is the body for Sample Blog Article 82. This is the body for Sample Blog Article 82.

Sample Blog Article 81

davesulliva — Tue, 03 Oct 2023 16:51:47 GMT

This is the body for Sample Blog Article 81. This is the body for Sample Blog Article 81. This is the body for Sample Blog Article 81. This is the body for Sample Blog Article 81. This is the body for Sample Blog Article 81. This is the body for Sample Blog Article 81. This is the body for Sample Blog Article 81. This is the body for Sample Blog Article 81. This is the body for Sample Blog Article 81. This is the body for Sample Blog Article 81. This is the body for Sample Blog Article 81.

Re: Another Blog Article 32

davesulliva — Tue, 23 May 2023 15:46:53 GMT

Test comment

Another Blog Article 32

davesulliva — Mon, 24 Jul 2023 22:21:27 GMT

Teaser lorem ipsum. Lorem ipsum. Lorem ipsum. Lorem ipsum. Lorem ipsum. Lorem ipsum. Lorem ipsum. Lorem ipsum. Lorem ipsum. Lorem ipsum. Lorem ipsum. Lorem ipsum. Lorem ipsum. Lorem ipsum. Lorem ipsum. Lorem ipsum. Lorem ipsum. Lorem ipsum. Lorem ipsum. Lorem ipsum. Lorem ipsum. Lorem ipsum. Lorem ipsum. Lorem ipsum. Lorem ipsum. Lorem ipsum. Lorem ipsum. Lorem ipsum. Lorem ipsum. Lorem ipsum. Lorem ipsum. Lorem ipsum. Lorem ipsum.