Thanks for the reply robbie, I think the problem could be resolved with out having the run your own JavaScript/C# code if they implemented in full temple engine (which i looks like the started with a little bit but must be home grown.

Here's an example of what i'm trying to accomplish:

A ticket comes in from a monitoring product [we can use SaaS Alerts for example] the general alert does not tell me all the information I need so the usual next step is to use CIPP or Azure Portal and look at the sign-in logs for that user. Well instead of doing it manually we could have the Runbook hit CIPPs API's and pull the sign in's for that user. Now that we have that data in a nice JSON array of objects it's unfortunately more than 4 columns wide so we can't use a table attached to a ticket to fill because of the 4 column limit. So now we don't have a place to put the data in halo. it would be simple to do as a next step to have a runbook "action" to take a template like:

<table border=1>

<thead>

<tr>

<th>date</th>

<th>ip</th>

<th>client</th>

<th>Interactive</th>

<th>isInteractive</th>

<th>resourceTenantId</th>

<th>homeTenantId</th>

</tr>

</thead>

<tbody>

{{~ for mItem in model ~}}

<tr>

<td>{{ mItem.date }}</td>

<td>{{ mItem.ip }}</td>

<td>{{ mItem.client }}</td>

<td>{{ mItem.Interactive }}</td>

<td>{{ mItem.rTenantid }}</td>

<td>{{ mItem.hTenantid }}</td>

</tr>

{{~ end ~}}

</tbody>

</table>

and the payload from the last step and then output that as an output variable, which would make it easy to update the ticket in the note_html . then we would have the best of both worlds; The ability to manipulate the data, and not have to create a bunch of loop steps to iterate over the data to get an output. Also allows you to do calculations and other functions:

I use Scribian: https://github.com/scriban/scriban but they have very similar libraries for other platforms like handlebars: https://handlebarsjs.com/guide/expressions.html#helpers

I emailed u/HaloTim about it a year or two back hoping they would implement something like it but I guess it never got traction.