The Automated Workflow Engine or "A.W.E" is designed to make your day to day life easier and less stressful by setting up workflow rules that will trigger under certain events. Load statuses, check calls, driver updates, credit hold and a plethora of other options will exist for you to be able to setup.
First where can you find the Automated Workflow Engine options?
Find the "Settings" menu option on the left-hand blue menu and click on the tab.
You will be taken to your AscendTMS settings area.
In the Settings menu, under "Company Settings" you will see the option for "Automated Workflow Engine".
Click the Automated Workflow option and set up your new workflow rules.
To create a new rule simply click the...
Load Status Changed Based On Check Calls
The first rule you will come across is setting Load/Truck statuses based on a check call.
This means any time you or a member of your team make a check call, the load or truck status will change automatically based on the check call type that was logged.
For the example above, when you log a check call and select "Arrived at pick up" the load status will change to "In Transit" and your truck status will change to "At Pick up".
Notice this rule also has an "At the stop type" option as well.
For the rule we have set here, "Apply to All Check Calls" is selected. This means the rule will trigger every time you log a check call at a pick up location.
You can also choose from the additional rule options above. For instance, if you have built a load with 2 loading locations and 1 delivery location and you wanted the rule to trigger on the first pick up check call but not the second, you would choose the "First Pickup" option.
Carrier Assigned/Removed/Replaced On A Load
The next rule is setting load/ truck statuses when a carrier is assigned/removed/replaced on a load.
Again, click the blue button to create a new rule.
In this example, when the carrier is assigned to the load the load status will change to "Carrier Assigned" and the truck status will change to "At Prior Load".
When the carrier is replaced on a load, the load status is changed to "Needs Driver" and the truck status is changed to "Dispatched".
When the carrier is removed from the load, the load status will change to "ATTENTION" and we don't have truck status selected so it would stay the same as it was.
Prevent Carrier From Being Assigned To A Load.
This rule will allow you to block a carrier from being placed on a load if one of the following parameters apply:
"Do Not Load" status is set to "Do Not Load"
"Do Not Load" status is not set to "OK to Load"
Primary insurance has not been entered in the carrier profile
Primary insurance has expired
Cargo insurance has not been entered in the carrier profile
Cargo insurance has expired
Preventing Load Statuses Being Set Based On Load Financials.
You can set up a rule that can prevent certain load statuses from being set based off the load's income or expenses.
A good example of this would be before you are sending a load to Accounting Management, you maybe want to set the load status to "To be Billed" or "Completed".
This example would prevent the load status from being changed to either one of those load statuses if the total income was equal to zero.
Preventing A Customer From Being Added To A Load Based On Credit Hold.
In AscendTMS you can place your customers on a credit hold if they are over their credit limit. This rule would allow you to block a customer from being assigned to a load if the customer credit hold is enabled.
Set Load Status When "No Activity" Occurs On A Load For A Specified Period Of Time.
This rule will trigger a load status update if a load has had no activity for a certain amount of time set by you.
Note: "Activity" on a load is anything that updates the "Last Contact" column in the load list. This includes check calls, tracking message responses and Ascend Portal updates.
This example shows after 1 hour of no "Activity" the load status will change to "ATTENTION" but only if the load status was in "Booked - Awaiting Call".
The second part of this rule is REQUIRED because not every load will be impacted. Only the load statuses that may be time sensitive will update.