Workflow Sales Formulas, and Purchase Order Formulas can logically control workflow statuses in Focus 2.0 - They have been setup at the Global level, and flow to the Site and Account levels by default. Explanation of the formulas is below.
"Purchase Order" Workflow Purchase Order Formulas

In the example above, the first line uses the CountCode function
to compare how many returned EDI codes exist that match code 420 (updated by
vendor, it identifies that a given PO has been accepted into the vendor’s
system) The logic dictates that if at least one line item on the PO has code 420, PO Workflow status is set to “PO Accepted”.
The second line uses the CountCode function to compare how
many returned EDI codes exist that match code 430 (updated by vendor, it
identifies that a given PO line item has been put on hold) The logic dictates
that if at least one line item on the PO has code 430, PO Workflow status is set to “On
Hold”.
The third line uses the CountCode function to compare if
returned EDI codes exist that match code 440 (updated by vendor, it identifies
that a given PO line is in production) AND the count of those codes equals the
number of line items. The logic dictates that if ALL line items on the PO have
code 440, PO Workflow status is set to “PO in Production”.
The fourth line uses the CountCode function to compare if
returned EDI codes exist that match code 460 (updated by vendor, it identifies
that a given PO line item has been shipped) AND the count of those codes equals
the number of line items. The logic dictates that if ALL line items on the PO have
code 460, PO Workflow status is set to “Shipped”.
"In Production" Workflow Sale Formulas

In the example above, the first line uses the CountCode
function to compare how many returned EDI codes exist that match code 390
(updated by OOP, it identifies that a given PO not been sent by OOP) The logic
dictates that if at least one line item on the PO has code 390, In Production Workflow status is set
to “PO Not Sent”.
The second line uses the CountCode function to compare how
many returned EDI codes exist that match code 420 (updated by vendor, it
identifies that a given PO line item has been accepted into the vendor’s
system). The logic dictates that if at least one line item on the PO has code 420, In Production Workflow status is set to “Partially Ordered”.
The third line uses the CountCode function to compare if
returned EDI codes exist that match code 420 (updated by vendor, it identifies
that a given PO line item has been accepted into the vendor’s system) AND the
count of those codes equals the number of line items. The logic dictates that if ALL line items on all PO’s have code 420, In Production Workflow status is set to “Ordered”.
The fourth line uses the CountStatus function to compare if
any PO associated with the SALE has a status of either “Partially Received” OR
“Received”, The In Production Workflow status is set to “Partially Received”.
The fifth line uses the CountStatus function to compare if
the number of PO’s associated with the SALE
having a status of “PO Received” is equal to the number of PO’s. If TRUE, the In Production Workflow status is set to
“PO Received”.