3 Replies · Latest reply on Dec 5, 2014 1:09 PM by Dustin Werner

    CMS Enhancements for Responsive ServiceNow ESS Portal with Twitter Bootstrap

      So the past month I've been working on enhancing the CMS to be easier to use, more powerful, and make it all around faster in deploying new custom themed ESS portals.

       

      I put together a quick video to show the progress: http://youtu.be/nxmYtWk7yXY

       

      If you have any questions or comments, I would love to hear from you.

      --------------------------------
      Nathan Firth
      Principal ServiceNow Architect
      nathan.firth@newrocket.com
      http://newrocket.com
      http://serviceportal.io

        • Re: CMS Enhancements for Responsive ServiceNow ESS Portal with Twitter Bootstrap
          Daniel Pettet

          Great video. Good to see some developments in this area. I have a few questions for you.

           

          1. How do you handle HTML5 tags? Currently ServiceNow outputs <br /> as <br></br> which is wrong. All self closing tags are also affected.

           

          2. How do you manage forms? Does the SN JS OOTB logic parse through to the end user or have you rewritten the JS validation and reference field logic inc. markup to achieve custom forms?

           

          3. Have you been able to use SASS or LESS for CSS? CSS/JS minification techniques? Server side compression?

            • Re: CMS Enhancements for Responsive ServiceNow ESS Portal with Twitter Bootstrap
              Nathan Firth

              Hi Daniel, Thanks for your response.

               

              1. Since <br/> is still considered valid HTML5, no reason to change it. Obviously there is some markup that ServiceNow produces that will never validate, so until ServiceNow starts producing valid code there is very little we can do. But we do extensive browser testing as well and so despite not validating, it still renders in browsers just fine.
              2. For handeling forms, it operates as the other content block types (ex: slideshow), where we drop a block on the page and configure which fields to be visible. For JavaScript, although it is technically possible to bring over client scripts, we purposefully did not implement them. I consider this a feature rather than a limitation, because I can think of many cases where you would want client scripts within the ServiceNow interface but would not apply to the CMS form. Also, we implemented a script field when configuring the form so that you can still use client scripts but specific to that form within CMS. One benefit of this is that we can have several forms for the same table, each with it's own fields and scripts (ex: one for creating, editing, and viewing)
              3. This is on the TO DO list. I know at least one other partner that has built a CSS template system (for variables in the stylesheet). I would love to get a full blown LESS compiler working with minification, etc, but I've been so busy I havent had much time to play with the idea yet. But that would be amazing. However, before I tackle that I think I would want to create a new CMS renderer (maybe using processors?) so that we can have a clean (and valid) markup page without all the additional js_includes and invalid markup

               

              If you have any ideas or suggestions, I'd love to continue this discussion. Good questions.

               

              Thanks, Nathan -

              --------------------------------
              Nathan Firth
              Principal ServiceNow Architect
              nathan.firth@newrocket.com
              http://newrocket.com
              http://serviceportal.io

            • Re: CMS Enhancements for Responsive ServiceNow ESS Portal with Twitter Bootstrap
              Dustin Werner

              Hi Nathan.  I watched your video with some of my fellow administrators, very impressive work.  I am just beginning to put together a CMS site, I have no experience in CMS so I am learning as I go.  It's great to have an opportunity to see what can be done.  Thanks for sharing.

               

              Dustin