# How to extend Flowable to add "Business Domain" specific BPMN elements

**URL:** <https://forum.flowable.org/t/how-to-extend-flowable-to-add-business-domain-specific-bpmn-elements/679>\
**Category:** Flowable Engine\
**Created:** [June 28, 2017, 5:08pm UTC](https://forum.flowable.org/t/how-to-extend-flowable-to-add-business-domain-specific-bpmn-elements/679 "2017-06-28T17:08:03Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![PascalSchumacher](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.flowable.org/pascalschumacher/32/336_2.png) [@PascalSchumacher](https://forum.flowable.org/u/PascalSchumacher)\
**Post date:** [November 29, 2017, 3:46pm UTC](https://forum.flowable.org/t/how-to-extend-flowable-to-add-business-domain-specific-bpmn-elements/679/6 "2017-11-29T15:46:24Z")

</div>

Thanks for the input.

In case anybody is interested: I managed to build a working prototype with a custom “domain specific” BPMN task based on the service task. To achive this I had to fork the following flowable modules:

- flowable-json-converter (added converter for the custom task, modified existing classes related to service task)
- flowable-process-validation (is is not possible to deploy processes with unknow bpmn elements, therefore ServiceTaskValidator must have knowledge of the custom servicetask type)
- flowable-ui-modeler-logic (stencilset\_bpmn.json: added stencil and propertyPackages for custom bpmn element)
- flowable-ui-modeler-app (use custom flowable-json-converter, flowable-ui-modeler-logic and flowable-process-validation dependencies)
- flowable-engine (ServiceTaskParseHandler must have knowledge of the custom servicetask type, otherwise no behavior is executed)

---

_[View the full topic](https://forum.flowable.org/t/how-to-extend-flowable-to-add-business-domain-specific-bpmn-elements/679)._