There are many ways to make digital processes make decisions. Rules are used in almost any workflow process today to determine what path of steps and decisions within a process should be followed.
FlowWright was built with two mandates: 1) "keep it intuitive" and 2) "do it your way". Most BPM/Workflow products require users to implement everything within their platform ecosystem. Users often learn the hard way that this restrictive approach makes it difficult to accomplish your goals successfully or efficiently. This blog explains why workflow without limitations is the best approach.
When new clients onboard the FlowWright workflow platform we ensure that they are set-up for success by ensuring all team members have completed our 4 day on-site Training Program.
A workflow can publish events an Enterprise Service Bus (ESB.) And a workflow instance may also wait for certain event or message to arrive: once the message arrives, the workflow process will proceed.
Workflow instance status has been available and accessible since FlowWright was first developed several years ago, but FlowWright now introduces a new, strategic enhancement: the ErrorWait state! Welcome to v9.6 of FlowWright BPM.
FlowWright's data access layer is the lowest architectural layer in the platform. This is where all calls to the database are handled. Whether users are requesting data from the database or updating data within the database, all calls are sent through this data access layer.
The FlowWright team spent a year studying, analyzing, and listening to customer feedback before settling on the new UI design, including critical technology updates.
Sendgrid is a Twilio product used to send emails in volume. FlowWright v9.6 introduces a new email workflow step for sending emails using the SendGrid service.
FlowWright customers can expand FlowWright’s capabilities as needed! While FlowWright out-of-the-box includes many system data types you can also build your own data types.
What's a data type? Data type is what gets rendered as a control for an input of a step.
Tasks are the most important step in any user-interactive workflow where tasks are routed to users for approval. Tasks have existed in FlowWright from Day #1 and task functionality has been enhanced with each release. V9.6 includes more task functionality upgrades.
