BPMN Diagram Import Feature in the .NET Workflow Engine Library by Optimajet

Optimajet Limited - Sep 3 - - Dev Community

Introduction

We are excited to announce a new feature that will be available in one of the upcoming releases of Optimajet Workflow Engine — BPMN diagram import. This feature is designed to significantly simplify and accelerate the process of creating and configuring business processes for .NET Developers. What’s even more important, it is a unique offering in the market of on-premise .NET libraries.

We are starting extensive testing of BPMN diagram import among Optimajet Workflow Engine users. If you need this feature and are willing to provide feedback, please contact us, and we will grant you access.

What is BPMN?

BPMN (Business Process Model and Notation) is an international standard for describing and modeling business processes. BPMN provides a visual language that is equally understandable to both business analysts and technical specialists. It is a universal tool for creating clear and comprehensive process documentation.

Key Advantages of the BPMN Diagram Import

  • Unique Market Offering: Optimajet Workflow Engine now offers a unique capability for on-premise .NET solutions — BPMN diagram import for Dot Net developers, it's rare to find a library that offers this functionality, making our product a trailblazer in the field

  • Accelerated Process Creation: With BPMN diagram import, users can instantly transfer their existing process models into Optimajet Workflow Engine, significantly reducing the time required to set up new workflows.

  • Support for International Standards: The new tool supports the BPMN standard, making your processes compatible with other systems and enabling easy exchange of diagrams across various platforms and teams.

  • Ease of Use: Importing BPMN diagrams is straightforward and involves just a few simple steps. The user uploads the diagram file, and Optimajet Workflow Engine automatically converts it into a workflow that is ready for further configuration and execution.

  • Handling Complex Processes: The new feature allows for easy import and management of processes of any complexity, including parallel flows, loops, and branches, expanding the scope of your automation capabilities.

In the image below, you can see an example of a pizza order BPMN diagram.

Image description

How Does It Work? Just Three Simple Steps

1. BPMN File Upload: The user selects and uploads a BPMN file (.bpmn) through the Optimajet Workflow Engine interface.

2. Automatic Conversion BPMN to Workflow Engine Schema: Workflow Engine analyzes the structure of the uploaded diagram and automatically converts it into a one or several workflow schemas that can be further configured or executed.

For example, the import of the pizza order BPMN diagram was transformed into two separate workflows: the Customer Workflow Schema and the Vendor Workflow Schema.

Customer Workflow Schema

Image description

Vendor Workflow Schema

Image description

3. Flexible Configuration: After import, users can make any necessary adjustments to the process, adapting it to specific business requirements, and start using it right away.

Practical Application

The BPMN diagram import feature will be especially valuable for companies that are already actively using BPMN in their work and want to migrate their processes to the Optimajet Workflow Engine platform with minimal effort. It is also an excellent tool for quickly launching automation when ready-made solutions need to be implemented promptly.

Conclusion

BPMN diagram import is an important enhancement that will be introduced in the upcoming versions of Optimajet Workflow Engine. We are confident that this feature, unique for on-premise .NET libraries, will help our users achieve better results in business process automation, making it faster, simpler, and more efficient.

If you need this feature and are willing to provide feedback, please contact us Or Stay tuned for updates and be ready for new possibilities in the upcoming release!

Very important

Please write in the comments about the challenges you face when choosing a workflow engine in the .NET stack. What is the most critical deal-breaker when deciding which library to use? We will try to create a guide that benefits the entire community and helps you.

. . . . . . . . . . . . .