Need multiple `Send Task` on diagram

Users
1

I need multiple Send Task like this, but all of the same standard type !!

Untitled

So, it’s easy to add these codes to bmpn-js.js:

{
			name: "SendTaskSms",
			superClass: [
				"Task"
			],
			properties: [ 
				{
					name: "implementation",
					isAttr: true,
					type: "String"
				},
				{
					name: "operationRef",
					type: "Operation",
					isAttr: true,
					isReference: true
				},
				{
					name: "messageRef",
					type: "Message",
					isAttr: true,
					isReference: true
				}
			]
		},

.  .  .

'bpmn:SendTaskSms': function(parentGfx, element) {
   var task = renderer('bpmn:Task')(parentGfx, element);
   var pathData = pathMap.getScaledPath('TASK_TYPE_SEND', {
   xScaleFactor: 1,
   yScaleFactor: 1,
   containerWidth: 21,
   containerHeight: 14,
   position: {
	   mx: 0.285,
	   my: 0.357
	   }
  });
/* send path */ drawPath(parentGfx, pathData, {
   strokeWidth: 1,
   fill: getStrokeColor$1(element, "#ff0000"),
   stroke: getFillColor(element, defaultFillColor)
});

   return task;
},



.  .  . 
{
     label: 'Send Task Sms',
     actionName: 'replace-with-sendsms-task',
     className: 'bpmn-icon-send-sms',
     target: {
	type: 'bpmn:SendTaskSms'
     }
},

and I added the same code for Send Task Email.
But the problem is if I use the default type for bpmn:SendTask, for both Email and Sms, when the user select Sms from the list (look at picture), and then decides to change it again, all of the SendTask types are hidden from the list , I mean selecting one of the SendTask from the list, makes other SendTask types , hidden from the list.

When I define two new types bpmn:SendTaskSms and bpmn:SendTaskEmail and then export/save my diagram, the types are not standard and so can’t be read in other standard bpmn apps, except my own app !!

How could I have multiple sub Tasks of the same type, in the task type list?

After adding mutiple type of sendTask type, I want to add qa:PhoneNumber=“123456789”
for one of them and/or qa:EmasilAddress="bpmn@info.com" for another SendTask type.

2

Hi @ehsan_kabiri_33 ,

instead of introducing new element types bpmn:SendTaskSms and bpmn:SendTaskEmail, you could just use the plain bpmn:SendTask with a custom extensionElement. This would allow basic compatability with other BPMN apps.

Best
Max

1 Like