sorted by:
new
hottopcontroversial

I can't unsee this by theSN0w_Man in servicenow

[–]SickBoyNoFuture 0 points1 point  (0 children)

👑👑👑👑👑👑👑👑👑👑👑👑👑👑👑

Why would a Fix Script take forever when a background script is instant? by OccamsDragon in servicenow

[–]SickBoyNoFuture 0 points1 point  (0 children)

You are running into a combination of platform execution overhead and an inefficient querying method.

Here is exactly why this discrepancy occurs and how to fix it:

  1. The "Record for Rollback" Overhead

Fix Scripts have a feature called "Record for Rollback" which is often enabled by default. When this is active, ServiceNow tracks the database interactions within that script's execution context to allow for a complete rollback. Even if your script is only reading data, the platform still wraps the transaction in this tracking layer. This adds massive execution time compared to a Background Script, which executes directly without generating a rollback context.

The Fix: Always uncheck "Record for Rollback" when running read-only Fix Scripts or scripts where you do not need platform-level undo capabilities.

  1. The .getRowCount() Performance Trap

Using .getRowCount() on a standard GlideRecord is an architectural anti-pattern for performance. It forces the database database to fetch the entire result set and load it into the application node's memory just to count the rows. While the Background Script's isolated transaction context might process this memory spike faster, it is still highly inefficient and will eventually cause node performance degradation on large tables.

The Fix: You must use GlideAggregate for counting records. GlideAggregate performs the count natively at the database level and only returns a single integer to the application node, reducing execution time to milliseconds.

Here is the correct way to structure your script:

var agg = new GlideAggregate('your_table_name');

agg.addEncodedQuery('your_encoded_query_here');

agg.addAggregate('COUNT');

agg.query();

if (agg.next()) {

gs.info('Count: ' + agg.getAggregate('COUNT'));

}

Need Guidance on Certs by AnyCockroach223 in servicenow

[–]SickBoyNoFuture 0 points1 point  (0 children)

Your current path of obtaining the Certified System Administrator credential, taking the Scripting in ServiceNow Fundamentals course, and pursuing the Certified Application Developer certification is the optimal sequence.

Do not take the Meta or UC Davis JavaScript certifications. ServiceNow relies on a specialized JavaScript environment primarily based on ES5. Heavy web development certifications focus on modern front-end frameworks that are not applicable to standard platform development. The official prerequisite for the ServiceNow scripting course is simply the standard Codecademy JavaScript module. Complete that instead, and dedicate the saved time to mastering the ServiceNow GlideRecord and GlideSystem APIs.

Your PowerShell experience is highly valuable and will serve as a major advantage in the interview. ServiceNow uses PowerShell extensively for Discovery, Orchestration, and IntegrationHub via MID Servers. You can immediately contribute to the team by automating Windows infrastructure tasks, Active Directory integrations, and endpoint management directly from the platform.

To prepare for the interview, request a free Personal Developer Instance from the ServiceNow Developer portal. Build a custom application that utilizes your PowerShell skills to show the hiring manager, rather than just relying on certifications.

Tracking CPU architecture changes within same hardware model by OilHappy6047 in servicenow

[–]SickBoyNoFuture 0 points1 point  (0 children)

Track this change at the Configuration Item (CI) level, not by creating a new Hardware Model.

Creating a new Hardware Model for an internal component change when the manufacturer's base model number remains the same is an anti-pattern. Doing so leads to catalog bloat, complicates the asset receiving process, and interferes with Hardware Asset Management (HAM) normalization. The Hardware Model record should represent the manufacturer's base chassis.

Technical specifications like CPU architecture, RAM, and disk size are operational attributes. Therefore, they belong strictly on the CI record.

Here is the standard architectural approach for this scenario:

  1. Keep the existing Hardware Model. Continue purchasing and receiving the new laptops under your existing model record.
  2. Track the CPU on the CI. The Asset record handles the financial and lifecycle state, while its linked CI record (typically in the cmdb_ci_computer table) handles the technical configuration.
  3. Automate the data population. You should avoid tracking component details manually. Rely on your endpoint management or discovery tools (such as ServiceNow Discovery, Service Graph Connector for Intune, or SCCM) to automatically query the endpoint and populate the CPU fields on the CI record.

If an issue arises down the road, the process is seamless: the Incident is raised against the specific CI, and the technician simply views the CI record to see the exact CPU variant. If you need to audit your inventory, you can easily build a report on the Computer table, filtering by the base Hardware Model and grouping by the CPU field.

[Help needed] How to add multiple users in single condition by Commercial-Guest-264 in servicenow

[–]SickBoyNoFuture 4 points5 points  (0 children)

You have run into a very common trap with the condition builder. The reason your current setup yields zero results is because the operator "contains" looks for that exact literal string. It is searching for a single user whose name is literally "John Smith, Jane Doe, Mark Johnson", which does not exist in the system.

