Questions about now-sdk functionality
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-09-2024 08:25 AM
As we've recently upgraded to the Xanadu release, the now-sdk became available to us for use. Since then, we've been periodically reading through the documentation and testing things out, but it has resulted in more questions than answers.
For context, the initial reason we explored the now-sdk is due to system limitations with generating custom PDFs in the platform. The available SN APIs are limited in their functionality, often not supporting CSS that is required to make a decent looking document. There are several NPM packages that handle this, however, and we'd like to use them within ServiceNow.
While it would be an excellent addition to the now-sdk, we're aware that we currently cannot write reusable code to be utilized across multiple application scopes, custom or otherwise. But for the time being, we wanted to explore what it would take to implement this for our custom-built CapEx application.
Put simply, what is the process for creating (in this case) a new UI Action for an existing scoped application that would import the necessary NPM package and execute its code?
For ServiceNow - In the future, can we see more examples on GitHub or in the docs for how to create functionality using npm packages for specific features? Currently, when searching for now-sdk specific tutorials/guides here, nothing is present.