From RPM Wiki
| Table of contents |
[edit]
Summary
Status levels are an integral part of Process management. Status levels define the different stages or milestones that define the life of a form.
[edit]
Rules
- At least one status level is required
- Status level names must be unique within the process
[edit]
User selectable
Status levels have a yes/no option to indicate if they can be selected by users or not. A status level that is not user selectable can be called "read only". The purpose of this feature is to allow the designer to indicate status levels that they only want to be reached through triggers and approvals.
- Default is "Yes" (user can select, not read only)
- Yes: Listed in the status drop-down when editing a form. In other words, the normal behavior.
- No: Not listed in that drop-down. If the current status is read only (not user selectable) then the drop-down is disabled.
[edit]
Auto-archive
This yes/no option specifies that when a form reaches this status level it should be archived.
- Default is "No"
[edit]
Security
(TODO)
[edit]
History
- Mercury: Predecessor, "Project Management" added
- Venus: Process management as we know it added
- Earth: Can set status level by new feature, form import. New feature global actions creates actions when a status level is reached.
- Luna: Drag & drop UI for status level order
- Mars: Status triggers (fill in a field sets form to a status). Template import/download.
- Ceres: Form archive feature added which includes auto-archive setting for status levels. Removed status level "instructions" field. Moved agent stauts level permission to new template permissions page.
- Rockefeller: Form history including status changes. History box shows time at current status.
- Judge: "User selectable" option
- This page was last modified 16:39, 25 Jul 2008.
- This page has been accessed 644 times.