New article articles in Developer

TEST Build anywhere, run on ServiceNow: deploying from external IDEs

LisaL8118081040 — Thu, 09 Apr 2026 19:07:43 GMT

Prefer Cursor, Claude, or your own IDE? You can now build there and run on ServiceNow. Here’s what Build Anywherelooks like from prompt to production.

JulAI Wrap Up

itd-dave3 — Fri, 27 Sep 2024 18:25:59 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

itd-dave3 — Fri, 27 Sep 2024 18:24:32 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.

Test message 3

kh-snehad — Tue, 05 Mar 2024 17:00:00 GMT

Test for schedule

kh-snehad — Wed, 31 Jan 2024 17:00:00 GMT

Test 3

test-message 02

kh-snehad — Tue, 23 Jan 2024 09:25:24 GMT

test

test-message

kh-snehad — Tue, 23 Jan 2024 09:23:07 GMT

test

Sample Blog Article 91

kh-dave1 — Tue, 03 Oct 2023 17:05:51 GMT

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

MVP Blog Article Test 2

kh-Aishwarya — Mon, 02 Oct 2023 02:11:56 GMT

This is the body of the MVP Blog Article Test 2. This is the body of the MVP Blog Article Test 2. This is the body of the MVP Blog Article Test 2. This is the body of the MVP Blog Article Test 2. This is the body of the MVP Blog Article Test 2. This is the body of the MVP Blog Article Test 2. This is the body of the MVP Blog Article Test 2. This is the body of the MVP Blog Article Test 2. This is the body of the MVP Blog Article Test 2. This is the body of the MVP Blog Article Test 2. This is the body of the MVP Blog Article Test 2. This is the body of the MVP Blog Article Test 2. This is the body of the MVP Blog Article Test 2. This is the body of the MVP Blog Article Test 2.

test video

David8383 — Thu, 28 Sep 2023 16:43:19 GMT

Now Learning is now your one-stop shop for developer learning

kristena10 — Tue, 23 May 2023 17:43:13 GMT

ServiceNow is committed to creating great learning experiences for our developer community. We heard your feedback from ServiceNow’s annual developer survey: “Why are there multiple starting points and so much duplicate content? It’s so confusing!” That’s why we’re excited to announce that Now Learning is now your one-stop shop for developer learning! Centralizing developer learning in one place lets us provide more valuable guidance for your career journey and opens more opportunities for you to grow your ServiceNow skills.

Don’t have a Now Learning login yet?

Podcast: Break Point - Career Conversation with Ebony Akkebala

kristena10 — Wed, 13 Sep 2023 19:56:12 GMT

You never know where your next opportunity to change your life will come from. Our guest today shares her amazing story of what happened and what it resulted in - along with some other great insights.

You can't transmit the array without connecting the solid state ADP card!

adityajois — Sat, 01 Oct 2022 11:38:38 GMT

Facilis iure qui et dolores quod modi sunt maxime iusto. Pariatur est accusantium corrupti exercitationem exercitationem hic similique. Ipsum non fugiat sit rerum necessitatibus. Dicta aut labore eum consequatur dolores et numquam assumenda doloremque.

We need to back up the auxiliary EXE circuit!

adityajois — Sat, 01 Oct 2022 11:35:38 GMT

Quisquam qui molestiae quas inventore voluptas. Est aut reiciendis asperiores rerum unde occaecati expedita temporibus tenetur. Aut enim et accusamus laudantium ut. Harum odio voluptatibus eligendi voluptates. Earum rerum ea quibusdam temporibus quia nobis sit quia. Saepe nisi occaecati voluptatibus.

You can't synthesize the matrix without indexing the multi-byte COM protocol!

adityajois — Sat, 01 Oct 2022 11:35:31 GMT

Libero id sit dolores rerum. Dolor voluptatibus omnis eum recusandae soluta sunt inventore. Eum magni ea atque quibusdam. Dolores quo omnis molestiae molestias voluptatem.

I'll calculate the solid state THX array, that should feed the HDD driver!

adityajois — Sat, 01 Oct 2022 11:33:59 GMT

Quidem est nemo odit maiores nihil optio at quae quos. Sunt sit tenetur eum optio fugit iure velit ducimus. Facilis veritatis dolore.

You can't back up the monitor without copying the virtual JSON firewall!

adityajois — Sat, 01 Oct 2022 11:33:48 GMT

Fugiat veniam quibusdam enim quo beatae. Aut eligendi est ut aut dolorem incidunt sint. Laboriosam qui sit. Sed minus aspernatur quibusdam facere eum distinctio doloremque quos. In delectus vel.

I'll parse the back-end COM port, that should sensor the TCP interface!

adityajois — Sat, 01 Oct 2022 08:59:49 GMT

Eum vero illum perferendis hic. Voluptatem nemo nesciunt et perferendis quia atque deleniti facere. Qui molestiae nesciunt minus doloremque. Sit sint itaque ipsam repellendus.

Try to navigate the SQL array, maybe it will hack the digital panel!

adityajois — Sat, 01 Oct 2022 08:54:22 GMT

Ea vitae iusto sint autem mollitia ut occaecati ratione. Dolor possimus laudantium saepe veniam molestiae aut. Voluptatum autem quibusdam qui esse eveniet corrupti. Dolor aspernatur ut saepe mollitia omnis est.

Try to calculate the SMS panel, maybe it will bypass the online bus!

adityajois — Sat, 01 Oct 2022 08:46:10 GMT

Dolores totam voluptatem temporibus sit sed rem est iure. Dolor vel enim consequatur illum beatae tenetur blanditiis. Earum odit architecto rerum voluptatem voluptas rerum. Consequatur in blanditiis ab.