Skip to content
IFS Wire

Community · Question

Why workflow user forms in IFS Cloud 25R1 can't take a multi-line email body, and a possible alternative

Asked by IFS Wire DeskEditorial · 1 Nov 2026 · 0 views

Type:
Technical
Product:
IFS Cloud
Version:
25R1

Sourced from IFS Community · original thread · pdollk

0

On IFS Cloud 25R1, a workflow action is launched from the Work Tasks page through a Send Email command. It opens a user form with three inputs: EmailTo, EmailSubject and EMailBody. EMailBody is defined as a String, so it only accepts one line and the email is sent as soon as the user presses Enter. Switching the field type to Text causes the field not to appear at all once the workflow is published. How can the email body be entered as multi-line text?

Technical details IFS Cloud 25R1; Business Process Automation workflow; user form fields EmailTo, EmailSubject, EMailBody; field types String vs Text; bpmn-js-properties-panel 0.46.0 (string, long, boolean, date, enum, Form Text); Page Designer; custom entity; event action; Workflow Trigger by Command; IFS API READ task.

Any attachments are visible to signed-in members.

1 answer

0

✓ Accepted answer

Stated limitation (IFS employee reply, not marked as best answer, not confirmed by the poster):

  • Workflow user forms do not offer a multi-line field. The form editor is based on bpmn-js-properties-panel 0.46.0, which supports only Form Fields of type string, long, boolean, date and enum, plus a plain Form Text element. There is no text area and no Camunda Forms option.

Possible alternative (explicitly an untested idea from the same replier, feasibility not confirmed):

  1. Create a custom entity (for example EmailRequest) and build a custom page for it in Page Designer with fields for email from, email to, subject and a message body set to multiline, plus a Send Email command.
  2. Save the entered details as a record in the custom entity, then start the workflow from an event action on new records, or use the Workflow Trigger by Command method.
  3. Remove the user task that collects the email details from the workflow and keep the remaining tasks (approvals, gateways, service tasks).
  4. If the values do not arrive as workflow inputs, add an IFS API READ task at the start of the workflow to read them from the custom entity.

Prerequisites and limitations Applies to IFS Cloud 25R1 as reported; later releases may change the form editor. The limitation comes from an IFS employee reply but no answer was marked as accepted and the poster did not confirm. The custom entity route is an untested suggestion and needs custom objects plus Page Designer work.

Sourced from IFS Community · original thread · pdollk

Answered by IFS Wire DeskEditorial · 1 Nov 2026