Deletions are marked like this. | Additions are marked like this. |
Line 13: | Line 13: |
* | |
Line 15: | Line 15: |
Line 16: | Line 17: |
= Translation Related = * Fix getMessage so that an empty message default to the default language's message * Search for \t\t in Messages.txt, FieldNames.txt, TableNames.txt and add missing DE translations * Fix missing DE translations: * OK - After file upload * Next Action - New task * Comment types |
|
Line 27: | Line 19: |
* Display drawing component name in front of entry field in input form. Use a tag to display the name. | |
Line 29: | Line 20: |
* Suppress display of '*' for non-required drawing code components | 1. Allow changing of document codes, even if a revision file has been uploaded, provided the file uses an internal number. |
Line 31: | Line 22: |
* Allow changing of document codes, even if a revision file has been uploaded, provided the file uses an internal number. | 1. Add a comment field for each workflow field that has an approval status. This is to allow entry of a comment for approved with comments. |
Line 33: | Line 24: |
* Add button 'preview', which stays in the input form. Sets the drawing code derived fields, and leaves you in the input form. | 1. Make entry of a comment required when a revision is rejected |
Line 35: | Line 26: |
* Add a comment field for each workflow field that has an approval status. This is to allow entry of a comment for approved with comments. | 1. Add approval status over-rulled (for release/versand only?) |
Line 37: | Line 28: |
* Make entry of a comment required when a revision is rejected * Add approval status overrulled (for release/versand only?) * Allow different workflow types for each revision. Add workflowTypeId to Revisions. Drawings workFlowTypeId --> defaultWorkflowTypeId |
|
Line 44: | Line 30: |
* --(In Document Detail: When you press the New Comment button, it should copy the classification information from the document to the new task.)-- DONE 2009-11-13 V11.3 | |
Line 46: | Line 31: |
* Allow entry/update of subscribers when entering a new task | 1. --(In Document Detail: When you press the New Comment button, it should copy the classification information from the document to the new task.)-- DONE 2009-11-13 V11.3 |
Line 48: | Line 33: |
= Searching = * Implement additional search fields for '''documents''': * Search for non-completed workflow steps assigned to X * Quick search for document workflow tasks assigned to me (or someone else). Like comment search. * '''Idea''': Simple for V11.x hierarchical reference data * Implement a search code, to use instead of the ID value - How to make it efficient? * Allow non-active items in dropdown lists = Email Related = * Generate email when a new comment is created - Check if this is implemented, and how to configure it * Generate email when a new comment note is entered - Check if this is implemented, and how to configure it = Configuration Documentation = * Document validation rule for checker != approver * Document for 'send mail: if required, always, never' works |
1. Allow entry/update of subscribers when entering a new task |
DrawMGT Wish List
Requests and Ideas for new DrawMGT Features
Contents
Major Features
- Generic reports
- Dashboard that displays:
Revisions with workflow steps assigned to me.
New/pending/repoened tasks assigned/delegated to me
Minor Bugs
General
Document Related
- Allow changing of document codes, even if a revision file has been uploaded, provided the file uses an internal number.
- Add a comment field for each workflow field that has an approval status. This is to allow entry of a comment for approved with comments.
- Make entry of a comment required when a revision is rejected
- Add approval status over-rulled (for release/versand only?)
Task Related
In Document Detail: When you press the New Comment button, it should copy the classification information from the document to the new task. DONE 2009-11-13 V11.3
- Allow entry/update of subscribers when entering a new task
History Related
- Implement field-level history messages. List before/after for each field that was changed. At least for:
- Revisions
- Tasks
create table history ( date date, time time, session_id int, old int, new int ); create trigger tr_upd_comments after update on Comments for each row insert into history values( now(), now(), @@pseudo_thread_id, old.projectPhaseId, new.projectPhaseId ); update Comments set projectPhaseId = 8 where commentId = 10; select * from history;
- Implement file versioning for uploaded files (add a version number field to the internal file names?)
Back-End Tools
- Update app/etc/uploadFile.pl to:
- handle internal file names
- handle matching of first 'x' characters of filename against drawing code