Skip to content

SDK 4.4.0

Choose a tag to compare

View all tags
@bryce-godfrey bryce-godfrey released this 12 Mar 00:48
· 1 commit to master since this release
v4.4.0
20b6fdc

@servicenow/sdk — Release Notes

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

🚀 Overview

Version 4.4.0 fixes some bugs and adds a new dev server capability for front end UI building with the SDK, and some internal support for future version of Build Agent and Australia release for global app support!

New Features

Front-End Dev Server

A highly requested feature — the dev server drastically reduces build cycles and enables rapid UI development without needing to deploy to an instance. Requests are proxied to the ServiceNow instance defined in your auth credentials.

Note: Dev server scripts are included in new projects only. A future release will add a command to install it into existing projects.

Getting started:

  1. Run sdk init using the react or vue template
  2. Start the server with npm run dev

Requirements:

  • @servicenow/isomorphic-rollup >= 1.2.14
  • @servicenow/sdk >= 4.4.0
  • now.dev.mjs present in your project (generated during init)

ServiceCatalog & Flows

Add support between Flows and ServiceCatalog in Fluent for interacting with catalog variables and actions in Flows, and for Catalog Items to trigger Flows!

  • Support for Flow Service Catalog Item triggers
  • Support for getCatalogVariables action in Flows
  • Support for `createCatalogTask' action in Flows
  • Support for submitCatalogItemRequest action in Flows

See sdk-examples Flow samples

Changes

  • Fix invalid transformation for duration field for Sla
  • Fix requestMethod on CatalogItem and CatalogItemProducer not serializing properly
  • Stable UX asset IDs (will see keys.ts location changes)
  • Add protectionPolicy to ACL
  • Add tableDefaultLanguage to now.config.json to support setting language on table column labels
  • Fix APIs that were not restricting arbitrary properties!

NOTE: Many APIs were not strictly enforcing that extra properties could not be defined on the API, which caused some usage errors around mispelling properties or thinking they can add a property and it will be added to the build output, and should be fixed or removed.

For example this would not produce an error:

Property({
 $id: Now.ID['property-1'],
 name: 'x_foo.myproperty',
 randomProperty: true
})

This will now produce an error diagnostic that randomProperty does not exist as an option on Property! This may introduce a build error for existing projects when upgrading to 4.4.0, but these properties were being ignored during build causing false positives.

Assets 2
Loading
9 Join discussion