The YAWL Android Client has had several people, that added functionality and fixed bugs. I created three workflows that helped me find the flaws and bugs in the different YAC versions, which I am going to describe here. SInce those workflows were mainly used for debugging and had to be completed often, they run in a loop and repeat themselves as the standard control flow.
Test data types
The first workflow was created to test different data types in YAWL and how they are displayed:
YAC, being a mobile application, needs to connect to the YAWL engine. Since one cannot rely on having a constant internet or network connection, YAC can work in an offline or asynchronous mode. While this feature is necessary, it also causes problems when considering the way YAWL works. Problems considering the offline mode will be presented in this article. A discussion is most welcome!
A prototype YAWL client for the android platform has been developed as a part of a master thesis. It allows you to access your work items, wherever you have a connection. It contains additional features that use the advantages of mobile devices. Read the full article for a list of interesting features.