End users, process managers and application managers are not allowed to have direct access to the data store.
It must be relative easy to migrate data from one distribution to other distributions. All distributions must therefor share a common data model.
The data model must be a relational data model without relationships. This means:
- the data model will contain multiple tables where each table is related to an unique component, like a process, a run, an action template or an action.
- that records have unique ID’s and these unique ID’s are used to relate records.
- no formal relationships are defined.
Data duplication is allowed if this has a positive impact on performance.
No auto numbering included in the data store must be used.
Automations included in the platform must not be long running automations. As a rule of thumb, automations should be executed within 2 minutes under normal circumstances.
The platform must have a performance that can be expected from the technology stack used, its number of users and the amount of data included.
The platform must support the easy and quick creation of processes.
The platform must have a consistent look and feel.
There must be one app, called the Forms and Flows app, for employees.
The platform must support reliable updates. This means:
- Updates will always be from one version to the next version. Versions are not skipped.
- The Forms and Flows app must support maintenance mode in combination with session expiration.
A rollback plan must be included in every update.