Some questions about now-sdk
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-23-2025 11:46 PM
Hi,
I am a rather pro-code oriented application developer, and I am experimenting with implementation via now-sdk on behalf of my company. To contextualize, I am working on the implementation of a REST API deployed in ServiceNow. This API contains model transformation logics (between those described in OpenAPI and ServiceNow internal models) that I want to unit test to detect possible regressions as early as possible.
After several weeks of experimenting, I have some questions and observations that I can't find the answers to that I would like to ask you.
1. package.json version
I notice that if I deploy an application in a specific version (located in my package.json descriptor), any other deployment on this version does not propagate my changes, even using the "--reinstall true" option of the CLI. Is this a limitation of the SDK (to force the increment of the version of the package.json) or of the instance setting? Used to the rolling deployment, this mechanism is slightly irritating.
2. update set management
Under the hood, the SDK will generate update sets. How are they handled on the ServiceNow side? Is there a naming logic? Where can I find documentation on this (the SDK documentation doesn't mention anything about the transformation applied by the CLI during deployment, and what this actually produces in the ServiceNow instance). In practice, I end up with update sets named "Default XX", with XX incrementing with each deployment.
3. history
When I view the details of my enterprise application, I see a lot of versions logged in the instance. I already manage the logged version of my source code via git, is it possible to not store all these histories in ServiceNow?
Beyond the history of my application, each JS file present in my application also has its own history (I have js files with more than 200 versions). Here too, the history is managed elsewhere in git, is it possible not to store all the intermediate versions of each source file? This is applicable to each Scripted REST API and Scripted REST resource.
4. resources
The existing documentation is quite basic and the examples are minimalistic: are there more advanced resources to illustrate the implementation of a complex project taking advantage of the benefits of the SDK put forward by ServiceNow? (such as the use of third-party Javascript modules).
Also, no training exists in Now Learning on this subject. Is it planned? Where can I find training items on this topic?
I think I'm forgetting some questions but I'll be sure to reply to this topic to ask them when they come back to me 🙂
Thank you for your time and answers.
Anthony
- 3,563 Views
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago
Did you solve the problem? Even for me it worked for the first push, but subsequent push from claudes are failing with the error " message: Not allowing install of third party application: no thrown error"