UI pages vs Service Portal pages - do we really need UI pages anymore?

[Andrew Pishchul]

Since Service Portal has been introduced, it appears that we may not need UI pages anymore - it looks like any Service Portal page can be easily displayed 'inside' of ServiceNow:

(thanks mitchellstutler for the d3js example)

Custom UI and functionality was the primary purpose of UI pages (at least for me) and now I can use Service Portal pages (with widgets), which provide more advanced and convenient approach for that.

Is it just me or you guys have the same opinion that since we have Service Portal pages, we don't need UI pages anymore? (for Helsinki+ instances)

[Goran WitchDoc]

Im into the same thoughts as you as well. Looking into Istanbul you find for example the whole "CAB Workbench" being build in the portal. I find this a good and nice way to get away from jelly

//Göran

[mitchellstutler]

The only things off the top of my head that would potentially still need UI pages would be:

1 - Using a Glide Dialog Window that loads a UI page in a modal

2 - Needing to create a very specific page that required Angular to not be loaded

Other than those (maybe these could be done with Service Portal), I know that I personally will be using Service Portal pages as much as possible.

[RajNow]

From ServiceNow devp roadmap, ServicePortal widgets would be adopted more and more by each existing/new product in all future releases. It's a conscious decision to move away from jelly. I would think that first try everything using portal pages due to advanced features and ease of development and sharing. Jelly pages are the last resort.