<img height="1" width="1" style="display:none;" alt="" src="https://dc.ads.linkedin.com/collect/?pid=287945&amp;fmt=gif">

Extending FlowWright - make it work the way you want

Posted by FlowWright on Dec 4, 2019 10:45:00 AM

FlowWright is designed to be extended and expanded and many of our users push the product into new areas (which we love to see!)  To highlight all the ways FlowWright can be extended we summarize them below. 

  • data types
  • workflow steps
  • business objects
  • event handlers
  • form widgets
  • dashboard widgets

Data types are rendered when you click on a workflow step.  For example, if you look at the "decision" step, the following properties are rendered.

workflow step properties

Most step properties are of the "String" data type and render a simple text box for users to configure a value for the property.   For the "condition to evaluate" property (above), a multiline text box is rendered.

Most properties use simple data types, but some properties require more complex data types.  For example, within the "task" step, the "route to users" property uses a highly complexity data type that renders a button that, when clicked, shows a user selection dialog.

Depending on your requirements, a data type can be built by implementing a very simple interface.

Workflow steps are the most important elements in any workflow.  The majority of our customers end up building one or more of their own workflow steps to perform custom functionality that is related to their application or domain.  Workflow steps can also be easily built by implementing a simple workflow step interface. 

Business objects are a way to reuse functionality that exists within your existing APIs in FlowWright workflows.  For example, your application has a "person" object, and it resides within your API, you can use that object within FlowWright workflows by implementing the business object interface.  Once implemented, objects that exist within your APIs can be directly used in expressions or inputs of a workflow step. 

As an example: users can define a business object called "person1" using the type "person" business object type.  You can use this "person1" object within any expression, here's an example expression and what it looks like below:

cDevBO.person1.age > 18

Event handlers act when events happen and are published and processed by the FlowWright Event service bus.  Event handlers can be built using a simple to implement interface.  Event handlers are the key to event-based processing.

Form widgets get used within form definition and form instances.  These UI controls either render information or capture information from the users.  FlowWright provides many form widget UI controls and if you may build your own, configure them within FlowWright and use them on your FlowWright forms. 

Dashboard widgets get rendered within FlowWright dashboards, FlowWright provides many widgets that are specific to FlowWright, but also common dashboard widgets that are data driven.   Users can also easily build and configure custom dashboard widgets. 

FlowWright's help section also provides helpful examples on how to build, configure and use each of the above items.

Making extensions is thoroughly covered in FlowWright on-boarding training sessions.  This training includes several hands-on development of custom items such as workflow steps, business objects and event handlers. 

FlowWright is built for extensibility: schedule a customized demo to learn about how FlowWright can be extended. 

New Call-to-action

 

Topics: extending workflow database, workflow solutions