<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to feature-requests</title><link>https://sourceforge.net/p/qiqcms/feature-requests/</link><description>Recent changes to feature-requests</description><atom:link href="https://sourceforge.net/p/qiqcms/feature-requests/feed.rss" rel="self"/><language>en</language><lastBuildDate>Sat, 16 Feb 2002 17:22:56 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/qiqcms/feature-requests/feed.rss" rel="self" type="application/rss+xml"/><item><title>E Mail Notification</title><link>https://sourceforge.net/p/qiqcms/feature-requests/3/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;E-mail notifications allow events to trigger &lt;br /&gt;
notofications by email. This way users can be alerted &lt;br /&gt;
that certain events, that require their attention, &lt;br /&gt;
have happened.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mario De Caerle</dc:creator><pubDate>Sat, 16 Feb 2002 17:22:56 -0000</pubDate><guid>https://sourceforge.netc9ce8ae4ff788427445f2fd39bf355fd8cac0d2f</guid></item><item><title>LDAP Authentication</title><link>https://sourceforge.net/p/qiqcms/feature-requests/2/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;LDAP authentication, will also allow integrated &lt;br /&gt;
authentication on Windows.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mario De Caerle</dc:creator><pubDate>Sat, 16 Feb 2002 17:20:58 -0000</pubDate><guid>https://sourceforge.net9ac8a93816b0b21cdd46cabf7c77801e5ee2d078</guid></item><item><title>Approval Route</title><link>https://sourceforge.net/p/qiqcms/feature-requests/1/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Since this is a Content Management System, and since &lt;br /&gt;
plans exist to create an ERP package out of the same &lt;br /&gt;
framework, there should be some sort of Approval Route.&lt;/p&gt;
&lt;p&gt;An approval route designates a line of approval, so &lt;br /&gt;
that content additions (or payments) can be held in &lt;br /&gt;
pending state until it is approved according to the &lt;br /&gt;
approval route.&lt;/p&gt;
&lt;p&gt;Possible approval routes:&lt;br /&gt;
- simultanious approval&lt;br /&gt;
Where several people can approve at the same time.&lt;br /&gt;
Possibly with a quotum (2/3, 50%, unanimous)&lt;br /&gt;
- Lined approval&lt;br /&gt;
Where the approvers are in a line; the second in &lt;br /&gt;
line only receives the document for approval after the &lt;br /&gt;
first has voted.&lt;br /&gt;
- Hierarchical approval&lt;br /&gt;
Where approval is done based on hierarchical &lt;br /&gt;
manager status. Meaning a manager votes on everything &lt;br /&gt;
people beneath him created/did.&lt;br /&gt;
- Overall approval&lt;br /&gt;
Where a person is always last in line, and must &lt;br /&gt;
approve. In Overall approval, he can not disapprove, &lt;br /&gt;
he can only send back.&lt;br /&gt;
- Veto approval&lt;br /&gt;
Where a person is always last in line, and has &lt;br /&gt;
veto rights. Meaning if he disapproves, it is &lt;br /&gt;
disapproved all together.&lt;br /&gt;
- Simultanious Veto approval&lt;br /&gt;
Where a group of persons have veto right by &lt;br /&gt;
approving a quotum. (e.g. 2/3 approve = approved)&lt;/p&gt;
&lt;p&gt;Possible Approval states:&lt;br /&gt;
- approved&lt;br /&gt;
Stating all is right&lt;br /&gt;
- disapproved&lt;br /&gt;
stating No&lt;br /&gt;
- Edit&lt;br /&gt;
The voter edits the document and sends it back to &lt;br /&gt;
the previous in the route&lt;br /&gt;
- Edit and approve&lt;br /&gt;
Is possible, but must be set as a special option&lt;br /&gt;
- Send back&lt;br /&gt;
The document is send back with comments, stating a &lt;br /&gt;
conditional disapproval.&lt;br /&gt;
- Approve with comments&lt;br /&gt;
The document is approved, but comments are to be &lt;br /&gt;
made. These comments go back to previous in route.&lt;/p&gt;
&lt;p&gt;Comments can be send down the route, and can be &lt;br /&gt;
annotated, sending the annotation to the original &lt;br /&gt;
sender. Everyone in the approval route should be able &lt;br /&gt;
to see all comments made, unless labeled private.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mario De Caerle</dc:creator><pubDate>Sat, 16 Feb 2002 15:56:02 -0000</pubDate><guid>https://sourceforge.netd49202431bc5c97ac67260bf1f782cec3bbad390</guid></item></channel></rss>