FlowWright v9.6 has been in the works for a while now - and now it is HERE! This latest version includes upgrades, including a new and very responsive User Interface. We listened to feedback from business users and gave the user interface a much-needed face lift. We had graphics designers and top developers working all year to design and implement FlowWright improvements - a great deal of thought, planning, and effort have resulted in significant benefits for FlowWright customers.
The FlowWright UI uses the latest version of Bootstrap 4.x for the UI technology. The improved UI design is geared to both business analysts and developers so that both feel equally at home. In addition, FlowWright improved server-side performance through improved technology changes. The new UI now provides a consistent and pleasant look-and-feel throughout.
All application icons were re-designed as SVG icons - icons that scale well regardless of resolution settings. All step icons also were re-designed as SVG icons and then converted to a standard PNG format for customer convenience.
Microservices’ use is becoming more standard within organizations. FlowWright v9.6 gives you the power to define a workflow definition and then turn that workflow definition into a REST API call. This was already possible using FlowWright’s REST API, but now you can just define a process, turn it into a Microservice and have your customers call it through REST, simple as that.
Workflow definition and instance audit reports have been enhanced to be more professional and template driven. Reports are generated based on a word template that is stored on the server. Templates can be modified to look like your reports. An example of a generated report looks as follows (for a workflow definition):
Improving reports was an important items on our development plan. Until now, reports were designed using SSRS - Microsoft’s report designer - and executed using the SSRS reporting engine. Now, with the release of v9.6, FlowWright has a graphical report builder that enables you to design and execute reports fully within FlowWright.
The API is more comprehensive and has been re-organized. In addition, lower level objects are now internal and cannot be created directly: they have to be retrieved using higher level objects. For example, "deWorkflowDefinition" object cannot be created directly, it must be retrieved using the "deDesign" class.
The FlowWright API also introduces a new constructor that accepts a user-session object. The introduction of user-session objects minimizes database calls on API constructors, and greatly improves the performance of the constructors without making database calls.
Interface for the data types now implement iDataType2 interface, which is more engine context based on consistent with the rest of the interfaces within FlowWright. The engine context gives access to the outside world from within the data type, without any limitations. In the future, the data type engine context can be easily expanded to provide more powerful functionality to data types. FlowWright v9.6 is fully backwards compatible with data types implemented using the "iDataType" interface.
All system data types have been updated to use this new "IDataType2" interface.
Data Access Layer
Data access layer was also upgraded with new API calls. All SQL calls now support "parameterized queries", where the parameters are automatically encoded/escaped and inserted into the query on the database side. This enhancement hugely reduces SQL injection attacks through the data access layer. We have also implemented single line queries, static methods are now available to get a data table, execute SQL and more.
Tasks now have percent complete. Once the task details are rendered, task percent can be updated.
Task list will also display the percent completed for each task:
Check List Tasks
v9.6 implements a new task type called "checklist" task, where you can define a check list of items and route the task to user(s). As checklist items are marked completed, the task percentage complete is also automatically computed. Checklist task is rendered as follows:
Checklist tasks can contain checklist items that are optional, providing flexibility if needed.
And, lastly, FlowWright now supports task delegation. Tasks can be automatically delegated to other users when tasks are created and assigned. Using the following UI, create a task delegation entry, and leave the rest to FlowWright to handle.
Workflow triggers have been expanded from just email and file system-based trigger to now include the following triggers:
The “trigger engine” supports the above trigger launch mechanisms and the number and types of triggers available for use will expand in the future.
When sending emails or task emails, content often repeated and it took effort and organization to maintain consistent content. FlowWright v9.6 lets you define email templates that can be used within email and task steps as the body of the email message. Point to an existing email template or make a copy, modify, and then use.
In addition, v9.5 of FlowWright sent task emails through the email queue, but now the email step can be configured to send email messages through the queue. By default it will perform a direct send as before, but for performance reasons the email queue can be used. There is also more information and enhanced functionality around the email queue. Lastly, a new email step is available for sending emails through the Twilio SendGrid email service.
There are quite a number of FTP steps, specifically in the area of SFTP, but v9.6 now includes additional steps providing new and enhanced functionality. For example, there is a new "waitformessage" step, that causes workflow processes to wait for a user defined message. Messages to the workflow instance can be sent through the .NET or the REST API.
The database query step is now able to return its result in XML or JSON (default format is XML.) Upgrades to the data access layer has dramatically improved performance of this step. Along with new triggers in the product, there are also steps for publishing messages to RabbitMQ, MSMQ, and SSIS - SQL server integration services-based steps for executing internal or external packages. There is also a new SQL step for executing SQL jobs.
There are also some new enhancements to step inputs: now you can make a step input hidden or read-only. Designers can also provide default values and tag values, which can be used within the data type of the step input.
Lastly, FlowWright now comes with a new "lookup data" data type: the step can be used within a step input to have dynamic list of items, where items are retrieved from the lookup list.
FlowWright v9.6 introduces a new error wait state for workflow instances. Instance may go into this state, when the instance contains steps that have errors and also waiting, as shown below in the graphic:
The UI upgrade includes improvements to form design. Importantly, forms now support server-level events. When forms definitions/instance are created, deleted, updated, events can be published to the Enterprise Service Bus for processing.
Business objects are powerful within FlowWright and now we have enhanced the business object configuration UI so that business object configuration can be easily tested.
User connectors synchronize users with directory services. Now, our updated connectors will ignore disabled users. In addition, if the "LDAP" user connector is pointed to an AD group, active members of that group will synchronize with FlowWright.
Hope you enjoy v9.6 as much as we do. We love our smart customers and we owe most of the vast improvements in this latest version from the needs and ideas you share with us!