Is your feature request related to a problem? Please describe
I am writing as my master thesis custom implementation of engine for BPMN processes. As for UI I choose bpmnio. For example I'd like to add a feature, that user defines its own script for bpmn:ScriptTask (via properties panel). I want to support only properties defined by official schema. Unfortunately default BpmnPropertiesProvider seems not to support all properties defined in bpmn-moddle's default schema
Describe the solution you'd like
I wish that BpmnPropertiesPanelModule supported all properties defined in bpmn-moddle's default schema. I don't want to use Camunda provider because it gives access to properties from camunda namespace which I don't want to support.
Describe alternatives you've considered
using Camunda gives an access to bpmn properties, but it gives access to camunda properties as well :(
for now I solved my problem defining my own custom, very provisional provider
Additional context
This feature request comes from topic on bpmnio forum. Implementation would help me in my project and I am assured that in the future somebody can use the feature too.
Correct, we don't support editing each of the properties defined in BPMN. However, we are open to accept contributions. If you implement any of the missing properties entries, feel free to create a pull request.
Is your feature request related to a problem? Please describe I am writing as my master thesis custom implementation of engine for BPMN processes. As for UI I choose bpmnio. For example I'd like to add a feature, that user defines its own script for
bpmn:ScriptTask
(via properties panel). I want to support only properties defined by official schema. Unfortunately default BpmnPropertiesProvider seems not to support all properties defined in bpmn-moddle's default schemaDescribe the solution you'd like I wish that BpmnPropertiesPanelModule supported all properties defined in bpmn-moddle's default schema. I don't want to use Camunda provider because it gives access to properties from camunda namespace which I don't want to support.
Describe alternatives you've considered
Additional context This feature request comes from topic on bpmnio forum. Implementation would help me in my project and I am assured that in the future somebody can use the feature too.