not sure if this is the right channel - I have a w...
# advancedpdf
d
not sure if this is the right channel - I have a workflow that sends an email on certain types of item changes and can't figure out which fields are available in the email subject/template. I want to say something like "change in `{item.name}`", and
{name}
,
{item.name}
don't work.
r
you might consider doing this as a saved search instead of a workflow. That way you can set it to fire ONLY when a specific field being updated on the transaction form, and then you'll have access to all the fields that are on that transaction no problem. works for us!
@David Stillman
d
Interesting - I haven't played with saved searches in that context yet. How would I set up that search?
r
one example we use it for is drop shipments where we don't have tracking right away, but we start the fulfillment process and fill in details later. This way we set up a saved search that triggers on creation/update, also filtering off the tracking number field, and fires the e-mail to the customer with the pertinent info.
d
Ah, that makes sense - great tip, thanks!
This behavior hinges on the "Email" tab of saved searches, yeah? I'm new to NS still, and saved searches seem to be the life blood of it all...
r
message has been deleted
message has been deleted
crude examples I just created
d
Ah, brilliant! Thanks so much!
r
you're welcome
one word of caution though.... test, Test, TEST! Saved searches don't always go how you think. My boss says "Trust but verify" to everything.
especially with new things, until you get a handle on it. been working with it for a year, and NS still surprises me.
d
Yeah, I hear that. We're coming up on 2 months and it's been... very interesting 🙂 Sales are just starting to get the hang of things, so my desk is quieting down some.
r
well then I'll give you another pro-tip. if you're using this to do fulfillment-type e-mails, restrict the time that they are sent to like once-a-day (after active hours) and have a "Do not send e-mail" custom field (checkbox) on your fulfillments. We've run into an issue where we set it to activate on creation/update, and didn't have filters on, so when someone opened up a fulfillment and added notes (triggering an update event), it re-sent the fulfillment e-mail to the customer. Sometimes a week after it had already shipped. Adding the "Do not send" to the criteria helped a bit, but also the whole "I'm adding internal notes, why is it sending another e-mail to the customer" thing gets old real quick.