Document Actions
PloneMeeting 1.4
Up to Product page
PloneMeeting 1.4 includes a refined document generation system: (1) Several POD templates may be defined for a given item or meeting content type (activation of those POD templates depend on permissions and conditions); (2) The user may "freeze" any POD template when any item or meeting transition is fired. UI improvements include the ability to walk from one item view to the item view of the previous or next item in the meeting. New algorithms for inserting items into meetings are included. New optional fields for items and meetings were defined (observations on items and meetings, meeting number, effective start and end date for a meeting, meeting place...)
For additional information about this project, please visit the
project page.
Available downloads
Release Notes
| State | Final release |
|---|---|
| License | GPL |
| Release Manager | Gaetan Delannay |
- Multiple POD document templates may now be defined for a given item or meeting content type within a given meeting configuration. A POD template is given a title, a condition, a permission, a format (doc/pdf/odt/rtf) and of course the real POD template (file). One may also specify an event that will trigger the freeze of the POD document into the database. This event can be chosen among all item- or meeting-related transitions.
- On MeetingItem, a new optional Kupu field "Observations" allows to enter comments on items. Specific permissions are defined for reading and writing the content of this field.
- On Meeting, new optional fields are defined: effective start and end date, place, observations and a meeting number that is incremented every time a meeting is published.
- Reading/writing decision annexes are now protected by distinct permissions
- "Add" permissions on content types used within the PloneMeeting tool were merged into a single permission.
- 4 ways to insert items into a meeting are now implemented: at the end, depending on proposing group order, depending on category order or depending on all groups order. Moreover, the method allowing to compute the "insert order" of an item may be overridden by a sub-product.
- Any object deletion is now logged into event.log (userId, object title)
- Some missing i18n labels were translated (french, english)
- On meetingitem_view, it is now possible to access previous and next items (when relevant) through arrows. So the user is not forced to pass through meeting_view.
- meetingitem_view now displays item number and "toDiscuss" field if relevant.
Change log
See all tickets.
PloneGov.ch receives the Swiss eGovernment Award 2008!