Author Archives: Allen Rodriguez
Script Includes are one of the main ways ServiceNow applications centralize reusable server-side JavaScript. The ServiceNow CAD value is not simply code reuse; it is having one named interface for logic that would otherwise be copied into Business Rules, flows, REST handlers, scheduled jobs, and other scripts. ServiceNow’s own technical guidance encourages small modular components […]
ServiceNow Access Controls protect records and fields by evaluating what object is secured, which operation is requested, and whether the user satisfies the required role, condition, and script logic. In the ServiceNow CAD track, that mechanism matters because application security fails when developers validate only the form they can see and not the ACL evaluation […]
Flow Designer is strongest when it orchestrates a business process across records, actions, approvals, and integrations without becoming the place where every piece of application logic is hidden. The current ServiceNow CAD learning path continues to teach custom actions, subflows, inputs, outputs, and reusable flow components because architecture—not just drag-and-drop construction—determines whether a flow remains […]
UI Policies and Data Policies both change field behavior, but they answer different enforcement questions. In the ServiceNow CAD workflow, UI Policies execute on the client and can make fields mandatory, read-only, or visible based on form state. Data Policies execute server-side and can enforce mandatory or read-only behavior regardless of whether a record is […]
Choosing between a Business Rule and a Client Script is really a decision about where correctness must live. In the ServiceNow CAD context, both are application-development tools, but they execute in different places and protect different parts of the transaction. A Client Script runs in the browser and can improve the form experience immediately; a […]
Glide Record is one of the core server-side APIs for reading and changing ServiceNow records, but the important design question is not how to call query(). It is how query conditions, indexes, ACL/application boundaries, loop behavior, business rules, and the surrounding transaction interact. The CAD exam context makes this systems view useful because a script […]
ServiceNow table design matters because tables become long-lived contracts for forms, scripts, reports, flows, APIs, ACLs, references, and integrations. The CAD exam context is useful here because application development is not only creating fields; it is deciding which data belongs together, which existing behavior should be inherited, and which choices will be hard to reverse […]
A ServiceNow application is more than a set of forms and scripts. It has a scope, data model, roles and ACLs, application-access settings, automation, integration points, and a lifecycle that determines how safely other applications can depend on it. The current 2026 ServiceNow learning path still includes the Certified Application Developer track, and the CAD […]
Telemetry at carrier scale can fail by being too sparse or by being too successful. Too little data leaves operators blind; too much unbounded data overwhelms devices, collectors, transport, storage, and analysts. The current 350-501 SPCOR v1.1 blueprint puts Automation and Assurance at 15% and explicitly calls for configuring gRPC/gNMI telemetry with dial-in/out and supported […]
Network automation in a service-provider environment is not simply replacing CLI commands with API calls. The current 350-501 SPCOR v1.1 blueprint includes YANG, NETCONF, RESTCONF, model-driven telemetry, automation, and service-provider operations because automation changes how intent is represented, how configuration reaches devices, and how drift or partial failure is detected. The distinction between automation and […]
Service-provider core resilience is not the number of redundant routers in a diagram. It is the set of customer services, control planes, and operating functions that remain usable when a defined failure occurs. The current 350-501 SPCOR v1.1 blueprint includes core architectures, routing protocols, MPLS, Segment Routing, traffic engineering, QoS, security, virtualization, and network assurance, […]
Provider QoS troubleshooting is difficult because congestion can appear as packet loss, delay, jitter, reduced throughput, application timeouts, or customer complaints long after the original bottleneck. The current 350-501 SPCOR v1.1 blueprint includes MPLS QoS models, DiffServ/IntServ concepts, trust boundaries, classification, marking, policing, shaping, queuing, and traffic engineering. The practical skill is to identify where […]
Traffic engineering exists because shortest-path routing does not automatically produce the best use of a provider network. The current 350-501 SPCOR v1.1 blueprint includes MPLS traffic engineering, SRTE, QoS models, path computation, policy, and network assurance. The useful mental model is cause and effect: demand enters the network, routing selects available paths, capacity becomes uneven, […]
Segment Routing changes the way a provider expresses a path through the network. Instead of requiring every transit node to maintain per-tunnel signaling state, the ingress can steer traffic through an ordered list of segments that identify nodes, adjacencies, services, or instructions. The current 350-501 SPCOR v1.1 blueprint explicitly includes SR, SRTE, and SRv6, so […]
Layer 2 VPN and EVPN services are valuable because they let a provider carry customer Ethernet semantics across a routed core without turning the entire provider network into one Layer 2 domain. The current 350-501 SPCOR v1.0 blueprint includes L2VPN, EVPN, MPLS, Segment Routing, and service-provider architecture, so the useful design question is not merely […]
