FlowWright is designed to be extended, and many of our users are pushing the product into new areas (which we would love to see!). Below, we summarize all the ways FlowWright can be extended. 

• Data types
• Process steps
• Business objects
• Event handlers
• Form widgets
• Dashboard widgets

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

Most step properties are of the "String" data type and render a simple text box for users to enter 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 require more complex ones. For example, in the "task" step, the "route to users" property uses a highly complex data type that renders a button that, when clicked, displays a user selection dialog.

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

Process steps are the most essential elements in any workflow. The majority of our customers build one or more of their own process steps to implement custom functionality for their application or domain. Process steps can also be built quickly by implementing a simple workflow step interface. 

Business objects are a way to reuse functionality from your APIs in FlowWright workflows. For example, if your application has a "person" object in your API, you can use that object in FlowWright workflows by implementing the business object interface. Once implemented, objects from your APIs can be used directly in expressions or as inputs to a workflow step. 

For example, users can define a business object called "person1" of type "person".  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 are published and processed by the FlowWright Event service bus. They can be built using a simple-to-implement interface and are the key to event-based processing.

Form widgets are used within Form definitions and form instances. These UI controls either render information or capture information from users. FlowWright provides many Form widget UI controls, and if you build your own, you can configure them within FlowWright and use them on your FlowWright Forms. 

Dashboard widgets are rendered within FlowWright dashboards. FlowWright provides many widgets specific to FlowWright, as well as standard data-driven dashboard widgets. Users can also quickly build and configure custom dashboard widgets. 

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

Making extensions is thoroughly covered in FlowWright onboarding training sessions.  This training includes several hands-on exercises in developing custom items such as process steps, business objects, and event handlers. 

FlowWright is built for extensibility: you can schedule a customized demo to learn how to extend it.