News

Workflow Engine 2.0 Improves UI

Version 2.0 of the business process development tool comes in builds for .NET Core and Java, and sports streamlined UI improvements and a number of new methods.

It's been some time since OptimaJet offered a major update to its business process development tool, WorkflowEngine.NET. Just in time and prior to the launch of Visual Studio 2017 launch earlier this week, the company released and renamed its WorkflowEngine 2.0, which now has support for .NET Core and Java and comes with a myriad number of UI and other improvements.

Workflow engines are software-based applications for managing a project's business processes and logic. Windows Workflow Foundation (WF) is a good example of one that's built into the Microsoft .NET Framework. Workflow Engine aims to become an improved alternative to WF.

Besides the .NET Core support, there are a number of other improvements, particularly to the Designer user interface, which has been streamlined and easier to understand (see Figure 1).

Related to the Designer is now the capability to print the Designer's viewport to a PDF within a browser sans UI elements, and the Designer can also be made non-editable in case there's a need to distribute it to certain users. Those capabilities come by way of the addition of three new methods: readonlymode(), printablemode(), and editablemode().

Another feature has been added to the Designer, which allows users to be able to use an autocomplete list when working with these fields: Actor.value, the Activity.Implementation.Action parameter, and Transition.Condition.ActionParameter.

There's also a few new methods for modifying the execution time for timers in running processes:

  • _runtime.SetTimerValue(processId,timerName,newValue), _runtime.ResetTimerValue(processId, timerName): These two methods now change and reset timer values outside the process.
  • _runtime.SetTimerValue(processInstance,timerName,newValue), _runtime.ResetTimerValue(processInstance, timerName): These methods change and reset timer values from within Actions.
UI Improvements to Designer in WorkflowEngine 2.0
[Click on image for larger view.] Figure 1: UI Improvements to Designer in WorkflowEngine 2.0

Besides the .NET Core build, version 2.0 also is available in a Java build, according to the company. Get more information from the company Web site.

About the Author

Michael Domingo is a long-time software publishing veteran, having started up and managed several developer publications for the Clipper compiler, Microsoft Access, and Visual Basic. He's also managed IT pubs for 1105 Media, including Microsoft Certified Professional Magazine and Virtualization Review before landing his current gig as Visual Studio Magazine Editor in Chief. Besides his publishing life, he's a professional photographer, whose work can be found by Googling domingophoto.

comments powered by Disqus

Featured

  • Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

    The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.

  • Diving Deep into .NET MAUI

    Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.

  • Copilot AI Boosts Abound in New VS Code v1.96

    Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.

  • AdaBoost Regression Using C#

    Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.

  • Versioning and Documenting ASP.NET Core Services

    Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.

Subscribe on YouTube