post mortem

The workflows functionality was the bootstrapper feature for what is now known as the HyperPortal platform, meaning that it was one of the first functionalities to be developed. 

The motivation for the transformation of workflows to CMS was to bring/allow more data to the processes/tasks tables (e.g., links between entities, advanced search, exports). Furthermore, with such a migration, processes and tasks would also get additional benefits such as individual field history to track deadline and status changes and also to prepare for future feature improvements, such as individual customizations for tasks. 

Initial planning was to completely redo the workflows (frontend and backend) with CMS logic, however, after starting the implementation and taking into account the large amount of data to be migrated and the current production usage of HyperPortal, we had to meet midway, meaning that we needed to reduce the risk by maintaining most of the workflows APIs, but simply replacing the underlying layer from a direct database storage to a CMS-based storage.



ab-automotive and bluekens are pushing the system on entity relations, ES search modeling, etc.

For the future

There was functionality added to support the same workflow behavior as before on the CMS. This added behavior, currently only being used in the workflows, will eventually need to be refactored, otherwise it might not fit other necessary scenarios. More specifically: