SDK 4.3.0

[bryce-godfrey]

@servicenow/sdk — Release Notes

Version: 4.3.0
Availability: npm — https://www.npmjs.com/package/@servicenow/sdk

---

🚀 Overview

Version 4.3.0 introduces the highly anticipated Flow API, significant build and transform performance improvements, expanded Service Catalog support, and several new platform capabilities.

This release focuses on enabling workflow-as-code, improving developer productivity, and strengthening type safety across UI and automation development.

---

✨ New Features & Enhancements

Trusted Modules

A new trustedModules property has been added to now.config.json.

This property allows 3rd party module dependencies to be explicitly marked as trusted for Glide code execution. This enables more typical Node style dependency package development for packaging and sharing code as a dependency with sys modules, instead of using another ServiceNow app.

Example:

// Trust all packages that are in the @mycompany organization.  NOTE: wildcard * only works with organization name prefix.
{
  "trustedModules": ["@mycompany/*"]
}

// Trust an explicit package by name
{
   "trustedModules": ["package-name"]
}

⚠️ Warning: Only enable this for dependencies you fully trust.

---

Type Checking for UI Builds

UI builds using TypeScript now perform diagnostic validation during the build phase.

• .ts and .tsx files are type-checked
• Build failures occur when TypeScript errors are detected
• Improves reliability before deployment

---

Credential Storage Changes

keytar has been replaced with @napi-rs/keyring due to deprecation of keytar, maintenance, and compatibility issues.

Note for Windows users: Existing stored credentials will re-authentication after upgrading due to storage changes

---

Performance Improvements

Internal optimizations to the build and transform phases deliver:

• ~30–40% reduction in heap allocation
• Faster build times for large projects (100s of files)

Performance work will continue in future releases, as we aim to drastically bring down build and transform times!

Improve Error Diagnostics

Expose missing mandatory properties when using the Record API when using the Fluent Language Extension

---

🎊 New Fluent APIs

Flow API (MVP)

The Flow API enables building ServiceNow workflows entirely in code using Fluent. Please try this out if you are a Flow user, and give us feedback in the discussions area, we plan to keep enhancing Flows in the next few releases!

Benefits include:

• Workflow-as-code
• AI-assisted development
• Pull request reviews
• Standardized development workflows

---

Supported Capabilities

Flow Definition

• Name, description, runAs
• Flow priority and protection
• Typed flow variables

Triggers

• Record: created, updated, createdOrUpdated
• Scheduled: daily, weekly, monthly, repeat, runOnce
• Application: inboundEmail, remoteTableQuery, knowledgeManagement, slaTask

Actions

• Record CRUD operations
• Communication (email, SMS, notifications, approvals)
• Attachment management
• Email utilities
• Core utilities and task automation

Flow Logic

• Conditional branching (if, elseIf, else)
• Loops (forEach, exitLoop, skipIteration)
• Variable management
• Flow control and delays

Data & Types

• wfa.dataPill() data referencing
• Full TypeScript type safety
• Reference dot-walking support

---

MVP Limitations

The following capabilities are planned for future releases:

• ❌ Subflow invocation
• ❌ Try/Catch error handling
• ❌ Step rewind (Go-Back-To)
• ❌ Service Catalog trigger
• ❌ Catalog actions
• ❌ DateTime flow variables (use StringColumn workaround)

---

Example

An incident severity alert flow — triggers on incident creation, branches by severity, notifies stakeholders, and sets state to In Progress.

import { action, Flow, wfa, trigger } from '@servicenow/sdk/automation'

