# Flowable task app and sub-processes **URL:** \ **Category:** Flowable Application\ **Created:** [May 13, 2020, 12:27am UTC](https://forum.flowable.org/t/flowable-task-app-and-sub-processes/6008 "2020-05-13T00:27:27Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![douglascrp](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.flowable.org/douglascrp/32/306_2.png) [@douglascrp](https://forum.flowable.org/u/douglascrp)\ **Post date:** [May 13, 2020, 12:27am UTC](https://forum.flowable.org/t/flowable-task-app-and-sub-processes/6008/1 "2020-05-13T00:27:27Z")
Hello. I am working on this process definition, which is composed of a main process and a sub-process that is created by the main process when the execution reaches a point in time. As I created an application containing both main and subprocess models, when I deploy it, flowable-task is showing both models for the user when he is starting a new instance, but I would like to avoid him to start this subprocess, and it should be started by flowable. The user should start only the main process. How could I avoid having this subprocess present in the new instance action inside flowable-task? Thank you. ---
**Author:** ![joram](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.flowable.org/joram/32/26_2.png) [@joram](https://forum.flowable.org/u/joram)\ **Post date:** [May 18, 2020, 8:26pm UTC](https://forum.flowable.org/t/flowable-task-app-and-sub-processes/6008/2 "2020-05-18T20:26:41Z")
The Java and REST api’s support the `startableByUser` parameter., which can be used for this purpose (the sub process would not have this property configured). However, I don’t think flowable-task uses this API. ---
**Author:** ![douglascrp](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.flowable.org/douglascrp/32/306_2.png) [@douglascrp](https://forum.flowable.org/u/douglascrp)\ **Post date:** [May 19, 2020, 12:19pm UTC](https://forum.flowable.org/t/flowable-task-app-and-sub-processes/6008/3 "2020-05-19T12:19:10Z")
Ok. I will check that. Thank you.