Rule Triggers: Timing - not based on due date

English Forum Tips and Tricks
, , ,
1

Hi all,

Healthcare industry person here. We have to track multiple certifications, start dates, credentials, etc. All of which have different time-tables.

Is there a rule which can be “triggered” to produce an “action” regarding a date - that is not the date date?

Thanks!

2

Only the Due date can be used as a date-based trigger I’m afraid, @Joe6.

Most of us can do the tracking that way, though. But that won’t work for you?

Thanks,

Larry

3

Thanks Larry - appreciate the reply.

The challenge is we manage multiple dates within the same task (i.e. healthcare provider).

I’ll think about this more and try to better clarify my question.

Essentially, I’m trying to use Asana as a date-based trigger manager for documents and events.

4

You’re welcome, @Joe6.

To work better with Asana, you’d likely want to have one task per notification so you can use the Due date field with each.

To then group all those by healthcare provider you have different options so it would depend on your overall goals/workflow which is beyond the scope of this reply (I help clients with things like this daily with consulting engagements). But consider either one project or one section perh provider. Another option is using a parent task as the provider to group subtasks for each notification (you still get one Due date per subtask) but rules don’t directly work with subtasks in Asana so you could use a workaround (making them parent tasks too in this or another project) or using @Phil_Seeman’s flowsana.net.

Larry

1 Like
5

Thanks, that is good to know on the engagements and already using @Phil_Seeman 's program - looks like a good upgrade to the current Asana based triggers.

Might be a good addition, Phil!

Thanks both!

2 Likes
6

Appears the way to handle this is to have the due-date reset when placed in a new section. Doesn’t allow time-based triggers for various values - which would be nice - but will hope to see in future.