To be done for Workflow 1.0
A) Basic Workflow
- A) work item has a speaking title and description
- which page, type of request (e.g. review), …..
- --> dynamic title and description based on workflow parameters
- A) no silly content in the message (task id, ….)
- A) open page to be reviewed
- --> can open the pages app
- open the correct version (feature should exist, is used for deleted pages)
- a version is created when the workflow is started (commend)
- the version is name is transported via the workflow (work item?)
- B) work item disappears after reacting on it
- C) reject
- should not stop workflow:
- 1. author publishes
- 2. reviewer rejects
- 3. author stops workflow
- pulse message to the author (without comment)
- tell that it was rejected
- should not stop workflow:
A) Support for Groups (Pulse and Workflow)
- work items are normally sent to groups (not specific users)
- no need to support roles: just users and groups
- once a member of a group reacted the others should know it
- remove the messages?
B) Error Handling
- if the activation fails (for instance the public instance is down)
- the last user/group gets again a work item
- ev. we could just send an error message
- the last user/group gets again a work item
B) Demo User Eric and Peter
- author can start workflow
- reviewer can reject and proceed
C) Commenting
- pass comment on
- starting the review process
- rejecting an item
C) Review App
- jump to an independent review app
- this app is not in the app launcher layout
- main tab
- shows the page
- workflow actions in the action bar
- open diff view
- show dependencies
C) Pulse
- should a message have a location
Next steps
- create stories for the above
Overview
Content Tools