• on process

What should we do?

Behaviors in this module are legacy and we have a dedicated behavior module to host all sorts of modeling behaviors.

We should migrate what is left in this module over.

Why should we do it?

Have a single place, not multiple places, to host behaviors.

This issue is the same as bpmn-io/bpmn-js-properties-panel#270.

• on formal expression

Due to

{
      "name": "TemplateSupported",
      "isAbstract": true,
      "extends": [
        "bpmn:FlowElement"
      ],
      "properties": [
        {
          "name": "modelerTemplate",
          "isAttr": true,
          "type": "String"
        }
      ]
    }

processes do not support modelerTemplate which is therefore not applied correctly.

The task priority is currently defined as integer.
It should be defined as String since it can be an expression.

https://docs.camunda.org/manual/7.4/reference/bpmn20/custom-extensions/extension-attributes/#priority

Add which types can be used with the Camunda Extension Elements, through the meta tag, with the property allowedIn.

Documented here.

Depends on https://app.camunda.com/jira/browse/CAM-4690

• camunda:resource
• camunda:resultVariable

AT:

rename semanticVersion to versionTag

This is needed for: bpmn-io/bpmn-js-properties-panel#179

A bpmn element with type camunda:Collectable can also have an attribute called elementVariable which is missing in the moddle.

Is your feature request related to a problem? Please describe.

Describe the solution you'd like

When a Start Event with camunda:initiator property is moved or created in a SubProcess, the property should be removed.

Describe alternatives you've considered

Additional context

Related to bpmn-io/bpmn-js#778

https://docs.camunda.org/manual/7.15/reference/bpmn20/custom-extensions/extension-attributes/#initiator

Example diagram:

<?xml version="1.0" encoding="UTF-8"?>
<bpmn:definitions ... camunda:diagramRelationId="foo">
  ...
</bpmn:definitions>

I'm truly out of my depth here, but I could not pull camunda moddle into my code directly because Webpack 4 seems to wrap such objects in an additional layer.

See the details of my issue here (with my hack fix):

https://forum.camunda.org/t/error-package-with-prefix-undefined-already-defined/8126/2

this includes:

• camunda:field
• camunda:string

Further details about the individual elements can be found here.

EventDefinition

• camunda:escalationCodeVariable #4
• camunda:errorCodeVariable #5
• camunda:async #2

UserTask

• camunda:assignee
• camunda:candidateGroups
• camunda:candidateUsers
• camunda:dueDate
• camunda:priority
• camunda:followUpDate

BusinessRuleTask

• camunda:decisionRef
• camunda:decisionRefBinding
• camunda:descisionRefVersion

ScriptTask

• camunda:resource #9
• camunda:resultVariable #9

CallActivity

• camunda:calledElementBinding
• camunda:calledElementVersion
• camunda:caseBinding #10
• camunda:caseRef #10
• camunda:caseVersion #10
• camunda:in #10
• camunda:out #10

Others

• camunda:class
• camunda:expression
• camunda:delegateExpression
• camunda:formKey
• camunda:initiator
• camunda:resultVariable
• camunda:type
• camunda:topic
• camunda:formHandlerClass #19
• camunda:connector #12
• camunda:connectorId #12
• camunda:executionListener
• camunda:field #16
• camunda:formProperty #13
• camunda:potentialStarter #15
• camunda:string
• camunda:taskListener #6
• camunda:candidateStarterGroups #18
• camunda:candidateStarterUsers #18

Multi Instance

• camunda:collection
• camunda:elementVariable
• camunda:exclusive
• camunda:asyncBefore
• camunda:asyncAfter

Asynchronous Continuations

• camunda:asyncBefore
• camunda:asyncAfter
• camunda:exclusive
• camunda:failedJobRetryTimeCycle
• camunda:jobPriority #11

Extension Elements

• camunda:resource #17
• camunda:formData #8
• camunda:formField #8
• camunda:validation #8
• camunda:constraint #8
• camunda:value #8
• camunda:properties #3
• camunda:property #3
• camunda:inputParameter #14
• camunda:inputOutput #12
• camunda:outputParameter #14
• camunda:list #14
• camunda:map #14
• camunda:entry #14

• wire camunda:executionListener#script
• add camunda:script

• SignalEventDefinition
• ServiceTaskLike

• connector -> Message Event Definition of Message Intermediate Throwing Event or Message End Event

• executionListener -> Embedded Subprocess, Event SubProcess, Transaction SubProcess (type SubProcess)

• failedJobRetryTimeCycle -> bpmn:TimerEventDefinition (for Timer Start Event, Timer Intermediate Catching Event, Timer Boundary Event), SignalEventDefinition, MultiInstanceLoopCharacteristics

