Client Property Field Creates Conditional Work Orders/Work Flows
live!
Ryan Lock
When Project Property = Permit Yes then create Work Order "Submit Permit"
When Project Property = Permit No then don't include work order
Currently we are putting all of the conditional work orders that only come up on x% of jobs for all jobs. It is overwhelming and cluttering the job and tasks for our team.
Max Kazakov
live!
Folks, this is now possible via "Project property updated" Automation Trigger & "Create work order" Action!
K
Keaton Garner
I agree. If we could have an Automation with a Work Order related Trigger that gave a Property related Action, this would be great. Then Ryan would be able to have a Work Order change his Permit Property, which triggers a "Project property updated" automation to create a new work order for him.
Ryan Lock
Keaton Garner I was meaning to use this inversely where if a project property were "YES" then create a specific work order.
We have a 50/50 Permit vs No Permit ratio so half of our jobs have an entirely different workflow. I'm wanting to use this as a "Build a Workflow" feature that would be different for every job based on the nuances.
This is my solve to get around not being able to have multiple workflow data into a smartview, while not overloading one workflow with all of the possible nuanced steps in a project.
K
Keaton Garner
Hey, Ryan! I'm curious, are you guys manually modifying the Permit Project Property? Or is this property modified with an automation?