WEM Team Development
The WEM flowchart editor allows for custom monitoring and testing processes. For instance, it is quite easy to direct an application flow onto a screen or dialogue for checking vital database fields - merely by rerouting an exit - and route the flow back to normal once the testing is done.
This can be implemented using a static testing flag, directing the logic through a testing flow in many flowchart locations simultaneously.
Many WEM developers use permanent testing and monitoring workflows inside the application without any of the application users being aware of it, which allows for continuous testing even in the live runtime.
In addition to this, the WEM modeler has an inbuilt debugger, allowing to step through a flowchart from marker to marker, and to define custom expressions to monitor each and every part of the database during the debugging process.
WEM equals CI CD by nature.
The seamless and real time publication protocol without downtime allows for continuous and side by side development and deployment like no other platform can offer.
It is the core property of the WEM platform and the main reason it was built.
It is also one of the differentiators from peers
For small and mid-size systems and teams, using a combination of flowchart / database folders and version numbers on flowcharts will bring adequate version control.
See for instance the screenshot below, where we use three different versions of the same sub flowchart. Changing to a version simply means connecting the exit to a different version number. In addition to this, the function library has a number of environment functions that determine for instance in which runtime (Preview, Staging, Live, Android, iOS) the application is currently running.
Inside the flowcharts, certain parts of the logic can be made available to that particular runtime only.
For very large projects and organizations, one of our partners has custom built WEM solutions available that will allow versioning inside a staging or live runtime without the need to re-publish the entire application to that particular runtime.