On 12 May 2026, FlowCentric welcomed customers and partners to Waterkloof Country Club for the official launch of FlowCentric Processware v6.0, the next generation of its enterprise business process management platform.
The afternoon event brought together long-standing customers, implementation partners, product specialists, and senior FlowCentric team members for a focused look at the future of the platform.
Denis Bensch, CIO of FlowCentric, opened the launch by welcoming guests and reflecting on the evolution of FlowCentric Processware. His presentation placed v6.0 in its broader product context: not only as a major technology milestone, but as the foundation for how the platform will continue to evolve.
FlowCentric Processware v6.0 has been designed as the platform of the future.
For FlowCentric, this means more than introducing a new look and feel. The new version represents a significant renewal of the platform architecture, user interfaces, administration tools, design environment, deployment model, and integration approach.
Bensch explained that previous major versions of FlowCentric Processware had provided a strong foundation for customers and partners, but that FlowCentric wanted v6.0 to address a broader technology shift. The goal was to modernise the platform while preserving the core process concepts and compatibility that existing customers rely on.
That balance is important. Enterprise software rarely operates in isolation. It supports established processes, integrations, business rules, approvals, reporting requirements, and governance structures. Replacing all of that simply to modernise the underlying platform is not practical for most large organisations.
FlowCentric Processware v6.0 has therefore been built around continuity and change: continuity in the core process principles that customers know, and change in the architecture, interfaces, deployment options, and extensibility required for the next phase of enterprise process automation.
One of the central themes of the launch was deployment flexibility.
FlowCentric Processware has a long history in on-site enterprise environments. With v6.0, FlowCentric has expanded that foundation by designing the platform to support both on-site and Azure-based deployment models.
This matters because many enterprise customers still operate complex, integrated environments where core systems, including ERP platforms, may remain on site. At the same time, more organisations are moving selected systems, services, and integration layers into the cloud.
FlowCentric Processware v6.0 is designed to support this transition by allowing processes to operate across both deployment models. The intent is to give customers flexibility as their technology environments evolve, without forcing a disruptive shift before the business is ready.
The move to cloud readiness has also influenced the platform’s tooling. Previous Windows-based tools have been replaced or reworked as web-based applications, with the exception of the migration tool used during upgrades. The Navigator, Administration Console, and Designer are now web-based, supporting a more modern and accessible working environment.
FlowCentric Processware v6.0 has been developed with several audiences in mind: end users, administrators, process designers, and developers.
For end users, the redesigned Navigator focuses on personalisation and ease of use. Users can configure aspects of their working environment, including appearance, menu placement, landing page, task-card layout, and preferred ways to start processes. The Navigator also supports configurable dashboards, calendar views, favourite tasks, reports, and task views that help users access the work that matters to them.
The intent is straightforward: different users work in different ways. A manager who wants visibility across reports may need a different starting point from a user who spends most of the day completing pending tasks. FlowCentric Processware v6.0 gives users more control over that experience.
For administrators, the new Administration Console brings several administrative functions into one web-based environment. The console supports user and licence visibility, system role views, local event logging, company configuration, user management, user templates, organisational units, runtime controls, participant assignment, notifications, events, and deployment functionality.
This is especially relevant for large enterprises, where user management can become complex as teams, departments, roles, and reporting structures change. Features such as user creation templates, filters, organisational units, and multi-select editing are designed to help administrators manage larger user bases more consistently.
For process designers, FlowCentric Processware v6.0 introduces a dedicated Designer application. The Designer supports process creation, participant management, task design, and interface-related configuration such as task icons. These capabilities reduce the need for certain back-end changes and make selected design updates easier to manage through the product interface.
The Designer application is still being actively developed, with future work including a WYSIWYG task form designer. This direction reflects a broader product focus: giving teams better tools to design and maintain process experiences without losing the control required in enterprise environments.
For developers, FlowCentric Processware remains a platform for building business-specific process solutions. Bensch was clear that the platform is designed for non-trivial enterprise processes: the kinds of workflows that often include complex rules, integrations, approvals, data requirements, and governance obligations.
Rather than treating configuration alone as the answer to every business process challenge, FlowCentric continues to support a development-led model for business rules and complex process logic. This is central to how the platform supports organisations whose workflows cannot be reduced to simple, generic task routing.
Another major theme of the launch was extensibility.
FlowCentric Processware v6.0 continues to strengthen the platform’s ability to connect with other systems, services, and tools. The platform’s facade, introduced in an earlier version as a REST API for initiating and interacting with processes, remains an important part of the product’s direction.
In v6.0, this integration-first approach is extended through new and enhanced event mechanisms. On-site environments continue to support email, file, and time-based events, with additional support for JSON files and Cron-based timing. For cloud-hosted environments, HTTP events allow external systems and developers to start or continue processes through API-based interaction.
This approach is significant because enterprise process automation often depends on more than one system. Processes may need to interact with ERP systems, cloud services, data sources, communication tools, integration platforms, mobile applications, or other front ends.
FlowCentric’s position is that the process engine remains the centre of value. The front end may vary depending on the business case, but the controlled execution of the business process, including its rules, data, handovers, and governance, remains the core of the platform.
The launch also addressed artificial intelligence, but in a measured way.
Rather than positioning AI as a blanket replacement for process logic, FlowCentric presented it as a capability that can be integrated where it makes practical business sense. This is an important distinction.
Bensch noted that AI can be useful for tasks such as interpreting text, classifying requests, supporting voice-based input, translating information, and helping developers work more efficiently. In one example discussed during the presentation, a helpdesk-style request could be passed to an external AI service to help classify the issue and suggest a priority before continuing through the process.
The broader message was clear: FlowCentric Processware does not need to become an “AI product” to support AI-enabled use cases. Its value lies in providing the process foundation that allows AI to be used where it adds practical value.
As an extensible development platform, Processware can connect to AI in several ways: through technologies such as MCP servers, through calls to external AI APIs, and through the structured process data it creates. That data can help AI services provide useful recommendations, such as suggested delivery dates based on historical activity.
In this model, AI supports the process. It does not replace the governance, control, and accountability that enterprise processes require.
For enterprise environments, this is a more credible approach than applying AI indiscriminately. Core business processes often require consistency, auditability, rule-based control, and clear accountability. AI can support those processes, but it should not replace the governance that makes them reliable.
FlowCentric Processware v6.0 has also been designed with the future upgrade path in mind.
Bensch explained that one of the lessons from earlier major version upgrades was the need to reduce the burden placed on customers and partners when moving from one version to another. While major platform upgrades can introduce important capabilities, they can also require significant services, testing, and validation effort.
FlowCentric’s strategy for v6.0 is to shift towards annual mini releases that introduce new features, updates, and enhancements. The goal is to support continuous improvement while reducing the disruption often associated with major version changes.
This does not remove the need for testing, particularly where updates affect security, critical behaviour, or customer-specific configurations. However, the direction is clear: FlowCentric Processware v6.0 is intended to provide a long-term platform base, with regular enhancements rather than repeated large-scale platform replacements.
The official launch of FlowCentric Processware v6.0 marked an important moment for FlowCentric, its customers, and its partners.
The platform has been modernised for a changing enterprise technology environment, but its core purpose remains consistent: helping organisations digitalise, automate, manage, and optimise complex business processes.
For customers, the significance of v6.0 lies in the combination of continuity and progress. Existing process thinking remains relevant. Backward compatibility remains a design priority. At the same time, the platform now offers modernised interfaces, stronger administration tools, improved deployment flexibility, expanded integration options, and a product roadmap designed for ongoing evolution.
FlowCentric Processware v6.0 is not simply the next version of the platform. It is the foundation for the next phase of enterprise process automation.