2018 was a fantastic year for FlowWright and our customers. Our customers around the globe automated many processes using our workflow technology and became very efficient in what they do. We saw some amazing uses for our product, and continue to push the boundaries of workflow automation to ensure whatever needs arise-our software can handle. Outside of automation of processes, the product was used in large scale Cutover projects, supply chain automation, workflow controlling IoT, and many more unique uses in different domains throughout the world.
As FlowWright v9.5 is about to come out in the new year, one of the major enhancements made to the product was to upgrade the workflow designer to expand its power capabilities. The Development team has been busy as we want to produce the best experience for our users in the simplest, easiest, yet flexible, workflow designer on the market.
Most start-ups start small, scale and begin to grow internal manual processes can become inefficient as the workload gets larger. These processes become cumbersome and can hurt your growth in the long run if you don't put tools and systems in place to become more efficient. So, when is this important to begin to think about finding a solution?
Our customers have multiple environments including: development, QA, and production for workflow. Workflows and their related items such as forms and events are built by developers on development environments, and then must be configured on QA environments for QA testing.
True Story: My wife gets a new vehicle. Two (2) weeks later, someone hits the new vehicle from behind. The car is a wreck. Accidents happen, that's life. The dealership says the process is: bring the vehicle to the dealer's body shop for repair, wait, then it'll be ready. When the vehicle was dropped at the body shop, they said, they will order the parts, fix the vehicle and it will be done and returned to us in one and a half (1.5) weeks.
There's no platform that offers an entirely "no code" solution (if someone does offer, I would be very careful). Even though "no code" is possible, low code is more realistic. FlowWright is built with "low code" in mind and thus certain parts of most can be reused within your application. Here's how its done:
The largest automotive OEM parts supplier in the world has to perform an upgrade on their SAP system that runs the whole company. This project entails every facility, department, and vendors that rely on product to be shipped to retailers around the globe. The stake are extremely high and there is huge risk involved. So, how does workflow play a part? At the onset the company has to do the following: