Olivia Moore

Guess who just became a ServiceNow Certified Application Developer? Me! 🎉🙌 Let me tell you, this certification journey was no walk in the park, but it was worth every late night and coffee-fueled study session. I've picked up some seriously cool skills along the way: - Customizing ServiceNow apps (it's like giving your house a new renovation, but for software) - Learning JavaScript within ServiceNow (because who doesn't love a good script?) - Creating workflows that would make even the most organized person jealous - Diving deep into ServiceNow's data model (it's like being a data detective) - Playing nice with other systems using APIs (think of it as teaching different apps to be best friends) I'm pumped to put these skills to work and help businesses work smarter, not harder. If you're looking for someone to sprinkle some ServiceNow magic on your team, let's chat! #ServiceNowWizard #LevelingUp #TechLife #AlwaysLearning

185

61 Comments

Imagine this…you do all this hard work…you’ve researched the #ServiceNow job market…you’ve tweaked your resume numerous times, applied to tons of job postings, participated in various types of interviews and you’ve managed to land a job! It’s time to celebrate right? Let’s pop some champagne! 🥂 While this is certainly an achievement, especially in this challenging and evolving market, a large portion of individuals end up starting off on the wrong foot at their new job. The most common reason -- the company, department, and manager have NO onboarding checklist geared towards ServiceNow professionals. So, what ends up happening -- you attend a very basic, generic company orientation and then are handed off to your team for “next steps”. Those “next steps” aren’t usually documented, and if they are, they almost certainly aren’t specific to ServiceNow professionals. What can you do -- create your own ServiceNow specific onboarding checklist to bring to the table that includes strategic steps to not only assist with a smoother onboarding experience but increase the chance of HUGE wins for your ServiceNow career. Check out my latest video that will help you START your ServiceNow job on the right foot - https://lnkd.in/dgGeRCYn #ServiceNowCommunity #ServiceNowMVP #ServiceNowDeveloper #allenovation

92

9 Comments

Another 25 minute Developer 101 free session! 1. Do the module called Install Visual Studio Code. Yes you can use the Salesforce developer console and Code Builder but alot of organizations use VS so this class will get you comfortable with this tool. 2. Install the Salesforce Extension pack 3. Install Java JDK version 17 - there are newer versions available but several people had issues in the class with the newer versions so I recommend following their recommendation for this version. Depending on the speed of your downloads and install, this may take you the 25 minutes. If everything was smooth then you have time to watch the video VS Code Overview for Salesforce Developers before taking a break. Otherwise take a break and watch this - you are now ready to start coding! It is an exciting day! If you still have not signed up for the free Cloud Code Academy free Salesforce Developer 101 course be sure to do so at: https://lnkd.in/gM2-WeY2 and let's code together!

18

4 Comments

Are you Looking for ServiceNow Developer Interview Preparation and Mock Interviews? DM me. Most Important Interview Questions #servicenow 1.     can you tell me your current role at xxx company and the type of tasks you handle daily? 2.     Can you explain your most challenging project and how you handled it? 3.     What is your favorite module or feature in ServiceNow and why? 4.     How do you configure and customize Incident forms in ServiceNow? 5.     Can you describe how you use ACLs to secure incidents? Provide a practical example. 6.     Can you explain the difference between Client Scripts, Business Rules, and Script Includes in ServiceNow? Provide examples of when you would use each. 7.     How do you implement field-level and table-level security in ServiceNow? What are some common challenges with ACLs? 8.     What are Access Control Lists (ACLs) in ServiceNow, and how do you configure them for field-level security? 9.     Could you explain the steps involved in configuring an SLA in ServiceNow and how you monitor SLA compliance? 10.  Explain the process of creating a Service Catalog Item and associating it with a workflow? 11.  Explain how you design and manage workflows in ServiceNow. 12.  How do you handle approvals within a workflow? 13.  In one of your projects, you worked with Record Producers. How do you differentiate between Record Producers and Catalog Items? Can you give a scenario where you chose one over the other? 14.  In a situation where an Incident needs to trigger a Change Request automatically, how would you design this in ServiceNow? 15.  Suppose you encounter an issue where an email notification is not triggering as expected. What troubleshooting steps would you take to resolve this? 16.  Write a GlideAjax script that retrieves user details from the server and displays them in a Client Script. Explain each part of your code. 17.  Write a sample script to fetch user details from a user table using GlideRecord. 18.  Could you write an example Script Include that calculates the priority of an Incident based on its impact and urgency? Include the necessary Business Rule or Client Script to invoke it. 19.  Write a Client Script that disables a field if another field (e.g., priority) has a specific value. 20.  Demonstrate how you would create a transform map for importing user data from an external source. 21.  Write a background script to delete records from a custom table where the "status" field is "inactive." #servicenow #interview #preparation #mock #Interviews #followme

41

4 Comments

A good exercise for #ServiceNow beginners is to ponder the merits of tools that have overlapping outcomes. Here's one squaring off #FlowDesigner against Scheduled Jobs #ServiceNowDev #Fladvocate https://lnkd.in/d68pqn3s PS: (old content, new thumbnail)

47

4 Comments

🔍 ServiceNow Developer Riddle! 🔍 I bridge the gap between code and data, I don’t store records, but I bring them to the beta. I follow your instructions, but I don’t work alone, I’m essential when you need a record to be shown. I don’t have a UI, but I access the core, Without me, your data’s locked behind a door What am I? 💭 Think you know the answer? Drop it below! #ServiceNow #Development #Scripting #TechChallenge

4

What are Screen Flows? Screen Flows in Salesforce are a type of Flow that allows for the creation of user-interactive interfaces. These interfaces can guide users through a series of screens for data input, display information, or facilitate decision-making processes. Screen Flows are particularly useful for tasks that require user interaction and decision-making within the Salesforce environment. Examples of Screen Flows in Salesforce Customer Service Inquiry Handling: Scenario: A customer service representative receives various types of inquiries through Salesforce. Flow Implementation: A Screen Flow can be designed to guide the representative through the process of logging a new customer inquiry. The first screen could capture basic customer information, followed by screens that categorize the inquiry type, and additional screens to collect specific details about the customer’s issue. The final screen could summarize the information and submit the inquiry for processing or escalation. Employee Onboarding Process: Scenario: An HR department onboards new employees using Salesforce. Flow Implementation: A Screen Flow could streamline the onboarding process. The flow might start with screens gathering personal and professional details of the new employee. Subsequent screens could guide the employee through company policies, benefits enrollment, and role-specific training modules. Each screen can present information and collect acknowledgments or choices, ensuring a thorough and consistent onboarding experience. Sales Order Processing: Scenario: A salesperson needs to process customer orders through Salesforce. Flow Implementation: In this scenario, a Screen Flow can facilitate the order entry process. The flow could start with a screen for selecting a customer, followed by screens to add products or services to the order, apply discounts, and choose delivery options. A final screen can review the entire order, calculate totals, and confirm the transaction, streamlining the sales process and reducing the possibility of errors. Feedback Collection: Scenario: A company wishes to collect feedback on its services from clients. Flow Implementation: A Screen Flow can be created to guide clients through a feedback form. The flow might begin with a welcome screen, followed by screens asking for ratings on various aspects of the service, screens for open-ended comments, and a final screen thanking the client for their feedback. This Flow can be integrated into the client portal or sent via email links. #flows #screenflows

2

Day - 67 ServiceNow Workflow Interview Questions 3? What is turnstile workflow activity? or How to avoid workflow going into infinite loop? Ans: We can use Ternstile activity. The Turnstile activity limits how many times a workflow can pass through the same point. This activity is useful alongside the Rollback To workflow activity. Have a Great Day 😁

55

1 Comment

Which one is easier for new developers to approach: Power Apps or #ServiceNow? This week I tried setting up a Personal Developer Instance (PDI) for ServiceNow. It took me over a day to actually get to building an app because: * PDI's don't come with the App Engine Studio plugin needed for building apps. * Despite of plugin installation being an option in the ServiceNow Developer portal, this list doesn't include App Engine Studio. * You have to login to PDI to do it. The instance identity is different than the ServiceNow SSO identity. * Signing up for the program gives you the user/pwd. However, it didn't work. * After resetting the pwd from Developer portal, I was presented with the attached error: "you need a valid App Engine Studio license to continue working." * Surely this can't require purchasing a login? Asking ChatGPT about this, it agreed that this error is BS. * With nothing else left to try, I decided to reset the instance. This took ~8 hours. * Once the instance was available, pwd reset was again needed. * Finally, with the reset instance, logging into it presented me with App Engine Studio directly. * However, for the tutorial I was following, I needed another plugin to be installed. But there was no menu to access, only thing visible was App Engine Studio. * I learned that despite being called a Developer program, I still had to tick the box "Admin" in the user profile in the Developer portal side. * Now I had finally access to install plugins from the ServiceNow catalog, as well as create a new table for my app. That's 12 unnecessary hurdles to get to building on #lowcode. Coming from the #PowerApps world, it was fun to see that also ServiceNow Maker UI has the familiar "switch to classic" options in it. Parts of the UI are "modern", some are just as old as the one's coming from the XRM legacy of Microsoft Power Platform. The lesson is: this is just how it is. Whenever you're working with a software platform that has decades worth of history, the experience won't be seamless. Be it Microsoft, ServiceNow, Salesforce - there will be parts of it that won't make sense upon initial contact. Because it hasn't all been built from scratch to meet what the market needs in the year 2024. Looking forward to exploring more of ServiceNow's features, now that my PDI is fully operational

42

10 Comments

Can you really train someone to be a Salesforce Architect? I don’t think so. I recently saw an ad for Salesforce Architect training, and it got me thinking. Becoming a Salesforce Technical Architect takes years of hands-on experience—not a course. Training may cover the basics but not true architectural skills are developed through complex projects, understanding intricate systems, and integrating Salesforce across an entire business ecosystem. In my view, real-world experience is what truly defines an architect.

204

12 Comments

Today, I had a user ask if I could remove the "Add Me" button that allows a logged in user to quickly add themselves to a custom List field. I figured it had to be simple, probably a dictionary attribute, but I couldn't seem to find anything about it in the ServiceNow Community. Searching there only yielded posts about using either client scripts or UI Macros + Formatters, and while those weren't terrible options, I was surprised I couldn't find something better.   Eventually, a colleague filled me in on the fact that there is a dictionary attribute for this, after all: "no_add_me=true". Adding that to the field did the trick, quickly and easily! I figured if I had trouble finding this answer, someone else probably will, too. I hope this tip helps! #ServiceNow

208

2 Comments

Salesforce feature retirements you need to plan for...don't wait till last minute. Get your orgs audited and updated asap! 👉 API versions 21.0-30.0 within June 2025 👉 Workflows and Process Builder within December 2025

4

Embedding links in info or error messages to redirect users to a form or a record is a common requirement in ServiceNow. Remembering the HTML tags and getting the syntax right in one go is a challenge that at least I often face. That's where the RecordToHTML method comes in handy—it's much easier to remember and use. RecordToHTML, turns any record into HTML format and has potential application in other use cases. Syntax- new RecordToHTML("table", "sysid", "${short_description} - <any of record's field>", true); Just an example in the clip. #servicenowdeveloper #servicenowcommunity #servicenow #servicenowdevs

318

7 Comments

Hello #AwesomeAdmins As we all know Salesforce's Summer '24 Release Notes are out. Now Admin will be prompted to turn on MFA if they have disabled it for testing or configuration purposes. Admins can dismiss this prompt, but it reappears periodically until the MFA org-wide setting is turned on again. Image Source: Salesforce Help #Salesforce #SalesforceReleaseNotes #Ohana #trailblazer #salesforceadmin

5

I am saying this wearing the hat of the business owner and a developer. In 2024, if you are a Salesforce developer and do not understand how DevOps works, then I am afraid to say you have not spent or invested time to learn the basics. It is not good enough to simply say, "I do not know," because then businesses can easily say, "Look, we don't want you." That is the easiest thing for businesses to say. Businesses are not responsible for paying you to train so you can add value. By the end of the week or month, there is an expectation from an employee that they should be paid. I believe every business should have the similar expectation that staff will be upskilled to add value on their own time. If they can't, it is easy to find someone else. I honestly won't consider someone a developer if they do not know how to work with Git. Not in 2024.

11

1 Comment

We hope these user experience tips can help you create a more intuitive and efficient experience on ServiceNow! ✨ Visit our website to learn more about how we can support you and your organization: https://lnkd.in/e3NFZ6fT ---- #ServiceNow #UXDesign #esolutionsONE #BestPractices

5

1 Comment

🌉 From Chaos to Connection: APIs Through a Business Analyst’s Lens Picture this: A customer reports an issue through **Salesforce**, but to resolve it: 1️⃣ A ticket needs to be created in **ServiceNow** for IT support. 2️⃣ A task must be assigned in **Jira** for the engineering team. 3️⃣ Updates must flow back to Salesforce to keep the customer informed. This workflow sounds simple, but without **APIs**, it can turn into a tangled mess of manual processes, delays, and miscommunication. As a Business Analyst (BA), you are the architect of these workflows, ensuring APIs are designed to solve real business problems. 🛠 **Mapping the API Workflow as a 'BA'** Step 1: **Customer Logs an Issue in Salesforce** - **Flow**: The customer submits a complaint in Salesforce. The **ServiceNow API** captures this data (e.g., issue description, priority) and creates an IT ticket. The ticket ID is sent back to Salesforce for tracking. Step 2: **ServiceNow Sends Details to Jira** - **Flow**: When IT identifies the issue as requiring engineering input, the **Jira API** creates a task with details from ServiceNow (e.g., ticket ID, urgency). Jira assigns it to the right engineering team (based upon say urgency of the ticket) and sends the task ID back to ServiceNow ticket. Step 3: **Status Updates Across Systems** - **Flow**: Engineers resolve the task in Jira, triggering the **Jira API** to update the ticket in ServiceNow. The **Salesforce API** syncs with ServiceNow, updating the customer’s case record and notifying them about the resolution. As a BA you need to also define how statuses like "In Progress" or "Resolved" flow across systems to keep teams and customers informed. 🌟 The Outcome With clear API workflows, you achieve: - A seamless experience for customers who feel informed and valued. - Empowered teams who collaborate without barriers. - A scalable system ready for future growth. **As a BA, you’re not just documenting requirements—you’re enabling systems to speak the language of business impact.** Have you worked on a project involving APIs? Share your experience—your insights could inspire the next breakthrough! Note : You do not have to code but your task involves designing the API workflow, focusing on how it will deliver business benefits such as increased operational efficiency, enhanced scalability, and seamless integration, ultimately driving growth and providing a competitive advantage. Note : You have to enjoy analysis to enjoy being in such roles. It does not matter if you are called a Business Analyst, Product Owner, Product Manager, Technical Product Manager, etc 🙂.... #BusinessAnalysis #APIs #Automation #Salesforce #ServiceNow #Jira #TechInnovation #ProductManagement #ProductOwnership

17

Chapter 8 of my upcoming Clean Apex Code book is about object oriented programming. I have found this to be one of the topics most misunderstood around the Salesforce developer community. Very few people use object-oriented programming and sometimes when they do, it's completely overdone with very complex hierarchies of inheritance and abstraction over abstraction over abstraction. Part of the problem is most resources talk about object-oriented programming as the answer to software design as opposed to simply a paradigm. In reality some problem domains are well suited for this paradigm whereas others are not. The real skill comes from understanding when to use each Paradigm to better deliver value to our customers. The second part of the problem is that not everything can be an object and I have found most online examples to be very frustrating as they always focus on a silly animal hierarchy or a shipping service. Very few resources show real life examples of object-oriented programming for Salesforce implementations. My goal with this chapter is to close these gaps and provide a balance view of the subject. Do you use object-oriented programming in your Apex code? 🧐

96

20 Comments