export const incidentSeverityAlertFlow = Flow(
    {
        $id: Now.ID['incident_severity_alert_flow'],
        name: 'Incident Severity Alert Flow',
        description: 'Notifies team based on incident severity and sets state to In Progress',
    },
    wfa.trigger(
        trigger.record.created,
        { $id: Now.ID['incident_created_trigger'] },
        { table: 'incident', condition: 'origin=NULL', run_flow_in: 'background' }
    ),
    (params) => {
        // Log the new incident
        wfa.action(
            action.core.log,
            { $id: Now.ID['log_incident'] },
            {
                log_level: 'info',
                log_message: `New incident: ${wfa.dataPill(params.trigger.current.short_description, 'string')}`,
            }
        )

        // High severity — notify manager + SMS all assignees
        wfa.flowLogic.if(
            {
                $id: Now.ID['check_high'],
                condition: `${wfa.dataPill(params.trigger.current.severity, 'string')}=1`,
            },
            () => {
                wfa.action(
                    action.core.sendNotification,
                    { $id: Now.ID['notify_manager'] },
                    {
                        table_name: 'incident',
                        record: wfa.dataPill(params.trigger.current.sys_id, 'reference'),
                        notification: 'high_severity_manager_notification',
                    }
                )

                wfa.flowLogic.forEach(
                    wfa.dataPill(params.trigger.current.additional_assignee_list, 'array.string'),
                    { $id: Now.ID['foreach_assignees'] },
                    () => {
                        wfa.action(
                            action.core.sendSms,
                            { $id: Now.ID['sms_assignee'] },
                            {
                                recipients: wfa.dataPill(params.trigger.current.additional_assignee_list, 'array.string'),
                                message: `High severity: ${wfa.dataPill(params.trigger.current.short_description, 'string')}`,
                            }
                        )
                    }
                )
            }
        )

        // Medium severity — SMS assignees only
        wfa.flowLogic.elseIf(
            {
                $id: Now.ID['check_medium'],
                condition: `${wfa.dataPill(params.trigger.current.severity, 'string')}=2`,
            },
            () => {
                wfa.flowLogic.forEach(
                    wfa.dataPill(params.trigger.current.additional_assignee_list, 'array.string'),
                    { $id: Now.ID['foreach_assignees_medium'] },
                    () => {
                        wfa.action(
                            action.core.sendSms,
                            { $id: Now.ID['sms_assignee_medium'] },
                            {
                                recipients: wfa.dataPill(params.trigger.current.additional_assignee_list, 'array.string'),
                                message: `Medium severity: ${wfa.dataPill(params.trigger.current.short_description, 'string')}`,
                            }
                        )
                    }
                )
            }
        )

        // Always set state to In Progress
        wfa.action(
            action.core.updateRecord,
            { $id: Now.ID['update_state'] },
            {
                table_name: 'incident',
                record: wfa.dataPill(params.trigger.current.sys_id, 'reference'),
                values: TemplateValue({ state: '2' }),
            }
        )
    }
)

---

🧾 Service Catalog Enhancements

Added support for Service Catalog and supporting entities:

• Catalog Client Scripts (catalog_script_client)
• Catalog Items (sc_cat_item)
• Catalog UI Policies (catalog_ui_policy)
• Catalog Variables (item_option_new)
• Variable Sets (item_option_new_set)
• Record Producers (sc_cat_item_producer)

Catalog Variables

Fluent provides 31 different types of catalog variables to support a wide range of form input needs. Each variable type has a specific function that creates a properly configured variable object.

Example

CatalogItem({
    $id: Now.ID['basic_catalog_item'],
    name: 'Basic Laptop Request',
    shortDescription: 'Request a standard laptop for business use',
    description: 'Use this form to request a standard laptop for business use. Approval from your manager is required.',
    catalogs: [catalogServiceCatalog],
    categories: [categoryHardware],
    variableSets: [{ variableSet: userInfoVarSet, order: 100 }],
    executionPlan: '523da512c611228900811a37c97c2014',
})

CatalogClientScript({
    $id: Now.ID['new-laptop-client-script'],
    name: 'Required By Date Validation',
    script: `function onSubmit() {
    var reqDate = g_form.getValue('required_by_date');
    var today = new Date();
    var selectedDate = new Date(reqDate);
    var diffDays = (selectedDate - today) / (1000 * 60 * 60 * 24);
    if (diffDays < 7) {
        alert('Required By date must be at least 7 days from today.');
        return false;
    }
    return true;
}
`,
    type: 'onSubmit',
    catalogItem: requestNewLaptop,
    appliesOnRequestedItems: true,
    appliesOnCatalogTasks: true,
    appliesOnTargetRecord: true,
    vaSupported: true,
})

