Converting a custom component to fluent.

prachikomal
ServiceNow Employee
ServiceNow Employee

4 hours ago

Hey com,

how to get started with converting a custom component (seismic) to fluent?

0 Helpfuls
  • 433 Views
3 REPLIES 3

Matthew_13
Kilo Sage

3 hours ago

Yeah, this trips a lot of people up from what I have seen, so you’re not off base.

There isn’t really a direct convert Seismic to Fluent step that I know of. They’re two different layers. Seismic Now Experience is the actual UI component, while Fluent is about managing your app and configuration in code instead of records.

In most cases, what people do is:

  • Keep the Seismic component as it is

  • Use the ServiceNow IDE / Now SDK to move the app metadata into Fluent so it’s source-controlled and easier to manage

If the goal is to modernize the UI that’s more about refactoring the component to newer Next Experience patterns — Fluent doesn’t replace that part.

So it usually ends up being: UI stays Seismic, configuration moves to Fluent. 

 

@prachikomal - Please mark Accepted Solution and give a Thumbs Up if you find Helpful!!

0 Helpfuls

prachikomal
ServiceNow Employee
ServiceNow Employee

2 hours ago

Thanks Matthew, that makes sense. Is there a way to move the metadata into fluent? I cloned my custom component repo into servicenow IDE, what should be the next step?

0 Helpfuls

Matthew_13
Kilo Sage
In response to prachikomal

2 hours ago - last edited 2 hours ago

Yes — there is, but the next step depends on where the metadata currently lives.

 

If the metadata is already in your instance

After cloning/opening the project in ServiceNow IDE, the next step is to convert/synchronize the application from the instance into Fluent:

  1. Go to ServiceNow IDE inside the platform.

  2. Open your application and choose Convert application to Fluent or basically Synchronize if it’s already set up.

  3. That pulls the app’s existing XML metadata down and transforms it into .now.ts Fluent files in your project. 

If you’re using the SDK workflow, you typically:

  • Initialize from the instance, then

  • Run transform to generate Fluent SDK v3+ emphasizes transform

Example SDK version::

npx now-sdk init --from <sys_app_sysid> --auth <profile> --packageName <name>
npx now-sdk transform

If you tell me one thing; is your repo a UI component library only, or a full scoped app repo tables/BRs/ACLs included; I’ll point you to the click path in IDE or the exact SDK command flow that matches your setup.

 

@prachikomal - Please mark Accepted Solution and give a Thumbs Up if you find Helpful!!

0 Helpfuls