Skip to content

Commit 8ffa873

Browse files
Merge branch 'ServiceNowDevProgram:main' into main
2 parents 090f179 + 5932eba commit 8ffa873

8 files changed

Lines changed: 94 additions & 0 deletions

.github/workflows/main.yml

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -23,6 +23,7 @@ on:
2323

2424
jobs:
2525
deployment:
26+
if: github.repository == 'ServiceNowDevProgram/ServiceNow-GenAi-Prompt-Library'
2627
runs-on: ubuntu-latest
2728
steps:
2829
- name: Log payload
Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
You are a ServiceNow developer assigned to write end user documentation based on work that has been completed. The documentation should focus on three key areas:
2+
1. What was created - Describe this in detail
3+
2. How it will benefit the users
4+
3. How to utilize the new functionality
5+
6+
Ensure that the documentation is designed for users who are not technical. When the users have finished reading this article they should be prepared to utilize the new functionality.
7+
8+
Story/Use Case/Completed Work details:

Prompts/Create Release Notes

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,3 @@
1+
You are a ServiceNow Product owner who needs to create weekly release notes for your end users. The release notes should contain a short blurb about each story and include which part of the platform that work impacted. This will help end users understand what changes have been made to the platform. Ensure that the output is easy to understand by users of all technical skill levels.
2+
3+
Story titles & descriptions:

Prompts/Create Teaser for New App

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
You are a ServiceNow Platform Owner who wants to introduce a new application that your team has built on ServiceNow. You want to encourage the company to utilize the app by showcasing the value that the application will bring to the individual users. Describe some of the following details based on the included description of the app:
2+
1. Expected time saved (areas where time can be saved, not specific numbers)
3+
2. Ease of use for requesters and fulfillers
4+
3. Ease of creating reports and recording metrics
5+
6+
Ensure that the message avoids technical jargon, do not exceed 1000 words.
7+
8+
App Title:
9+
App Description:
Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
You the product owner for ServiceNow writing up a teaser for a new webinar discussing the new features for the latest release of ServiceNow, Xanadu. You want the webinar to excite your audience for your company's upcoming upgrade from the version Washington to Xanadu. Include new features specific to Xanadu. Provide three examples of varying lengths, 500 charcters, 1000 characters and 1500 characters.
Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
Assume the role of an Administrator and design an optimized notification system for incident management in ServiceNow. The goal is to make notifications more relevant, timely, and user-friendly. How would you go, step-by-step, through the process of creating this workflow?
2+
3+
Keep in mind that you will need to develop a process where low-priority incident notifications are consolidated into daily summary emails, and ensure that high-priority incidents trigger immediate notifications to alert relevant teams. Please also outline the following:
4+
5+
1. The key fields to consider when building the workflow (e.g. incident priority, status, user preferences)
6+
2. The appropriate triggers to initiate the notification (e.g. incident creation, priority change, resolution)
7+
3. Conditions to be applied to differentiate notifications for high vs. low-priority incidents
8+
4. Actions to configure for sending notifications (i.e. summary emails, instant alerts, etc.)
9+
10+
Please also provide a final workflow overview, along with best practices or considerations for making this workflow efficient and scalable, while ensuring a smooth user experience.
Lines changed: 33 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,33 @@
1+
Hi, I need your help as my personal assistant to write a LinkedIn post that promotes an article on ServiceNow's key features. The post should showcase how ServiceNow is revolutionizing IT service management (ITSM), HR service delivery, and enterprise operations with cutting-edge capabilities like automation, workflow management, and AI-powered analytics.
2+
3+
I’d like the post to focus on three main features:
4+
5+
Automation – How ServiceNow streamlines repetitive tasks, reducing manual workloads and freeing up teams for more strategic initiatives.
6+
Custom Workflows – How the platform allows users to create tailored workflows across departments, improving collaboration and business efficiency.
7+
AI Insights – How built-in AI tools provide real-time insights, helping organizations make data-driven decisions to enhance service quality and reduce downtime.
8+
9+
The tone should be engaging yet professional, tailored to IT leaders, managers, and decision-makers who are looking to optimize their operations. It would also be great if you could include an example of how a company increased productivity by 30% after implementing ServiceNow's automation tools, to make it more relatable.
10+
11+
I also need a headline that grabs attention and a few hashtags to improve visibility. Please ensure the post encourages readers to engage by either liking, commenting, or sharing, and invites them to explore the full article to learn more about how ServiceNow can help their business.
12+
13+
For example, the post could start with something like:
14+
15+
‘Transform your business with ServiceNow: Discover how automation, AI, and custom workflows are driving operational excellence.’
16+
17+
Please suggest some variants for the headline and provide 3-5 relevant hashtags."
18+
19+
Example of the LinkedIn post:
20+
21+
Headline: Maximize Efficiency with ServiceNow: Automation, Workflows, and AI Insights for the Modern Enterprise
22+
23+
In today’s fast-paced business environment, efficiency is everything. With ServiceNow, companies can streamline operations across IT, HR, and enterprise service management with powerful features like:
24+
25+
Automation – Reduce manual tasks and focus on strategic initiatives
26+
Custom Workflows – Improve collaboration and business efficiency
27+
AI-Powered Insights – Make data-driven decisions in real-time
28+
29+
One global company saw a 30% boost in productivity after implementing ServiceNow’s automation tools, allowing their teams to work smarter, not harder.
30+
31+
Explore how ServiceNow can empower your team to do more with less.
32+
33+
#ITSM #Automation #AI #WorkflowManagement #ServiceNow
Lines changed: 29 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,29 @@
1+
You are presenting a topic to a freshmen level college class. Break down the topic of ___ into several high level steps/levels/high-level bullet points.
2+
3+
Then, create a talk track that eli5s this process along with explaining what each of the keyterms means while using a common analogy throughout so that the we can teach newcomers about the topic in an approachable way.
4+
5+
For example, if I had said the topic is "Git" then you would have broken down the process into these steps: forking a repo, creating a feature branch, committing changes, creating a pull request, and a maintainer pushing the changes into the main repo
6+
7+
Then, an example of the talk track analogy that you could have provided would be:
8+
9+
Imagine you're part of a team of writers creating a big adventure storybook together. To make sure everyone can add their own chapters without mixing things up or overwriting each other's work, you follow a special process.
10+
11+
**Fork (Making Your Own Copy of the Storybook):**
12+
13+
First, you make your own photocopy of the main storybook so you can write your chapters without changing the original. This is like forking a repository in Git—creating your own copy of the project to work on independently.
14+
15+
**Branch (Starting a New Chapter):**
16+
17+
You decide to write a new chapter about a dragon adventure. To keep it organized, you start a new notebook just for this chapter. This is like creating a feature branch—a separate path where you can develop new ideas without affecting the main story.
18+
19+
**Commit (Saving Your Drafts):**
20+
21+
As you write, you finish a few pages and think, "This is good so far!" So, you save that version by putting a bookmark in it. This is like making a commit—you're saving snapshots of your work at various stages so you can go back if needed.
22+
23+
**Pull Request (Sharing Your Chapter with the Team):**
24+
25+
Once your chapter is complete, you go to the team and say, "Hey, I've written this dragon adventure chapter. Can we add it to the main storybook?" This is creating a pull request—you're requesting that your changes be reviewed and merged into the main project.
26+
27+
**Push (Adding Your Chapter to the Main Storybook):**
28+
29+
The team reads your chapter and loves it! They decide to include it in the main storybook. So, they carefully copy your chapter into the original book. This is like pushing your changes into the main repository—the final step where your work becomes part of the shared project.

0 commit comments

Comments
 (0)