VariableSet({
    $id: 'contact_info_set',
    title: 'Contact Information',
    internalName: 'contact_information',
    description: 'Standard contact information fields including phone, email, and address',
    type: 'singleRow',
    order: 100,
})

CatalogUIPolicy({
  $id: Now.ID['employee_request_ui_policy_external_1'],
  shortDescription: 'If urgent is true, require manager approval and show department',
  catalogCondition: `${departmentVariableSet.variables.urgent} === true`,
  variableSet: departmentVariableSet,
  appliesTo: 'set',
  actions: [
    {
      variableName: departmentVariableSet.variables.department,
      order: 100,
      mandatory: true,
      visible: true,
    }
  ],
});

CatalogItemRecordProducer({
    $id: Now.ID['basic_incident_producer'],
    name: 'Report an Incident',
    shortDescription: 'Create a new incident ticket',
    description: '<p>Use this form to report IT issues and incidents.</p>',
    table: 'incident',
    catalogs: [catalogServiceCatalog],
    categories: [categoryIncidents],
    variableSets: [
        { variableSet: incidentDetailsVarSet, order: 100 },
    ],
    hideSaveAsDraft: false,
    mandatoryAttachment: false,
    hideAttachment: true,
    availableFor: [userCriteriaITStaff],
})

Email Notification

Creates an Email Notification (sysevent_email_action) in ServiceNow.

import { EmailNotification } from '@servicenow/sdk/core'

EmailNotification({
    table: 'incident',
    name: 'Incident Assigned Notification',
    description: 'Notification sent when an incident is assigned',
    triggerConditions: {
        generationType: 'engine',
        onRecordInsert: true,
        onRecordUpdate: true,
        condition: 'assigned_toISNOTEMPTY'
    },
    recipientDetails: {
        recipientFields: ['assigned_to'],
        sendToCreator: false
    },
    emailContent: {
        contentType: 'text/html',
        subject: 'Incident ${number} assigned to you',
        messageHtml: '<p>You have been assigned incident ${number}.</p>',
        importance: 'high'
    }
})

Workspace

Configure a Workspace record (ux_workspace) for managing business entities in ServiceNow. A Workspace provides automatic page generation, standardized navigation, and table integration with landing, list, and detail pages.

import { Workspace, UxListMenuConfig, Applicability, Role, Dashboard } from '@servicenow/sdk/core';

// 1. Define roles and applicability
const userRole = Role({
    $id: Now.ID['incident_user_role'],
    name: 'x_myapp_incident.user',
    containsRoles: ['canvas_user']
});

const applicability = Applicability({
    $id: Now.ID['incident_applicability'],
    name: 'Incident Users',
    roles: [userRole]
});

// 2. Create list configuration
const incidentListConfig = UxListMenuConfig({
    $id: Now.ID['incident_list_config'],
    name: 'Incident List Configuration',
    description: 'Navigation for Incident Workspace',
    categories: [
        {
            $id: Now.ID['incidents_category'],
            title: 'Incidents',
            order: 10,
            lists: [
                {
                    $id: Now.ID['incidents_open'],
                    title: 'Open',
                    order: 10,
                    condition: 'active=true^EQ',
                    table: 'incident',
                    columns: 'number,short_description,priority,state',
                    applicabilities: [
                        {
                            $id: Now.ID['incidents_open_applicability'],
                            applicability: applicability
                        }
                    ]
                }
            ]
        }
    ]
});

// 3. Create workspace
const incidentWorkspace = Workspace({
    $id: Now.ID['incident_management_workspace'],
    title: 'Incident Management',
    path: 'incident-management',
    tables: ['incident', 'user'],
    listConfig: incidentListConfig
});

