Fred L's Angular CMS?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-22-2015 11:24 AM
Sure was impressed to see the Jelly free, iFrame abolished CMS shown off in the keynote this morning.
So, how do we get to that? Didn't find anything on Share, no Plugins and we are in Fuji. Unless they just expect to build up from scratch.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-27-2015 06:43 AM
I know in the keynote Fred says that he is glad about no more Jelly. But I think that he means that you won't have to use jelly if you don't want to. As far as I understand that yes jelly won't be in the new Service Portal. However, the new portal isn't replacing CMS meaning that they aren't going to take away the CMS part of the platform. So that means Jelly will still be in the platform as far as I understand.
Nathan Firth, can you shed some more light on this. Will jelly still exist on the platform? Or is there a plan to remove all of jelly? I know that jelly is used throughout the whole platform not just in CMS. It's not that I want jelly to stay it just that I want to know what to plan for. As you stated, Service Portal might not be available in Geneva. I'm thinking it will be available.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-27-2015 07:12 AM
Nice question Chris.
I had same question in my mind and wanted to ask from few days. Jelly is used all over the place across platform and not only restricted to CMS. So I agree with you that it wont be taken off from platform since it may cause major issues while upgrading from prior releases to Geneva .
I was trying to learn jelly from some time but I am not sure whether to invest any time on it at this point now.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-27-2015 02:48 PM
Jelly is not going anywhere, he was referring to within Service Portal. So UI Pages, UI Macros, CMS, etc will obviously continue to use Jelly. Now my personal opinion is that if Service Portal does well, certain portions of the platform, such as Service Catalog, Knowledge, UI Pages, Macros, *could* be moved over to use the Service Portal technology. Service Portal is a lot more than just a CMS and works very well for creating data driven applications, so I wouldn't be at all surprised if it does start to replace a lot of places where Jelly was once used... but I doubt it will ever fully replace the use of Jelly within ServiceNow.
