|
Q-flows approach to Process design has been inspired by the natural way in which people conceive and mold business processes.
Thus, Q-flow quickly integrates itself to the organization, optimizing the performance of its employees and their learning curve.
Q-flow’s design tools allow you to graphically define the company process that is to be automated, expressing it in the form of generic tasks through the use of questions, notifications, evaluations of conditions that may modify the process’ course, control points and finish points, among other elements.
They allow you, furthermore, to define roles, such as “Reviewer” or “Authorizer”, so that processes do not have to directly reference the users who will execute the tasks, but rather may reference roles whose players can be determined at the time the workflow is started. It is also possible to define the user who will perform a role by means of some process relationship. Examples: the user who started the started the workflow, the user who manages the process.
In addition to the basic steps, Q-flow includes advanced steps that users with basic computer knowledge can add to the process models. These steps are not interactive, since their execution does not involve human participation, but rather execute automatic operations:
- Code: allows C# code to be written. Q-flow compiles this code and executes it when the workflow reaches one of these steps.
- Office: handles Office 2003 and 2007 documents.
- XML: handles XML documents and can apply changes to them.
- Web services: interacts with web services.
- Integration: executes operations that have been defined to operate with the organization’s applications (web services, databases, ERPs, etc).
These steps make it possible to interact with external systems, thus taking advantage of the company’s existing systems. It also allows the construction of intelligent processes that include, for example, special calculations and complex operations.
Q-flow can interact with systems that implement interfaces in any of the following technologies:
- COM Components
- Web services
- Enterprise Services (MTS)
- .Net Assemblies
- Databases (OleDB o ADO.NET)
For the interactive steps, in which people participate, it is possible to define priorities, audit levels, and actions that are automatically triggered to prevent delays and other deviations from the desired performance, and to control expirations. The possible actions are:
- Send alerts
- Send reminders
- Delegate the task to another person who is in better condition to carry it out within the stipulated timeframe
- Modify the process trajectory once a certain amount of time has passed.
|