Integrating with Dashboard (par_dashboard)

import { Dashboard } from '@servicenow/sdk/core';

Dashboard({
    $id: Now.ID['my_dashboard'],
    name: 'My Dashboard',
    tabs: [
        // ... tabs configuration
    ],
    visibilities: [
        {
            $id: Now.ID['my_dashboard_visibility'],
            experience: myWorkspace // Reference to Workspace object
        }
    ],
    permissions: []
});

Sla

Add support for ServiceNow SLA definitions (contract_sla)

Example:

// Basic SLA with user specified duration
Sla({
    $id: Now.ID['incident-p1-response'],
    name: 'P1 Incident Response',
    table: 'incident',
    duration: Duration({ hours: 1 }),
    schedule: 'b1992362eb601100fcfb858ad106fe16',
    conditions: {
        start: 'priority=1',
        stop: 'state=6',
    },
})

---

✅ Summary

Version 4.3.0 delivers a major step forward in Fluent-based development with workflow automation, stronger type safety, improved performance, and expanded platform coverage.

We look forward to continued iteration and feedback in upcoming releases.

For more comprehensive samples be sure to check the sdk-examples repository.

For help or support please visit the SDK Github discussions

---

This discussion was created from the release SDK 4.3.0.

[CGraabaek]

This is awesome news!

I am specifically interested in how it works with module imports between apps.

I just tried it out, but I guess there is something I am missing.

I have two SDK 4.3.0 apps:

test-utils (x_1109743_test_uti) — a utility app that exports a validateUser function from user-util.js
incident-response (x_1109743_incident) — a consuming app that wants to import and use that function

Here's what I did:

Added "trustedModules": ["test-utils"] to now.config.json in the consuming app
Added "test-utils": "0.0.1" to dependencies in package.json of the consuming app
Imported the function in a server script:
Used it in a Business Rule defined via Fluent

The build succeeds — the SDK resolves the import and bundles everything fine. However, at runtime the Glide module system throws:

[now-sdk] Initiating the build process ... [now-sdk] Building project from /Users/xxxx/Documents/Repositories/test-sn-app... [now-sdk] Type check completed successfully [now-sdk] Running script "prebuild" from /Users/xxxx/Documents/Repositories/test-sn-app/now.prebuild.mjs [now-sdk] Bundled chunk: main.jsdbx (146120 bytes) [now-sdk] Bundled asset: main.jsdbx.map (1118267 bytes) [now-sdk] Bundled asset: index.html (430 bytes) [now-sdk] Script "prebuild" completed successfully [now-sdk] test-utils is a ServiceNow Scoped App and will not be installed automatically. [now-sdk] You will be able to use JavaScript Modules from test-utils but please make sure it is installed on your ServiceNow instance to use any other application resources. [now-sdk] Building test-utils 0.0.1... [now-sdk] RollupError: Could not resolve entry module "test-utils/src/server/user-util". [now-sdk] Done! [now-sdk] Build completed successfully

The module files from test-utils are definitely deployed on the instance (I can see them in sys_module), but the runtime require() can't resolve the package.

Any help is appreciated.

[CGraabaek]

For the incident response app that consumes the util, I do have the sys_module with external=false, it looks like this.

