The term “Workflow” can mean a lot of things to different people. The QBO Workflow module refers to orchestrating a “flow chart” of activities that tend to happen many many times. Examples include:
Managing the outsourcing of a collections effort by a collection agency
Orchestrating the steps of a foreclosure, bankruptcy, or eviction
Orchestrating the creation, review, approval, and delivery of documents
Evaluation of the value of a piece of real estate, and orchestration of the steps involve in purchasing it
What can a Workflow do? The most common activities include:
Create a task for a user to complete
Generate a document
Copy a document to an investor’s imaging system
Send an email to a vendor
Launch a child workflow
Check an FTP site for files to import
Order and receive a real-time credit report
Order an automate value for a property
Search the Department of Defense for a borrower’s military active duty status
Fetch recent payment information from a servicing system
Post notes, change status codes, or open work stations in a servicing system
More broadly, a workflow can call any operation of any QBO class. If you can do something in QBO via the front-end, you can have a workflow do it.
If you need QBO to do something that it currently cannot do, there’s a bit of IT work involved by Quandis IT — or by your IT department. (We’re happy to consult with you on such things, but you don’t have to be dependent on us!) The QBO IService interface allows the geeks out there to configure QBO – via the web browser – to call pretty much any web service out there.
Most flow charts are not linear, and QBO Workflow does not have to be linear either. Workflows support conditional if/then statements, as well as simple or complex dependencies.
The Workflow dashboard provides a snapshot of all open workflow, and you can drill down into any “bucket” to determine the exact step the workflow is on. From the dashboard you can also: