Intervention Manager: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
=Screenshots= | ==Screenshots== | ||
Grouped by event, so that we have a chronological record | Grouped by event, so that we have a chronological record | ||
* [[SynergyWorkshopGrabs]] | * [[SynergyWorkshopGrabs]] | ||
=TODO= | ==TODO== | ||
===Frontend=== | ===Frontend=== | ||
| Line 28: | Line 28: | ||
* Improved popup windows | * Improved popup windows | ||
* Email scheduling from intervention | * Email scheduling from intervention | ||
==Known Issues== | |||
* When a submit-jumpto button is pressed, LifeGuide records a move to the next page in the flow followed by a jump to the target page. This is a side effect of the button having to make sure that all validation is done on the current page before moving on. TODO: It might be possible to filter the extra sequence nodes to remove the unseen page from appearing... | |||
Revision as of 13:34, 11 September 2008
Screenshots
Grouped by event, so that we have a chronological record
TODO
Frontend
- Personal messaging - i.e. when you have been added to an intervention, etc....
- Improved rendering of sequence chart - show offsite jumps, etc -> re-implement in Flex?
- Improved rendering of overview weighted digraph -> re-implement in Flex?
- Pages for deploying and editing interventions
- Emailer pages
- More stats in the information boxes!!
- Forum
- Forum and wiki registration linked with manager
Backend
- Bugs in flow logging (jumps not always recorded properly)
- Investigate IE handling of backwards (might need to generate unique urls...)
- Timing bugs - total time is really broken if you go back!!
- Recording of offsite or internal html jumps
- Investigate possibility of using virtual host for a particular intervention - what needs to be done to support this???
Player
- Method to render page by id, rather than path
- List of pages (render test through xslt)?
- Improved popup windows
- Email scheduling from intervention
Known Issues
- When a submit-jumpto button is pressed, LifeGuide records a move to the next page in the flow followed by a jump to the target page. This is a side effect of the button having to make sure that all validation is done on the current page before moving on. TODO: It might be possible to filter the extra sequence nodes to remove the unseen page from appearing...