Generic Javascript View

Hello,
I would like to do some testing with the Generic Javascript View node.
I see it is marked as “legacy”. Does this mean I should try to avoid using it ?

If yes : what is the recommended alternative?
If no : is there anywhere I can find some good documentation on it ?

Thanks & Best Regards,
Marc G

Hey Marc,

It’s marked as legacy to indicate that it won’t work together with the “new” view nodes. In this context, “not work” mainly means the interactivity—like selecting and filtering—won’t function across the two node sets.

We do plan to rewrite the node and give it quite a facelift to bring it up to speed with modern JS development, but that will take some time.

That said, you can absolutely still use the node. Regarding documentation, it depends on what you’re looking for—its node description is a good place to start.

Greetings,

Daniel

1 Like

Let me add:

I think you are better of going for Generic eCharts View Node for most topics where you want to visualize something in a chart… it has K-AI Support and also works with Reporting Extension…

Depends a little on what you are trying to do though…

4 Likes

Thanks Daniel and Martin. It was just that someone asked about the generic JS view.

It seems it is better to use generic eCharts, at least for now.

2 Likes

Hi Daniel,

since I’m using the GJSV a lot to create interactive and complex UI elements - often replacing dozens of widget nodes - I wanted to ask whether you could consider adding a re-execution option to the new (Generic) JS View(s).

It would help tremendously if the downstream execution could be triggered directly from within the node, instead of relying on a refresh button that also clears the generated content.

Thanks a lot!
John