# Is a more elaborate form designer on the roadmap? **URL:** \ **Category:** Flowable Engine\ **Created:** [September 28, 2017, 6:22pm UTC](https://forum.flowable.org/t/is-a-more-elaborate-form-designer-on-the-roadmap/1009 "2017-09-28T18:22:38Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![jpotts](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.flowable.org/jpotts/32/32_2.png) [@jpotts](https://forum.flowable.org/u/jpotts)\ **Post date:** [September 28, 2017, 6:22pm UTC](https://forum.flowable.org/t/is-a-more-elaborate-form-designer-on-the-roadmap/1009/1 "2017-09-28T18:22:39Z")
Currently, when you design a form for a process the form is limited to one property after another. This is perfectly fine for cases where you need a handful of properties for a task. But there are obviously use cases where users have much more elaborate form requirements. Is there a plan to include a more elaborate form designer in the product? Or is the intent to push complicated forms out to external renderers? ---
**Author:** ![PHH](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.flowable.org/phh/32/94_2.png) [@PHH](https://forum.flowable.org/u/PHH)\ **Post date:** [September 28, 2017, 8:37pm UTC](https://forum.flowable.org/t/is-a-more-elaborate-form-designer-on-the-roadmap/1009/2 "2017-09-28T20:37:17Z")
Hi Jeff, We’re planning to separate the advanced modeling from the enterprise edoras one product and make it available (plus forms runtime) as a non-open source extension that runs against the open source libraries. However, we’re not going to stop any open source contributions for more complex forms. We have to fund our developers, as you know 🙂 Our thoughts are to make the design & forms runtime available free for development. We’re still working through what’s possible. Regards Paul. ---
**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:** [February 14, 2020, 1:24pm UTC](https://forum.flowable.org/t/is-a-more-elaborate-form-designer-on-the-roadmap/1009/3 "2020-02-14T13:24:27Z")
Hello @jpotts Have you developed something for this? ---
**Author:** ![jpotts](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.flowable.org/jpotts/32/32_2.png) [@jpotts](https://forum.flowable.org/u/jpotts)\ **Post date:** [February 22, 2020, 1:01am UTC](https://forum.flowable.org/t/is-a-more-elaborate-form-designer-on-the-roadmap/1009/4 "2020-02-22T01:01:32Z")
Hi Douglas, no, I haven’t, was just curious. ---
**Author:** ![Robinyo](https://avatars.discourse-cdn.com/v4/letter/r/dec6dc/32.png) [@Robinyo](https://forum.flowable.org/u/Robinyo)\ **Post date:** [February 22, 2020, 6:55am UTC](https://forum.flowable.org/t/is-a-more-elaborate-form-designer-on-the-roadmap/1009/5 "2020-02-22T06:55:30Z")
> [@jpotts](#): > > But there are obviously use cases where users have much more elaborate form requirements. You can use a tasks’s [formKey](https://robferguson.org/blog/2019/01/03/flowable-rest-api-part-3/) to take advantage of one of the open source [dynamic forms libraries](https://github.com/Robinyo/serendipity/tree/master/projects/dynamic-forms): ![image](https://canada1.discourse-cdn.com/flex035/uploads/flowable/original/2X/2/235b112b96eec20d1877e86ebf6bf6f8c1a32c39.png) ---
**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:** [February 24, 2020, 2:14pm UTC](https://forum.flowable.org/t/is-a-more-elaborate-form-designer-on-the-roadmap/1009/6 "2020-02-24T14:14:17Z")
Hello. Thank you for the input, but if I understood it correctly, that form library would require a custom app, angular based, right? It is not something we could use with the default Flowable’s task app (angularjs). ---
**Author:** ![Robinyo](https://avatars.discourse-cdn.com/v4/letter/r/dec6dc/32.png) [@Robinyo](https://forum.flowable.org/u/Robinyo)\ **Post date:** [February 24, 2020, 10:14pm UTC](https://forum.flowable.org/t/is-a-more-elaborate-form-designer-on-the-roadmap/1009/7 "2020-02-24T22:14:37Z")
If you want some additional functionality that is not available via the open source Flowable UI Web Applications (implemented in AngularJS) then you would need to add that functionality (configuration/customisation) to them. I am most familiar with Angular, hence, the link to some Angular-based open source dynamic form libraries. **Note:** Angular will soon be moving to [Material Components for the Web](https://github.com/material-components/material-components-web) (MDC Web). ---
**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:** [February 25, 2020, 7:11pm UTC](https://forum.flowable.org/t/is-a-more-elaborate-form-designer-on-the-roadmap/1009/8 "2020-02-25T19:11:29Z")
I have just found an interesting dynamic forms framework for AngularJS. [http://angular-formly.com/#!/](http://angular-formly.com/#!/) It is marked as unmaintained, but still, interesting. ---
**Author:** ![Robinyo](https://avatars.discourse-cdn.com/v4/letter/r/dec6dc/32.png) [@Robinyo](https://forum.flowable.org/u/Robinyo)\ **Post date:** [February 25, 2020, 9:43pm UTC](https://forum.flowable.org/t/is-a-more-elaborate-form-designer-on-the-roadmap/1009/9 "2020-02-25T21:43:28Z")
I think most people have moved on from AngularJS (JavaScript) to Angular (TypeScript). > In January 2018, a schedule was announced for phasing-out **AngularJS** : after releasing 1.7. 0, the active development on **AngularJS** will continue till June 30, 2018. Afterwards, 1.7 will be supported till June 30, 2021 as long-term support.