• field -> Message Event Definition of Message Intermediate Throwing Event or Message End Event

• camunda:caseBinding
• camunda:caseRef
• camunda:caseVersion
• camunda:in
• camunda:out

camunda:formData
camunda:formField
camunda:validation
camunda:constraint
camunda:value

Its properties should be serialized as attributes, not child elements.

required to implement
bpmn-io/cmmn-js-properties-panel#55

• ErrorEventDefinition

Hey,

starting with Camunda BPM Runtime 7.12.0-alpha4, time-triggered task listeners can be used.

An example configuration looks like this:

...
<bpmn:userTask id="myTask">
  <bpmn:extensionElements>
    <camunda:taskListener delegateExpression="${setBusinessKeyListener}" event="timeout" id="timeout-friendly" >
      <bpmn:timerEventDefinition>
        <bpmn:timeDuration xsi:type="bpmn:tFormalExpression">PT1H</bpmn:timeDuration>
      </bpmn:timerEventDefinition>
    </camunda:taskListener>
  </bpmn:extensionElements>
</bpmn:userTask>
...

Modifications:

1. Value timeout allowed for event attribute of camunda:taskListener
2. Element timerEventDefinition now allowed as a child of camunda:taskListener, but only if the event of the camunda:taskListener is set to timeout
3. New attribute id for camunda:taskListener, only mandatory if event of camunda:taskListener is set to timeout

UI-wise all existing property panel controls for TimerBoundaryEvents can be used here as well for the timer event definition, if the timeout value is chosen as event type of the task listener.

If you have any questions concerning this, let me know! :)

It would be great to have Modeler support for this for Camunda BPM Runtime 7.12 (due November 30, 2019).

Thank you guys,
Tobi

As documented here the default value for camunda:isStartableInTasklist.

We must correctly initialize it in the model.

Example

<StartEvent xmlns="http://www.omg.org/spec/BPMN/20100524/MODEL"
          xmlns:camunda="http://camunda.org/schema/1.0/bpmn"
          camunda:modelerTemplate="bar"
          camunda:modelerTemplateVersion="1" />

Related to camunda/camunda-modeler#1969

AT:

Add taskProperty Attribute

In order to support binding to form files as described in #2295 we need to add new properties to this extension.

New User Task Properties

• camunda:formRef (maps to id property of the form)
• camunda:formRefBinding (latest or version)
• camunda:version (maps to an internal version property set by the engine)

Example

<bpmn:userTask
  id="Activity_1"
  camunda:formRef="formId"
  camunda:formRefBinding="version">
</bpmn:userTask>

or

<bpmn:userTask
  id="Activity_1"
  camunda:formRef="latest">
</bpmn:userTask>

Child of camunda/camunda-modeler#2295

• set default value of CallActivity#camunda:caseRefBinding to 'latest'

Describe the Bug

Hey there! First of all, tnx for your time.

Im facing an issue while trying to add a complex name in the CalledElement on CallActivity section panel.

After doing a saveXML({}) the string from CalledElement itsself converted as a QName.

The problem is that it continuing to convert as a QName when he already is.

Steps to Reproduce

We are doing a tipical form page with the BPMN Modeler and bpmn-js-properties-panel + camunda-bpmn-moddle, without no custom parameters, just with the initial README.md config steps.

When form submit, we execute modeler.saveXML({ format: true });, and keep in our BBDD the XML.
When we reload the page, we fill the Modeler with the XML saved in our BBDD.

• 1
  Fill Called Element with some spaces

and then, execute modeler.saveXML({ format: true });

• 2

Reload the page and fill Modeler with the last XML. We can see that Called Element has serialize itself

Then, execute modeler.saveXML({ format: true }); without no changes.

• 3

Reload the page and fill Modeler with the last XML. We can see that Called Element has serialize itself AGAIN

Then, execute modeler.saveXML({ format: true }); without no changes.

• 4

Reload the page and fill Modeler with the last XML. We can see that Called Element has serialize itself f AGAIN

Expected Behavior

It should not serilize _ to unicode

Environment

Please complete the following information:

• Browser: Chrome Version 89.0.4389.128 (Official Build) (64-bit)
• OS: Windows 10
• Library version:
  • "bpmn-js": "^8.2.0",
  • "bpmn-js-properties-panel": "^0.42.0",
  • "camunda-bpmn-moddle": "^5.0.0",

Since the extension is not returning anything when checking wether a property can be copied it's not working.

• EscalationEventDefinition

• camunda:inputParameter
• camunda:outputParameter
• list
• entry
• map