nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Activiti 6 UI: What is the connection between Form properties & Referenced Form

fluidnotions

I understand that process variables are from form properties by default.
I can't see how to connect the form input fields to defined form properties in a start event.

The only way I can get a form to appear on the start of a process application run is if I click the referenced form field in the process editor and the Form reference pop up window appears where I can create a new form which is then attached to the start event.

However I want the form input values to then be available as variables in the process (which are later used by a camel task - which is kinda irrelevant t to the question)

The form properties seem to be entirely separate from the referenced form. Even if I make the id's the same, the text input I place in the form is not contained in the process variables. I've stepped through the Camel behaviour code in a debugger and there just aren't any variables to add to the camel message body.

A clue on how this should work would be helpful in my reverse engineering efforts.

Find more posts tagged with

Comments

maudrid

I'm having a similar issue.
I took a very simple process from the latest stable version of Activiti that only uses form properties and imported it into Activiti 6.
When I start the process or when a user task with form properties are displayed, the inputs do not show up. On the previous version the inputs do show up.
After creating a form and adding it to the referenced form properties of the start and the user task, the inputs show up again, but it seems like form properties on their own are not yet working in Activiti 6.

fluidnotions

When you say the inputs do show up …. where do you mean? I'm just wondering if we are talking about the same thing here.
What is the difference in function between form properties and referenced form …. how are they usually linked. The referenced form seems to be the visual representation of the form and form properties seem to be the description of fields in the form. From the test cases I can see that bpm20 defined form fields are put into the process instance variable context by default, but I don't see how the FormProcessingServiceImpl which correctly collects input fields places them into process instance variable context.

maudrid

In Activity 5 there was no such thing as a referenced form.
You can just fill in the form properties and the form is generated for the user.
Now they have added the referenced form in activiti 6. You then use the new form designer and you can reuse the same from on multiple user tasks, just by setting the reference to an existing form.
I suspect that you should be able to use both ways now. What I mean is that it should be backwards compatible with activiti 5. The old way should work or you should be able to switch to the new functionality.
But what I am experiencing is that the way you used to do it in activiti 5 is not working anymore.

yvoswillens

That is correct. In Activiti6 UI a new way of creating and referring to forms was introduced. This means that the forms are no longer necessarily part of the process definition lifecycle. Like it was when using form properties.

Generating forms based on form properties is no longer supported in Activiti6 UI.
Using the Form Builder and referencing the created form in the process start or user task is the way to go in Activiti6 UI.

(The form field values will of course be available as process instance variables during execution)

We're open for PR's containing form properties based form generation!

Regards,

Yvo

piyush_wadhwani

the problem when process with form is started in activiti 6 is creating a new task and is assigned to user , so user has to go to click task and then fill the form instead of gathering information there itself

jbarrez

Not sure I'm following what you're saying here … that behaviour fully depends on how you define the process, no?

aliraza521

I am facing similar issue,can you please post the resolution????

hai_nv3

I have same issue, I want to set default value to the form field like expression but I do not know where and how to do that??? Can anyone please show me how?