<?xml version="1.0"?>
<record_update table="sys_module">
  <sys_module action="INSERT_OR_UPDATE">
    <sys_id>c98ec5ffca17481eb4920fbe4cd7d469</sys_id>
    <sys_scope display_value="x_1109743_incident">66547f0985094608bfdd6a612c7eb3a2</sys_scope>
    <sys_update_name>sys_module_c98ec5ffca17481eb4920fbe4cd7d469</sys_update_name>
    <content><![CDATA[{
  "name": "incident-response",
  "version": "0.0.1",
  "description": "",
  "license": "UNLICENSED",
  "imports": {
    "#now:*": "./@types/servicenow/fluent/*/index.js"
  },
  "scripts": {
    "build": "now-sdk build",
    "deploy": "now-sdk install",
    "transform": "now-sdk transform",
    "types": "now-sdk dependencies"
  },
  "devDependencies": {
    "@servicenow/sdk": "4.3.0",
    "@servicenow/glide": "27.0.4",
    "eslint": "8.50.0",
    "@servicenow/eslint-plugin-sdk-app-plugin": "4.3.0",
    "@servicenow/isomorphic-rollup": "^1.2.11",
    "rollup-plugin-vue": "6.0.0",
    "typescript": "5.5.4"
  },
  "dependencies": {
    "vue": "3.5.21",
    "test-utils": "0.0.1"
  }
}]]></content>
    <external_source>false</external_source>
    <path>x_1109743_incident/incident-response/0.0.1/package.json</path>
    <sys_name>x_1109743_incident/incident-response/0.0.1/package.json</sys_name>
  </sys_module>
</record_update>

If there is a demo repo or something, I can also debug myself.
Also if you need any other info from me, let me know.

[bryce-godfrey]

@CGraabaek It actually looks like you are trying to load a sys module from another one of your ServiceNow Fluent apps? If so that is different from this use case, and we call that "cross scope modules". That is explicitly blocked in the Rhino engine right now, and they are still working on a way to manage that.

This use case is a 3rd party npm style package that both your apps reference. For instance if "lodash" was the trusted package you want to add that had Glide code in it that both apps want to share. You would set "lodash" as trusted, and the build would respect it.

[sonisoft-cnanda]

For using modules cross scope, we tend to expose those through a namespace object. Essentially defining a container object in a module, load it up with references to the ones we want access to cross scope, and then have one script include that requires that namespace object that is available cross scope.

But we are moving away from that and using what Bryce has enabled here which is flagging a module that we build and include with each of our apps. That way the library is pinned, and changes in another app dont break this one.

[CGraabaek]

@bryce-godfrey thanks for the clarification, I was thinking if this was the case, but it was not entirely clear to me.
Is this something that is expected to come in a later release?

[CGraabaek]

@sonisoft-cnanda that is probably the way I will go for now as well!
Do you have a working example I could take a look at?

[SapphicFire]

This is huge, excited to start leveraging this.

Flow and Catalog will be game changers for daily work for our customers.

It looks like Workspace bootstrapping will be much easier by way of Fluent too!

[DanielMadsenDK]

Very excited for this release, I can't wait to try out the Flow support!

Also a big thank you for removing the Keytar dependency, I have verified that the SDK now works in the environment that it didn't work in before.

[bryce-godfrey]

Great news!

[mak1A4]

this is the best thing servicenow has ever done for pro code developers <3 love it <3 big big thank you

[dalestubblefield]

Flow API: active property on FlowDefinition

Great work on the Flow API! I've been building flows with it today and the developer experience is solid once you understand the patterns.

One thing I noticed: the build plugin hardcodes active: false and status: 'draft' for all deployed flows (flow-definition-plugin.ts:1971-1972). There's no way to set a flow to active on deploy.

For my use case (5 simple record-triggered flows), I had to manually activate each one in Flow Designer after every deploy. It would be helpful to support an optional active property on FlowDefinition:

Flow({
    $id: Now.ID['my_flow'],
    name: 'My Flow',
    description: '...',
    active: true, // deploy as active (default: false for safety)
})

Deploying as draft by default makes sense as a safe default, but having the opt-in would save a manual step — especially for CI/CD pipelines where you can't click through Flow Designer.

Also — the sdk-examples repo doesn't have any Flow examples yet. The release notes example was enough to get me started, but a dedicated Flow example project would help adoption.

[bryce-godfrey]

The Flow team is working on what the publishing process will be when working through the SDK. There is alot of complexity there around snapshots and such, which is why you see the draft status in current version. This is a high priority item for them though, but you do need to manually publish from the instance for now as you have been doing.

[bryce-godfrey]

sdk-examples repo is now updated with Flow and Service Catalog samples