Workflow Soluiton

Is there a way to retain the formatting a user inputs into a MultilineTextBoxComponent within a form so when the variable from that textbox is displayed in an email message body or Altiris ticket, the formatting is not lost?

I have a worker who tried to input some changes being made into distinct paragraphs in one multi-line textbox component when filling out a Change Request workflow project but when the email came out, all the formatting was lost and the text she had put in all ran together on one line. The same thing happenend with her text when it was entered into the Altiris ticket. Thanks for any ideas on how to overcome this.

 I have had the same issues when creating external applications pulling comments out of incidents.  

I partially figured this out on my own. I can get emails to appear formatted correctly but not using the multi-line textbox. I found a component called "HtmlEditorComponent". When put into a form, it gives you a nice input window with a formatting toolbar on top of it. Very nice. I then used the variable assigned to that component and dropped it into the email body and it worked great, keeping all the formatting I could throw at it. When I tried to put that variable into the 'Comment' section of my "CreateTicketComponent" though, the output in the ticket comment had tags troughout like shown:



So half my problem is solved ... just got to get the ticket comment part figured out. Hope that helps you a little mccarthy.cw.

 It gives me a few ideas.  Mainly its an issue of how to decipher the text from the database and format it accurately to an output such as a PDF file.  I have done some workarounds such as splitting the text on line breaks and such but its not totally accurate.

Matzebru--  I believe the formatting getting lost in the ticket comment is more of a function of the Helpdesk 6 ASDK webservices method than it is Workflow Solution.  One could test this by calling that webservice from something other than Workflow, and seeing if the ticket comment formatting (e.g. carriage returns) still get lost...I think they will.  With Service Desk 7 coming out shortly, I don't know how likely it would be that this would get fixed if indeed it is an issue with the Helpdesk 6 ASDK...that's more of an "unofficial" answer than an official one, though.