# Parameter Mapping from Parent Process to Subprocess

**URL:** <https://discuss.workflowgen.com/t/parameter-mapping-from-parent-process-to-subprocess/738>\
**Category:** Process Design\
**Created:** [March 23, 2017, 3:26pm UTC](https://discuss.workflowgen.com/t/parameter-mapping-from-parent-process-to-subprocess/738 "2017-03-23T15:26:38Z")\
**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:** [May 24, 2017, 6:29pm UTC](https://discuss.workflowgen.com/t/parameter-mapping-from-parent-process-to-subprocess/738/2 "2017-05-24T18:29:37Z")

</div>

For future clients bumping into this issue, here is an article that explains the reason of this issue:

> [@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…

---

_[View the full topic](https://discuss.workflowgen.com/t/parameter-mapping-from-parent-process-to-subprocess/738)._