I am LOVING the new Custom Task Types and I mean loving them.
It makes sense alongside approvals, tasks and milestones to have specific other styles of tasks with their own status/closure type (it also means having more curated options for certain tasks than needing a custom field with all possible status options).
A use case I have been using with a client was using them as decisions. Having a custom task type that is a decision point. For this example it was if an RFP was required for a project. The options on the task was ‘?’ decision to be made, ‘Required’ or ‘Not Required’ (which completed the task).
We also used rules to say that IF the custom decision task was set to required in that section then it converted that task into a project using the RFP project template. Giving them an easy link to the RFP from inside the project. This could also be done with adding tasks if the decision is small.
I just wanted to share this in case you guys found it useful!
8 Likes
I’m not quite following how this works. How would the statuses get set? Does a person go in and set the status to one of the options, or is that determined by something about the options set on the RFP?
I’m thinking about this in terms of the “decision” nodes in an email marketing platform, where you can insert something in your automation flow that checks, “Was this email opened/clicked on?” and then depending on whether the answer is “yes” or “no,” you go down a different branch of the automation.
I’m not really understanding if that’s what you’re describing here, or if the example of what I’m thinking about is way off track from what this is.
Hi @Rebekah_Chalkley thanks for your reply. So on the task custom task types give you the option instead of a tick, to click a box that gives you the status options (a bit like a single select custom field).
Not sure on ‘Decision nodes’ as i’m not in email marketing but essentially this task status serves as a trigger in rules for actioning another project.
