Newbie: An action requiring a follow-up
 

Under a project, I have an action that says, "email SoAndSo" I've emailed her, so that action is complete, but until I hear from her, the action is only partly complete. Should I make a sub-action that says, Emailed: Response?
Got to be a better way. I just can't think of it.

You can create a second task, e.g, “Waiting for reply from [contact] regarding [email subject]” and assign it to a Waiting context. (If you'd like you can make the Waiting context stalled, which will affect what tasks are visible when you use various filters). If you prefer to have these two actions grouped in your project, assign them to an action group.

To automate the process, check out curt.clifton's [URL="http://www.rose-hulman.edu/~clifton/software.html#Await"]Complete and Await Reply script[/URL]. Another option is simplicitybliss' [URL="http://www.simplicityisbliss.com/2009/06/adding-waiting-for-mail-to-omnifocus-by-applescript/"]Add Waiting For emails to OF script[/URL] discussed [URL="http://forums.omnigroup.com/showthread.php?t=12810"]here[/URL].

Thanks!
 

That works great.

[QUOTE=kaijin;66432]You can create a second task, e.g, “Waiting for reply from [contact] regarding [email subject]” and assign it to a Waiting context. (If you'd like you can make the Waiting context stalled, which will affect what tasks are visible when you use various filters). If you prefer to have these two actions grouped in your project, assign them to an action group.

To automate the process, check out curt.clifton's [URL="http://www.rose-hulman.edu/~clifton/software.html#Await"]Complete and Await Reply script[/URL]. Another option is simplicitybliss' [URL="http://www.simplicityisbliss.com/2009/06/adding-waiting-for-mail-to-omnifocus-by-applescript/"]Add Waiting For emails to OF script[/URL] discussed [URL="http://forums.omnigroup.com/showthread.php?t=12810"]here[/URL].[/QUOTE]
Just downloaded mail tag! What a wonderful app. And then the script!

[QUOTE=yennta;66436]Just downloaded mail tag! What a wonderful app. And then the script![/QUOTE]
For the Add Waiting For emails to OF script, you'll also need Mail Act-On since the script functions best with an Outbox rule in Mail.app. There's a workaround without Mail Act-On—I think it's posted as a comment on the developer's page.

Awwww. I've worked on it all day, reloading it, making sure the @Waiting was not a nested context but at the top of the list. I've tried everything, the workaround posted on the developer's page. And then I went and bought mail tag and act on. So, the email is supposed to appear in my @Waiting context list??? It doesn't. It doesn't go anywhere at all. AND Growl doesn't show the script running, failing, nothing.

I'm on an intel mac running 10.5.8 and the latest version of everything.

Confirm that the Mail rule you create is an Outbox rule since the script is triggered when you send the email. Be sure the keyword you enter in the MailTags panel matches what you defined in the Mail rule. Also, the name of the waiting context in the script needs to exactly match the name of the context in OF.

I just installed the script and at first thought it wasn't working. I re-did the installation and script configuration 3 times and still got the same thing.... UNTIL I realized that the email wasn't being directly sent to the OmniFocus @Waiting For context in the perspectives I was looking at, it goes into the "inbox" and I had to give it a project and hit Clean Up first. I wasn't looking there for it initially.

[QUOTE=kaijin;66737]Confirm that the Mail rule you create is an Outbox rule since the script is triggered when you send the email.[/QUOTE]

I'VE TRIED IT EVERY WAY I COULD

CURRENTLY: Okay, it's an Outbox rule, but is it supposed to be listed as an Act On rule? as shown in the first image? "Act On rules.jpg"

And then the Act On rule is invoked in the Outbox as "Act On Waiting" ?

Here is the script (which is in user/library/scripts/Mail/Waiting-for etc.) as I use it: "script.jpg"

Here is a sample mail test.jpg
OF inbox.jpg (nothing there)
Omni Contexts.jpg (nothing there either) AND Growl shows zero. Is not affected.

And, since I can't add any more images, here is a link to the invocation of the rule in both outbox and Act On

[url]http://idisk.me.com/nowsthetime/Public/Pictures/Skitch/Mail-20090913-163304.jpg[/url]

Since that didn't work, I tried: in the outbox, I selected, "apply act on rule" and I chose the Act On Waiting rule. That didn't work either

[QUOTE=yennta;66773]CURRENTLY: Okay, it's an Outbox rule, but is it supposed to be listed as an Act On rule? as shown in the first image? "Act On rules.jpg"[/quote]
No, it should be under Outbox Rules. Select the rule in Act-On Rules, right click, and select Move to Outbox Rules.

[QUOTE=kaijin;66776]No, it should be under Outbox Rules. Select the rule in Act-On Rules, right click, and select Move to Outbox Rules.[/QUOTE]

Tried THAT. Still doesn't work. And I don't understand why Growl has no response, even "failed" ?

[QUOTE=yennta;66773]And then the Act On rule is invoked in the Outbox as "Act On Waiting" ?[/QUOTE]
[QUOTE]Since that didn't work, I tried: in the outbox, I selected, "apply act on rule" and I chose the Act On Waiting rule. That didn't work either[/QUOTE]
The rule (and therefore the script the rule points to) is automatically triggered when you send your email. There is no need to assign it an Act-On keyword. The only reasons you need Act-On for this script is because Act-On creates the Outbox Rules tabe in Mail Preferences > Rules.

Weird thing is when Omni Focus isn't on, sending the mail with the tag and the rules turns it on. But it doesn't do anything else.

[QUOTE=kaijin;66778]The rule (and therefore the script the rule points to) is automatically triggered when you send your email. There is no need to assign it an Act-On keyword. The only reasons you need Act-On for this script is because Act-On creates the Outbox Rules tabe in Mail Preferences > Rules.[/QUOTE]

I didn't give it an act on keyword.

I have no idea why this isn't working, but it just isn't. I've followed your instructions exactly, and it still hasn't worked. Thanks so much for your help. This script is eating up my life. Unless you can think of anything else, I have to give up on it.

Can you post a screenshot of the rule you created, as well as the path for where you placed the rule?

[I][COLOR="DarkRed"]-- EDIT[/COLOR][/I]: Sorry, I missed this information upthread. [COLOR="DarkRed"]--[/COLOR]

The steps you're using seem to be solid and I can't reproduce the issue. A thought: If you've recently downloaded MailTags, you're probably using MailTags 2.3b351 (the build posted on their main site). I reverted to MT 2.2.3, a previous stable build, since I had issues with the beta version. I've not tested this script using 2.3b351 and wonder if this is the issue. I believe another OF user posted a similar issue in the MT forum. If there hasn't been a solution offered in that thread, you can email the MT developer. Perhaps you could send a message a simplictybliss as well.

I'm using 2.3. I'll look at the site and see if I can get an earlier version. I've sent a message to simplicybliss and haven't gotten a response. Thanks for all your help.

Just discovered Clippings in OF. That does pretty much all I need. I can add a "waiting" context to each clip I send over to OF from mail. No rules required.

[QUOTE=yennta;66794]Just discovered Clippings in OF. That does pretty much all I need. I can add a "waiting" context to each clip I send over to OF from mail. No rules required.[/QUOTE]
The Clippings feature is great. It's a shame we can't get the script to work for you, though. It nicely automates the whole process after you hit send.

It's not onerous, however, to do this manually. As you've discovered, just switch to Sent Mail folder in Mail, select your sent message, clip it to OF, and later adjust the task title and context as desired in OF. If you configure Clippings to open QuickEntry, rather than send directly to the OF Inbox, you can streamline some of those steps.

If you come across a solution for the script, please return and share it!

The context that you have in your script and the keyword you have in MailTags is named '@Waiting', while the context you have in OmniFocus is named 'Waiting'. These names must match exactly, so you'll need to remove the '@' from the script and the MailTags keyword, or add the '@' to the name of your OmniFocus context.

Great catch Greg Jones! If yennta changes the context in Omnifocus from@Waiting to Waiting, it should work.

I believe the MailTags keyword can be @Waiting, as long as that is the MT keyword assigned in the Outbox Rule. The MT keyword doesn't have a reference in the script—it only serves as a trigger to run the script. In other words:[LIST][*]The OF context name must match the context name entered in the script[/List]And[List][*]The keyword entered in the MT panel of the outgoing email must match the MT keyword assigned in the Outbox Rule.[/List]But[LIST]All four don't need to match. (It may be less confusing, though, to simply configure all four entries as the same name).[/LIST]

I believe all 4 will need to match. The MailTags keyword is not referenced in the script, but OmniFocus does evaluate imported emails and will assign a task a context based on an exact match with a MailTags keyword. I just tried adding a '@waiting' tagged email using the script and it does not import to OmniFocus. I changed the keyword to 'waiting' and ran the script again and it works.

Greg, this is interesting—I observe different results. My OF context is named 'Waiting' and that is what I designate in the script. I assign '@waiting' as the MT keyword in the Outbox Rule, which is what I use to tag an outgoing email. The script functions fine for me.

The script and rule also run properly when I assign the word 'saxophone' in the Outbox Rule and tag the outgoing email with the same, but have my context named Waiting in OF and the script.

It's my understanding that OF is currently unable to import a MT keyword as a context. (OF can import a MT project, but this script doesn't grab that data). Going from Mail to OF, the context is assigned via the script, not because OF can scan the keyword and match a context. If, for example, I set the MT keyword of an outgoing or received message to 'Errands'—which matches a top-level context in OF—and clip it to the OF Inbox or QE, the task is added, but no context is imported.

Are you observing different behavior?

Mac OS X 10.5.8
OF 1.7.3

[QUOTE=Greg Jones;66839]I just tried adding a '@waiting' tagged email using the script and it does not import to OmniFocus. I changed the keyword to 'waiting' and ran the script again and it works.[/QUOTE]
In your test, did you also change the MT keyword in the Outbox Mail rule to '@waiting'?

[QUOTE=kaijin;66842]It's my understanding that OF is currently unable to import a MT keyword as a context.[/QUOTE]

You are absolutely correct-my mistake. It is keywords that are not mapped to contexts, and I'm always forgetting and getting it wrong. Perhaps because I really want MT keywords mapped to a context! It is curious why the script breaks for me if the MT keyword does not match the context in OF.

[QUOTE=kaijin;66843]In your test, did you also change the MT keyword in the Outbox Mail rule to '@waiting'?[/QUOTE]

Nope, that was what caused it to fail.