AnsweredAssumed Answered

Custom extension -- possible to use expressions not text?

Question asked by blezek on Mar 5, 2012
Latest reply on Nov 20, 2012 by chillwabbitt
Hi,

  We've written a custom extension to Designer.  It appears that only <activiti:string> are supported for fields, but I would like to use <activity:expression>.  Does anyone know if this is possible?

I have an item with this annotation:

   @Property(type = PropertyType.TEXT, displayName = "Message Type", required = true, defaultValue = "Status")
   @Help(displayHelpShort = "Text string indicating event type")
   private String eventType;

   @Property(type = PropertyType.TEXT, displayName = "Text", required = true, defaultValue = "Status from Workflow")
   @Help(displayHelpShort = "Text")
   private String eventText;

which produces this XML:


       <activiti:field name="eventType">
          <activiti:string>Status</activiti:string>
        </activiti:field>
        <activiti:field name="eventText">
          <activiti:string>Starting Denoising workflow for ${BOKey} with tags ${Tags}  – Has Denoise? ${Tags.containsKey("Denoise")}</activiti:string>
        </activiti:field>

but I would like to have it produce this XML (notice <activiti:expression>, not <actviti:string>):

       <activiti:field name="eventType">
          <activiti:string>status</activiti:string>
        </activiti:field>
        <activiti:field name="eventText">
          <activiti:expression>Starting Denoising workflow for ${BOKey} with tags ${Tags}  – Has Denoise? ${Tags.containsKey("Denoise")}</activiti:expression>
        </activiti:field>

Suggestions are welcome!
-dan

Outcomes