I'm attempting to generate audit events that track changes to a specific
multi-valued attribute. I would like the custom event to contain the
value of the attribute in the destination store. I am able to track this
by setting one of the TEXT fields to Destination Attribute("myAttr").
However, this only logs the first value in the attribute.
Looking at the help text in Designer, I suspect I'm running into the
difference between using the Destination Attribute token in string context
as opposed to node context. Can anyone tell me how to use Destination
Attribute in node context, in order to join all the values of an attribute
into a string that I can include in the custom Audit event?