A Baptism by Fire. From jBPM to Camunda-powered Case Management

In 2011, I began what would become one of the most transformative phases of my professional journey. As a software engineer eager to explore BPM automation and BPMSs, I have spent the past decade observing and contributing to continual innovation in this field. This post provides a glimpse into my initial forays into BPM, setting the stage for a series on Case Management and my vision of creating WKS Platform.

Diving Deeper into the PJ-e: A Revolution in the Brazilian Judicial System

My introduction came through the Brazilian PJ-e, a pioneering project for which I served as a Java specialist. Our task was to build it using jBPM. The PJ-e represented a significant shift for the Brazilian government and legal sector, conceived as a digital platform to modernize the judicial system.

The platform aimed to make justice more accessible by reducing time and costs associated with legal proceedings. The vision was that court proceedings could be initiated, tracked, and concluded electronically, eliminating the need for physical presence and paperwork. For the government, it was a step towards modern governance; for the legal community, it marked a new era where technology would play an indispensable role in ensuring swift justice.

However, the ambitious vision came with substantial challenges. The legal field’s myriad intricacies demanded aggressive requirements. Each court, procedure, and administrative process had its own nuances that needed perfect encapsulation within the system.

The nebulous terrain of case management emerged as the most significant roadblock. Even with an exceptionally talented engineering team, merging case management with process automation proved daunting. The inherent ambiguities of legal proceedings, combined with requirements that often lacked clarity, meant constantly pivoting, iterating, and refining our approach.

The Learning Curve

Navigating these challenges, I spent countless hours demystifying the connection between case management requirements and process automation. The PJ-e vividly highlighted the nuances of integrating these two paradigms.

Dynamic Workflow Paths

Legal proceedings don’t follow set templates. Depending on case specifics, evidence presented, or actions of parties involved, procedural steps could vary significantly. BPM required linear processes, while case management needed flexibility. Balancing the two was a daily challenge.

Varied Access Levels & Case Visibility

Legal cases involve various stakeholders, each needing different data at different stages. A judge might require comprehensive case views, while attorneys might need only specific files. Building a system that was both restrictive and liberating where necessary involved constant negotiation between structured BPM environments and adaptive case management.

Bespoke Document Management

While PJ-e had its unique web document editor, digital signing component for PKI, and custom document storage, aligning these with process automation proved intricate. Determining at which stage documents could be edited or signed without disrupting process flow added significant complexity.

Dynamic Task Management & Notifications

Legal scenarios involve responding to dynamic situations. While BPM operates best with preset tasks, case management often requires creating, assigning, or modifying tasks on-the-fly. Integrating dynamic task management in legal cases with a BPM framework, ensuring proper escalation and notification without process breakdown, was a substantial hurdle.

Handling Exception Scenarios

Legal cases feature unique exceptions—unexpected turns of events, sudden case dynamics changes, or unplanned interventions. While BPM thrives on predictability, case management often lives in unpredictability. Designing a system marrying these opposite ends of the spectrum while ensuring seamless flow despite interruptions was challenging.

With each challenge, I learned more about the delicate equilibrium between structured BPM and flexible case management. Each project phase honed my understanding, preparing me for bridging these domains seamlessly.

Beyond jBPM: A Broader Perspective

The PJ-e was just the beginning. As the BPM landscape evolved, I found myself at the intersection of different open-source BPM engines and commercial BPMSs, understanding their intricacies, strengths, and areas for improvement. A recurring theme was companies wrestling with case management, especially when using tools primarily designed for BPM.

Today, I frequently encounter clients eager to understand how to replace platforms like Pega Systems with Camunda. The desire for a comprehensive open-source solution is clearly significant.

Towards an Open-Source Vision

With collective insights from these experiences, I am steering towards a mission: creating an open-source Case Management Platform atop Camunda BPM. It’s an ambitious goal, but one close to my heart.

In subsequent posts, I’ll dive deeper into experiences with different BPMSs and open-source BPM engines, shedding light on shared challenges companies face when wrestling with case management using BPM-centric tools.

Learn more about WKS Platform

Stay tuned on LinkedIn for updates about upcoming blog posts and project news.

To learn more about WKS Platform, follow the project on GitHub at github.com/wkspower/wks-platform and read platform documentation at doc.wkspower.com.