Are Jelly scripts being phased out?

S A Martin
Tera Contributor

I have heard that Jelly scripts are being phased out in favor of Angular.js.   Is this accurate?   And if so, is it limited to any particular sections or is it just in general?

1 ACCEPTED SOLUTION

HI Steve,



When you implement the new Service Portal, there are many out of box features which will make the portal work as expected. Except that you need to make some adjustments for mobile interface.


You need not worry about the KB macros as they have been deployed as widgets.


If at all you have some record producers/catalog item with UI Macro variable type, you may need to change that UI macro into a widget and redeploy it in the site otherwise all other piece of code are self driven.



Thanks,


Vinitha.K


View solution in original post

6 REPLIES 6

Abhishek Raj3
Tera Guru

Hi Martin ,



It is but we can use jelly scripting in our Ui PAge and CMS.


We cannot use   jelly scripting in service portal.



Thanks,


Abhishek


vinitha3
Tera Guru

Yes, if you have opted for Service Portal of Helsinki then no more Jelly/Iframes, we need to adapt to angularjs/bootstrap.



Thanks,


Vinitha.K


I'm very new to this so I apologize if these follow-up questions seem a bit basic:


My company is implementing the Helsinki Service Portal but are also using the standard ServiceNow environment.



  • How does this apply to UI Macros like kb_view_common_content or kb_view_common_body?
  • Do we need to replace the existing ServiceNow default UI Macros with Angular content (it looks like the Jelly scripts are still there by default in Istanbul)?
  • If we wish to display additional fields in the Knoweldge Article View, does it need to be added to the existing Jelly script, or does the script need to be rebuilt from the ground up in Angular?

HI Steve,



When you implement the new Service Portal, there are many out of box features which will make the portal work as expected. Except that you need to make some adjustments for mobile interface.


You need not worry about the KB macros as they have been deployed as widgets.


If at all you have some record producers/catalog item with UI Macro variable type, you may need to change that UI macro into a widget and redeploy it in the site otherwise all other piece of code are self driven.



Thanks,


Vinitha.K