Is it possible to still use CMS in ServiceNow new installation?

[guruprasadbhat]

Applications having dependency "Content Management" (com.glide.cms) are possible to install in the newer versions of ServiceNow or not?

It appears CMS is marked as Inactive now, and Service Portal is the alternative to be used. It can be noticed as marked Inactive in the list of plugins.

However it appears to me that, the reason for not supporting CMS is, it is using Jelly and iframe etc, which don't provide such good UI experience. (cms and service portal docs).

Now, of course it is required to migrate the applications using CMS to Service Portal for long term, however I am asking is it okay to still continue to install CMS for the short term until such migrations is completed.

Such as, does the newer version of ServiceNow even allow CMS to be installed, is there any breaking changes if installed b/w CMS and Service portal perhaps; and is there any security risk with installing CMS?

[Brian Lancaster]

I believe this plugin was deprecated a long time ago. So you cannot install it on new instances.

[guruprasadbhat]

Thanks a lot for your reply. Noted about installation on new instances.

I want to add a few more info.

I found these sentences in the snow docs

• ref docs: "ServiceNow continues to support CMS in current and upcoming releases. If you have existing CMS sites and activate Service Portal on your instance, your CMS sites will continue to work, as CMS and Service Portal are separate applications."
• ref docs: "You must request the Content Management System (CMS) application from ServiceNow personnel."

The reason I was asking was, I wanted to check if an application having dependency CMS cannot even be installed until we remove the CMS dependencies. For now, I have also raised a question to snow support. I will update here if I get any reply.

[Brian Lancaster]

If an application is has dependency on CMS you must have CMS install. It should like to install CMS you need to request it via now support.