Automation - new item created status

Question

Hi everyone!

I'm exploring automations more and have set up an automation which is triggered by selecting a specific custom field.  Once the custom field is selected a new task is added to the project.  The only problem is the task is set as the default workflow rather than the workflow that has been set for that folder and the rest of the tasks in that project.  Is there anyway to set this up so the task will use the workflow that we want?  I tried setting up another automation for any new items created in that folder but I am guessing automations don't work on items that have been created using an automation?

Amy Hunter · Answer

Hi @Sherrie Besecker the original project is being created upon submission of a request form from a blueprint.  Then once the brief is assessed a custom field is selected to determine what category of job it is (green, orange or red).  If red or orange is selected then certain tasks need to be added to the project.  This is where I have set up the automation triggered by the custom field selection.  So this happens AFTER the request form is submitted.  For some reason the extra tasks added upon the automation use a different workflow status.  I think we will need to just manually change the status once the automation creates the task.  Anyways thank you so much for chatting this through with me 😊

Sherrie Besecker · Answer

@Amy Hunter Ahhh - I am not 100% sure of your set up without seeing it - but if you have a RF —and you are doing this: "Once the custom field is selected a new task is added to the project" - (it sounds like you are "adding subtask (to project via RF)) - add subtask (from blueprint) - you can prob just create the blueprint task itself instead of CIT if needed.  In the blueprint - change the status to what you need (or tag with CF too if needed).

Amy Hunter · Answer

Thanks @Sherrie Besecker I hadn't thought to do a CIT.  Will this still be suitable since the rest of the project will be normal tasks?  I tried creating a blueprint from the autmation but because I am doing this with a project that has already been created (off the back of a request form submission) if I created a blueprint with the automation it would become a subproject and I don't want that.