SerivceNow has already deprecated CMS from a long time in favor of moving to Service Portal. This makes a lot of sense, as CMS relied of technologies such as Jelly, static content, whereas Service Portal offer more modern technologies like Angular.
I am needing to add a couple of static pages to our custom application, where the pages are like,
- About: this page will describe what are the capabilities of the app
- Usage Guidelines: this page will have instructions on setup, and using the capabilities with some screenshots etc.
I am on the Xanadu release of the PDI and I can see that Content management is still shown.
I want to ask,
- Is it okay if I use the content management, if yes, will it require the customer to install the CMS plugin? If not, will page be broken when finally service now removes anything and everything related to CMS from the software level. Also why does the CMS still shown in the newer version of the PDIs?
- If I develop page using CMS, but do not declare "CMS as Dependency" in the application dependency list; perhaps that will still work? I know that if CMS is declared as a dependency, the application won't be able to install at all, as CMS plugin is no more possible to install on our own. (note: this dependency is still possible to install with asking service now support)
