Maybe  SM_ACTIONING_USR_N]?

 

It depends when the template applies. Action templates are typically used in assystWeb to populate the template for an action based on the current values of the event before the action is taken. They can’t use values from the action itself because the action has not yet been taken (if that makes sense)?  

For example the syntax would be $new.actionedBy.name for actioning user, or $new.event.assignedUser.name for the assigned user, however both of those values are only populated after the action is taken.

If you need this sort of feature I’d recommend suggesting it in the Ideas forum 

   

Could we pulled Assigned User from the parent event for the action instead?

You could - though again that would be assignment before the action is taken. If the action itself is assign (or there’s any workflow that performs an assignment on the back of that action) the outcome may not be what you are looking for. If the action doesn’t reassign that will work (syntax as above)

ok, that would work for our purposes I believe - however the syntax you’ve given doesn’t match the style used in Action Templates which is more of the tEVENT_AFFECTED_USER_NAME] style syntax

We’ve been using this without issue in our templates to pull in the actioning user as well as in others their phone number, email etc. via Extended Keyword Notation functionality.

Thank you, 
ACTIONINGUSER]
 

Etc

Thank you @moconnor1 that is the key piece of information I was missing. Much appreciated.