TOKEN() equivalent function within the string utilities list

[Kelvin]

Following a forum discussion 

Please can I raise the idea to have a TOKEN() equivalent function within the string utilities list in a business flow, this would allow further manipulation of an email into custom field for future use.

Use case
We have an old system that send out an email on completion of a task, this email contain 5 lines with outputs of a process, I would like to auto log a ticket and capture each line into a separate custom field which I can them base decision from.

[Steve Giller]

23 minutes ago, Kelvin said:

I would like to auto log a ticket and capture each line into a separate custom field

The TOKEN() function matches (rather than extracts) so would not be suitable for achieving that goal. It is similar to Regex Substring in that regard.
Also, TOKEN() matches individual words on a line, not complete lines or multiple words, so I don't think that would help you either.

Matching a line, or a portion of a line requires the Regex Substring Task from the String Utilities.