ServiceDesk

 View Only
  • 1.  Description field does not allow for paragraph breaks

    Posted Dec 09, 2013 07:24 PM

    Is there a way to add paragraph breaks in the description field of a ticket?  For example:

     

    Title A

    Some words and whatnot.

    Title B

    More words

     

    Thanks!!!!



  • 2.  RE: Description field does not allow for paragraph breaks

    Broadcom Employee
    Posted Dec 11, 2013 07:48 AM

    Line breaks or paragraph breaks? In ServiceDesk description is plaintext so paragraphs as such really do not exist.

    What's the ServiceDesk and Workflow version you are trying this on? There have been some issues with the consistency of line breaks in certain ServiceDesk versions.



  • 3.  RE: Description field does not allow for paragraph breaks

    Posted Dec 12, 2013 10:43 AM

    You could replace the current description component with an  Htmleditor component...

     



  • 4.  RE: Description field does not allow for paragraph breaks

    Broadcom Employee
    Posted Dec 12, 2013 10:49 AM

    There is a reason for description being plaintext. We simply cannot anticipate every kind of HTML you may write (or worse, copy-paste) into the HTMLEditor. If you want to replace the Multiline Textbox with HTMLEditor, you should definitely take additional steps to sanitize the input from that field.

    There are instances where theoretically valid HTML can screw things up a bit and there are definitely a number of places where invalid HTML will screw things up in possibly funny but very annoying ways.



  • 5.  RE: Description field does not allow for paragraph breaks

    Posted Dec 13, 2013 08:53 AM

    I would stay away from html if possible in 7.5. As Toomas said, its hard to tell what else would be affected and we saw this when we were using custom forms. We had HTML input for the description field and we couldn't work an incident in some browsers because the HTML in that field caused the window not to load. We didn't even have complex HTML, just some breaks, links and strong tags. I agree it would be nice to have formatted text in some cases but be cautious and test the entire lifecycle of an incident before implementing.