Ticket #370 (enhancement)
Opened 3 years ago
Last modified 3 years ago
pending events: add buttons that change submission state. Create simple workflow.
Status: closed (fixed)
| Reported by: | johnsa | Assigned to: | johnsa |
|---|---|---|---|
| Priority: | major | Milestone: | Bedework 3.5 |
| Component: | web client: admin | Version: | |
| Keywords: | Cc: | ||
Need to provide buttons in the pending events list / edit pending events page to provide some simple workflow:
- take - to take ownership of the event
- send message - to send an email message to the submitter (e.g. asking for more information about the event): details of the message can be produced in the xslt
- reject - with a message explaining why (e.g. the event is already posted)
Already in place: - update
- publish
- cancel
Items 1-3 should change the X-BEDEWORK-SUBMIT-STATUS xproperty so that we can explain to other users what's going on in the basic workflow. E.g. if an event admin "takes" a pending event, her group gets ownership of it, and the UI should let other admins see this. If an admin sends an email to the subitter, the event is "in progress", etc.
Change History
04/17/09 16:53:11: Modified by johnsa
- description changed.
04/17/09 16:53:25: Modified by johnsa
- description changed.
04/17/09 16:54:02: Modified by johnsa
- description changed.
04/17/09 16:54:15: Modified by johnsa
- description changed.
04/17/09 16:54:50: Modified by johnsa
- description changed.
05/13/09 14:21:37: Modified by johnsa
- status changed from new to closed.
- resolution set to fixed.
Status settings aren't needed - only complicates the matter. We now allow event admins to "claim" and "release" pending events. These can (and may) generate email to the submitter. The group and user is stored in X-BEDEWORK-SUBMISSION-CLAIMANT, and the UI checks for the presence of this property.
We now need to complete the email handling bits - send a message on event deletion, let the UI handle sending of a message. Already have message on publish.