...

• as much as possible should be driven by the workflow using generic components
  
  • this allows for maximum customisation by customers
• review app should be equally configurable in case the customers wants more Human Tasks with different options
• there can be multiple items in review app for one workflow instance, in case it branched and both branches are in Human Tasks

Open questions

• should we remove or change messages (for all users) that point to an item in the Review app when the item is answered?
• how do we transfer command context attributes into the workflow, currently it cherry-picks only a few of them
• can we remove the need for configurable views in Review App and instead supply the available options from the workflow itself? on the item added
• is the review app a content app?
• jbpm starts background threads, how much of a problem is this and what can we do?
• workflow definitions are reloaded on change in repository but not updated in jbpm knowledge service, how can we do this without restarting the knowledge service?

• should we maybe mark item in review app as completed instead of removing it?

...