Skip to main content
Question

Adding a multi line field in workflow

  • Oct 26, 2026 4:28 PM UTC
  • 3 replies
  • 53 views
Do Gooder (Customer)
Forum|alt.badge.img+1

Hi Team,

We are on IFS cloud 25R1, We are creating a work flow action from work tasks, when you click a Send Email button it opens an input with 3 fields - EmailTo, EmailSubject and EMailBody.

Currently we are using “String” for email body.

The problem we have is that it only allows a single line entry and the moment a user hits enter the email is sent.

We Tried changing the eMail body to “Text” instead of String, but when we publish it the field does not even appear.

 

Do you know how we could get this as a multi line field?

3 replies

Do Gooder (Employee)
Forum|alt.badge.img+5
  • pdollk
  • Do Gooder (Employee)
  • Oct 27, 2026 3:53 AM UTC

Hi ​@Vibhu_Nandakumar ,

As far as I know, you can't get a multiline field in User Forms. bpmn-js-properties-panel 0.46.0 supports only Form Fields (string, long, boolean, date, and enum) and a plain Form Text. It doesn't support a text area or provide a Camunda Forms option.

Do Gooder (Customer)
Forum|alt.badge.img+1

Hi ​@pdollk 

Thanks for the reply. Is there a different way to achieve this? I mean I need a form that can have a multi line field and trigger an email on a button click from the Work Tasks page. Is there a way to use something other than a user form as part of the workflow ?

Do Gooder (Employee)
Forum|alt.badge.img+5
  • pdollk
  • Do Gooder (Employee)
  • Oct 30, 2026 4:55 AM UTC

Hi ​@Vibhu_Nandakumar ,

I'm not sure whether this is possible or practical in your situation, but since this cannot be achieved using the built-in generated form, you could consider using an IFS custom page (Aurena Page) to capture the email details.

 

 

Build a custom Aurena page in Page Designer on a custom entity (for example EmailRequest).

Add these fields:

  • Email From (text)
  • Email To (text)
  • Subject (text)
  • Message body (text field set to multiline)
  • Add a command button (for example “Send Email”).

This replaces the generated Camunda user form, which cannot provide a multiline field or a button.

When the user clicks the button, save the details to a custom entity. Then, you can configure an event action to trigger the workflow when a new record is created in that custom entity.

Alternatively, you can configure the button to trigger the workflow directly using the Workflow Trigger by Command method.

Remove the “Enter email details” user task, since the page now covers it.

Keep all the other tasks (approvals, gateways, service tasks) as they are.

The workflow now starts from the Start Event with the data already available.

If the details don’t arrive as inputs put an IFS API READ task as first task to read the details from the custom entity.

I'm not sure whether this is possible. It's just an idea, and we need to investigate its feasibility.

Terms & ConditionsAccessibility statement