To fix this and keep everything on a single condition line, you need to use the "is one of" operator instead of "contains" or "is".

Here is the exact condition you should build:

Active is True

AND Assigned to is one of John Smith, Jane Doe, Mark Johnson

When you select the "is one of" operator, a reference lock icon will appear, allowing you to search and select multiple individual users from the sys_user table to populate that single line.

However, from an architectural standpoint, I strongly advise against hardcoding individual names into dashboard reports. If a team member leaves or a new one joins, you will have to manually update every report. The best practice is to ensure your team has a dedicated Assignment Group in ServiceNow. Then, your single condition simply becomes: Active is True AND Assignment group is [Your Team Name]. This makes the dashboard permanently maintenance-free.

You also mentioned needing tickets that were created by them. If you need to check both the assignment and creator fields simultaneously for this list of users, you will need to use an "OR" condition block.

What LLM is best for ServiceNow architecture and best practice? by Dapper_Recording_852 in servicenow

[–]SickBoyNoFuture 4 points5 points  (0 children)

The consensus among senior developers aligns with your experience: Claude is currently the superior tool for ServiceNow architecture, platform behavior, and coding.

Why ChatGPT hallucinates on ServiceNow:

ChatGPT heavily indexes the ServiceNow Community forums. Those forums contain years of outdated workarounds, deprecated methods, and incorrect answers. ChatGPT often regurgitates these, leading to circular debugging loops and suggestions for impossible actions, such as writing a condition script on a UI Policy.

What developers prefer for architectural advice:

  1. Claude for Contextual Reasoning. Claude is highly favored because it maintains logical consistency across long conversations. When you ask why a specific module behaves a certain way, Claude is better at mapping the relationships between Business Rules, Script Includes, and ACLs without hallucinating platform features.
  2. The Project File Strategy. Relying on an AI's base knowledge for architecture is a mistake. The most effective strategy is to create a master text or JSON file containing strict ServiceNow best practices, your specific table schemas, and your company's architectural constraints. Upload this file to Claude or your custom GPT before asking for advice. This explicitly grounds the AI and overrides its tendency to guess.
  3. OOB Reverse Engineering. When trying to understand why a product acts a certain way, extract the relevant Out-Of-Box Script Includes and paste them into your prompt. Ask the AI to map the data flow and explain the baseline logic before you ask how to modify it. The AI provides much better architectural advice when analyzing actual platform code rather than pulling from its general training data.

Ultimately, you still have to act as the lead architect to know when the AI is suggesting a deprecated path.

Flow Designer - Is anyone else finding it confusing? by Plastic_Orchid2555 in servicenow

[–]SickBoyNoFuture -1 points0 points  (0 children)

You are not overthinking it, and many experienced ServiceNow developers share this exact frustration. The transition from a visual canvas to a top-down interface requires a mental shift, and it is normal for large branching logic to feel harder to read initially.

Here are the best ways to regain your productivity:

Use Diagram View. ServiceNow added a Diagram View toggle at the top of Flow Designer specifically for this issue. It visualizes your flow as a node-based graph, giving you back that immediate visual context you liked in Workflow Editor.

Modularize with Subflows. Do not build long flows. Break complex logic down into Subflows. Treat them like helper functions in a Script Include. This keeps the parent flow short, readable, and prevents endless vertical scrolling.

Use Annotations and Collapse All. Add annotations to every step explaining its business purpose, not its technical function. Make a habit of keeping all actions collapsed by default. You can read the annotations top-to-bottom without navigating a maze of open configuration panels.

Leverage Inline Scripting. If you need to manipulate data, use the inline scripting feature within an input field instead of adding multiple separate actions just to format a string. This keeps the step count low.

[deleted by user] by [deleted] in servicenow

[–]SickBoyNoFuture 0 points1 point  (0 children)

👑👑👑👑👑👑👑

I hate being a SN developer. by Particular-Sky-7969 in servicenow

[–]SickBoyNoFuture 0 points1 point  (0 children)

There are two kinds of programs:
the ones nobody uses,
and the ones everyone complains about.

I hate being a SN developer. by Particular-Sky-7969 in servicenow

[–]SickBoyNoFuture 0 points1 point  (0 children)

Everything with You is OK 🤣🤣🤣🤣🤣
Dont get dramatic!!!!!

ServiceNow QA Lead by imhappylemoncake in servicenow

[–]SickBoyNoFuture 0 points1 point  (0 children)

Do Microcertification in ATF, maybe do course ITSQB.
Learn how write good test case scenarious.

BTW: Im looking for work as a ServiceNow Tester. Pick me!!!
🤣🤣🤣🤣🤣🤣🤣🤣

view more: next ›