Skip to main content
Question

Formatting Text in the Description Field of a Decision Task

  • August 12, 2025
  • 2 replies
  • 50 views
vanpej
Do Gooder (Customer)
Forum|alt.badge.img+2

Hello, I’m looking for guidance on how to format text within the Description field of a Decision task using an expression. I’m trying to make a lengthy statement more readable and user-friendly.

Here’s the original version:

“To determine whether you can authorise this Change, you need to assess the required level of approval: If the Change is classified as RFC 4, you can authorise it yourself. RFC 3, it requires approval from a peer. RFC 2, it requires approval from the Services Manager. RFC 1, CAB approval is necessary. If the Change is no longer required, it should be rejected.”

And here’s the revised version I’m aiming for:

“To determine whether you can authorise this Change, you need to assess the required level of approval.

If the Change is classified as:
• RFC 4 – You can authorise it yourself.
• RFC 3 – It requires approval from a peer.
• RFC 2 – It requires approval from the Services Manager.
• RFC 1 – CAB approval is necessary.
• No longer required – It should be rejected.”

Is there a way to achieve this kind of formatting guaidance on using expressions or supported syntax within the platform?

Thanks in advance for your help!

Best regards,
Jessica Lee van Pelt
Service Analyst

J L van Pelt
E

2 replies

R
Sidekick (Customer)
Forum|alt.badge.img+9
  • RobinHunter
  • Sidekick (Customer)
  • August 18, 2025

I’m not sure which filed you are referring to as “Description field of a Decision task” but in IFS Aurena (Apps 10 or Cloud), you can use Page Designer to enable the “Multiline” function on the field in question. After doing so, you’ll get a little “notepad” icon next to the field. Clicking that icon will allow you to enter multiple lines of text into the field (i.e. you can include return/new-line characters).

Here’s an example on the Wage Class Name field (but it will be the same on any IFS Aurena page).

  • Robin
eqbstal
Superhero (Partner)
Forum|alt.badge.img+21
  • eqbstal
  • Superhero (Partner)
  • August 21, 2025

Nice answer of ​@RobinHunter and I want to add to this, that you should perform the change at all places where the field can be updated. Else you might remove unwillingly the formatting when the standard type of the field is used.

And ​@vanpej make sure that you test this thoroughly :-).

Thanks for using the community, it helps me. I hope I can help you.
R
Terms & ConditionsCookie settingsAccessibility statement