To efficiently meet varying client requirements, the output tool should allow for custom rule definitions regarding the naming of drafts (preliminary copies) and official issues (releases).
1. Flexible Naming Logic
The system must support various nomenclatures for automatic index incrementing:
- System A (Separated): Use of specific prefixes, e.g., V01, V02, ... for drafts and F01, F02, ... for official issues.
- System B (Cyclical): A letter defines the cycle, while a specific number marks the release. (Example: A01–A98 are drafts, A99 is the final release of Cycle A). The next cycle starts with B01 (draft) or directly with B99 if a release is published immediately, and so on.
2. Functional Status Control
When creating an output, a checkbox or dropdown menu defines whether it is a draft or a release. This triggers the following automated features:
- Watermarks & History: For drafts, the watermark remains visible in the index history even after the output is finalized/closed.
- Intelligent Revision Clouds: For releases, the system automatically detects all revision clouds created during the draft phase (since the last official release) and displays them if the corresponding setting is enabled. This eliminates the current manual process of selecting which revisions should be shown for each output.
3. Key Benefits
This logic makes the tool significantly more adaptable. It covers a wide range of client-specific standards, reduces manual indexing errors, and ensures seamless, automated documentation of all design stages.
Open