How to export or move custom Now component from one instance to another
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-22-2022 02:34 AM
Hi Team,
We have developed and deployed a custom now component in workspace view, now we want to export or move the component into another instance. How we can export or move. Please guide me.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-22-2022 03:32 AM
Go to My companys applications, select the application scope for the component.
Then in the links in the bottom click on "Publish to updateset". Then you can move that to other instances the usual way.
If you use the application repository you can also publish to that.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-22-2022 03:41 AM
That is working for other applications, but The now component framework is different. We need to create a component from CLI, that is specific to instance. Not sure how we can export it.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-22-2022 05:58 AM
I am aware that the component is created via the CLI etc.
Have you tried what I suggested or are you dismissing it because you think it does not work? Because I have done it and unless ServiceNow have disabled that in a recent release you can do it too.
I have just done it on Rome and the updateset contains all the correct elements for the component.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-22-2022 06:38 AM
Tommy is correct here. When you deploy a component from the CLI to a dev instance, it creates or at least deploys within a scoped app. You can then promote that scoped app from the dev to test/prod through your normal development pipeline whether that is update sets or the app repo. The important thing is after you deploy the component to the instance you treat it like any other scoped app code.