Workflow automation users are accustomed to building workflows using various steps such as decisions, tasks, email and more. They use workflow to route tasks and emails to specific users . In this article we talk about how using a test environment for testing these workflows, and associated user routing, saves time for teams responsible for delivering workflow solutions.
All of us here at FlowWright hope you are healthy and safe! And we wish you an amazingly ascendent 2021! Last year, we promised our customers some 2020 improvements and FlowWright delivered on those promises - and then some!
FlowWright user notifications can be created by any user, current user or a workflow process. Unlike tasks, a workflow can create user notifications and continue processing. The user can acknowledge and close the notifications anytime. User notifications can be managed under the Tasks menu. Learn more by watching our video below.
What is Clustering? Clustering is the addition of multiple servers to improve processing throughput and fault tolerance. Clustering is common practice in hosted solutions where the adding more servers can alleviate hardware limitations that are causing processing bottlenecks. Often, the only way to increase business process automation performance is to configure and use additional servers to process workflows.
FlowWright supports the generation and recognition of barcodes. Our workflow automation software supports many barcode formats including UPC. QR codes, and more. Barcodes are a valuable tool for businesses to use across teams, campaigns, and in many areas of business. Users can not only generate, but also recognize barcodes with this functionality. We share a little more in depth look at this feature in the video below.
FlowWright provides several different task routing steps. Now, we have added a new “Route for user selection” task step. A task can now be configured for multiple user selections, and once a task is routed then it will appear with many selections. The selections that are actually made are then stored within variables, and these variables can be used with other task routing steps in the same process flow.
Everyone designs workflows to run from step-to-step from start to finish, but there are some business processes that may necessitate jumping around from one part of a workflow to another. FlowWright now supports this flexibility by allowing some users to select any waiting step and a target step to direct workflow to complete that waiting step and jump to the target step.
FlowWright version 9.8 has just been released and includes significant upgrades to:
- forms capabilities,
- foreign language support,
- authentication support,
- Optical Character Recognition - OCR,
- Enterprise Service Bus (publish/subscribe message bus)
- User Interface customization capabilities, and
- ...much more
Many customers use FlowWright's user interfaces in their own applications - using API calls to choose elements (or whole webpages) of the FlowWright UI in their own User Interfaces. It is important to those customers for FlowWright UI elements be consistent in look and feel with their own company and application standards. FlowWright's new version 9.8 now allows you to customize the Flowwright UI to match your organizations UI scheme. FlowWright now lets you change the following: