Uploaded image for project: 'camunda BPM'
  1. camunda BPM
  2. CAM-736

CDATA in activiti:expression is saved as escaped text

    XMLWordPrintable

Details

    Description

      Example from forum:

      Hello everybody,

      I have a process definition which was modeled with Yaoqiang. It works quite fine with camunda modeler, except for one thing, the email service task.
      The original task in the bpmn-xml-file looks like this:
      <serviceTask id="_104" activiti:type="mail" name="Benachrichtigung über Terminverzug" implementation="##WebService">
      <extensionElements>
      <activiti:field expression="${studentMail}" name="to"/>
      <activiti:field name="from" stringValue="f...@bar.de"/>
      <activiti:field name="subject" stringValue="Termin überschritten"/>
      <activiti:field name="charset" stringValue="UTF-8"/>
      <activiti:field name="html">
      <activiti:expression><![CDATA[
      <html>
      <body>
      Hallo,<br/><br/>
      ...<br/>
      Mit freundlichen Grüßen
      </body>
      </html>]]>
      </activiti:expression>
      </activiti:field>
      </extensionElements>
      <incoming>_105</incoming>
      </serviceTask>

      After changing something in the process the modeler also changes the HTML into this:

      <activiti:field name="html">
      <activiti:expression>
      <html>
      <body>
      Hallo,<br/><br/>
      ...
      <br/>
      Mit freundlichen Grüßen,<br/>
      </body>
      </html>
      </activiti:expression>
      </activiti:field>

      Is there any reason, why the modeler changes my HTML-mail-text? I'd prefer if the modeler wouldn't change anything in the process-definition without letting me know

      mgm-controller-panel

        This is the controller panel for Smart Panels app

        Attachments

          Activity

            People

              michael.schoettes Michael Schoettes
              drobisch Andreas Drobisch
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Salesforce