![]() ![]() The core philosophy of Elsa is to be able to connect small executable units with one another, allowing you to orchestrate real business processes such as document approval, customer on-boarding and order fulfillment processes.Īs should be clear by now, Elsa is inspired on Orchard Core Workflows. NET Standard libraries and tools that enable developers to implement long-running workflows. NET application to enjoy the power of workflow. Ultimately, I decided it was about time to take Orchard Core’s workflow engine and philosophies, and turn it into a reusable. However, these applications were not Orchard Core powered applications, nor did the simple desire to use workflows warrant taking a dependency on Orchard Core Framework. I often found myself wishing that I could use it in other ASP.NET Core applications as well. ![]() ![]() Being able to create, configure and modify complex, long-running business processes is a powerful feat in many an app, and the Orchard Workflow module makes this sort of thing child’s play. ![]() I’ve used Orchard 1 workflows to implement user registration, authentication and content approval workflows. One if its most awesome features is Workflows. NET applications using Orchard, an extensible, modular, open source application framework and CMS built with Classic ASP.NET MVC back in the days, and now redeveloped for ASP.NET Core. NET applications with Elsa 2, please checkout this series instead.įor many years, I’ve been developing. If you want to learn how to build workflow driven. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |