cancel
Showing results for 
Search instead for 
Did you mean: 

Create a new FormType / FormRenderer outside Explorer, how?

sergiofigueras_
Champ in-the-making
Champ in-the-making
Hi! Smiley Happy

I'm developing an integration between my Vaadin App / Activiti BPM (5.10). In fact, my Application is the one which should renderers my form properties, since I'm not using the Activiti Explorer. In fact, I'm using only the engine dependencies (activiti-engine, activiti-spring).

My requisites is that I need other kind of data in my form, it means: if the modeler of process thinks that in the task he's modeling the executor will need to select a user, or department, for example, he would use something like a "SelectUser" in Type of a form property, and when it shows up to executor, there should be a button with a popup to the executor select the user and attach it to my flow.

I've seen some people talking about extend AbstractFormType, and attach it to activiti-ui-context.xml, but I'm not using the Activiti Explorer itself and I've my own Spring files.

What I need to do?

Regards,
1 REPLY 1

frederikherema1
Star Contributor
Star Contributor
Look at the activiti-sources… The form-rendering of the form-properties is extremely simple. You can easily extract the *FormPropertyRenderer and related classes and use that in your app. To add additional supported types (with your own UI to select e.g.. department), you just plug in an new FormPropertyRenderer.

Another approach would be to just use the StartFormData and TaskFormData you get back from our AOI and inspect the list of FormPropertiy instances and render a UI-element, based on the getType().