# Modular Workflows

**URL:** <https://discuss.workflowgen.com/t/modular-workflows/836>\
**Category:** Workflow Designer\
**Created:** [August 4, 2017, 8:05pm UTC](https://discuss.workflowgen.com/t/modular-workflows/836 "2017-08-04T20:05:20Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![eddy.daouk](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.workflowgen.com/eddy.daouk/32/672_2.png) [@eddy.daouk](https://discuss.workflowgen.com/u/eddy.daouk)\
**Post date:** [August 7, 2017, 2:30pm UTC](https://discuss.workflowgen.com/t/modular-workflows/836/2 "2017-08-07T14:30:36Z")

</div>

Hi Steven,

This really depends on the design of your process. But using subprocesses for example will handle this situation. You would only have to change the subprocess once and all the parent processes will have that change:

> [@Workflow Design: Subprocess versioning management](https://discuss.workflowgen.com/t/workflow-design-subprocess-versioning-management/395):
>
> Default By default, the WorkflowGen engine automatically uses the last active sub-process version or, if there is no active version, the last “in test” version. This is a flexible solution because when you modify or update a sub-process, you know that all parent processes will call the new version. Incompatible sub-process parameters If your new sub-process version is no longer compatible with the parent processes (for example, due to parameter changes), one solution is to create a new sub-proc…

Best Regards,  
Eddy.

---

_[View the full topic](https://discuss.workflowgen.com/t/modular-workflows/836)._