They pass to the task itself, but they show up as the placeholders in the email notificaitons
Just my opinion, but fields are fields, whether built-in or custom, All fields should be available for notifications, filtering, sorting, reporting......it's a database platform it shouldn't make a difference which type of fields are available for which screens or functions.
This is a very logical expectation since this already works effectively for Tasks. That this doesn't extend to Approvals - which are, I think very logically, just a more specific type of "Task" - seems like an oversight from the original enhancement to Task.
This is a massive gap in this product, and the fact that it doesn't already allow you to pull custom fields collected, to put into an approval flow, or as-hoc email is so telling of what Solarwinds ITSM has become. They've focussed on using these fields for their new AI offering, but nothing about the simple integration of using a completed custom field in an ad-hoc email, template or approval.
https://thwack.solarwinds.com/discussion/151280/november-23-release-for-solarwinds-service-desk-gen-ai-process-integrations-and-more#latest
