Technical Data Sheet:
Technology: Qflow BPM, back office, and administration portals
Client: OCA S.A.
Service: Business Process Automation
Industry: Financial Services
To explain Qflow’s flexibility as a business process automation tool, let’s look at OCA S.A. as a concrete example. We should highlight the process size, complexity, and criticality in acquiring credit cards, prepaid cards, and loan applications.
Every process needs to be integrated into OCA S.A.’s existing processes and external services including credit policy calculation, security controls, and applicants’ identity validation.
OCA S.A. integrates its Apps into Qflow through services implemented for such communication. From the Qflow Web site, the client’s collaborators, back office branches, and call centers can analyze all request cases that require action.
On the other hand, Qflow’s generated database information is used for market research and retargeting campaigns through email, SMS, and Whatsapp. For this purpose, a SQL Server database with Always On Availability Groups technology with independent read and write replicas allows for heavy read operations without affecting system performance.
The challenge:
The following are the non-functional requirements that the system must meet:
Reliability:
- Availability: Given that the processes executed on the system are critical for the client, its downtime must be minimized to the maximum.
- Fault tolerance: Given the number of external Qflow processes built-in, it must be possible to handle system errors with automatic or manual retries.
- Recovery capacity: It must be possible to recover the data in case of interruption or failure of the system.
Security:
- Confidentiality: A system user can only access the processes, trays, tasks, tools, and sites for which they have permission.
- Integrity: A user can only respond to or modify tasks or parameters for which they have permission.
- Non-repudiation: The answers to tasks and modifications of the system parameters are associated with the user who answered or modified them. The user cannot alter this information.
- Authenticity: Users must authenticate themselves in the system to perform any actions.
Results
The installed solution consists of multiple modular components connected to Qflow. On the one hand, the layer from where the client integrates with Qflow. This layer consists of REST APIs deployed in separate processes that receive the information for further processing.
On the other hand, the administration and maintenance sites. These are MVC sites where the client can view real-time requests coming into the system, their status, and modify configuration parameters.
Finally, the Qflow website, for collaborators to start processes and respond to tasks, and its entire ecosystem, where permissions, organizational charts, and process designs are managed.
First-person testimony
“I see Qflow always present in our day-to-day. It allows us to trace key flows for our business. In addition to this, adaptation to our needs is always quick and the proactivity of the team that develops the tool is super valuable. You can tell they are always looking for the optimization and evolution of the tool.”
Richard Godinho – OCA S.A. Product Manager
You can also go for greater efficiency in your business through process automation.
We are here to help you. Please contact us for more information.