Differences between revisions 64 and 65
Deletions are marked like this. Additions are marked like this.
Line 18: Line 18:
= Work Status =

 || '''Item''' || '''Draft''' || '''Spec.''' || '''Coding''' || '''Review''' || '''Notes''' ||
 ||<-6> '''Detail Screens''' ||
 || Document || Done || Done || OPEN || OPEN || ||
 || Task || Done || Done || OPEN || OPEN || ||
 || Transmittal || Done || Done || OPEN || OPEN || ||
 || User || Done || OPEN || OPEN || OPEN || ||
 || File || Done || OPEN || OPEN || OPEN || ||
 || Dossier || Done || OPEN || OPEN || OPEN || ||
 ||<-6> '''New/Edit Screens''' ||
 || Document || OPEN || OPEN || OPEN || OPEN || ||
 || Task || OPEN || OPEN || OPEN || OPEN || ||
 || Transmittal || OPEN || OPEN || OPEN || OPEN || ||
 || User || OPEN || OPEN || OPEN || OPEN || ||
 || File || OPEN || OPEN || OPEN || OPEN || ||
 || Dossier || OPEN || OPEN || OPEN || OPEN || ||
 ||<-6> '''List Screens''' ||
 || Documents || OPEN || OPEN || OPEN || OPEN || ||
 || Tasks || OPEN || OPEN || OPEN || OPEN || ||
 || Transmittals || OPEN || OPEN || OPEN || OPEN || ||
 || Users || OPEN || OPEN || OPEN || OPEN || ||
 || Files || OPEN || OPEN || OPEN || OPEN || ||
 || Dossiers || OPEN || OPEN || OPEN || OPEN || ||
 || Folders || OPEN || OPEN || OPEN || OPEN || ||
 || Invitations || OPEN || OPEN || OPEN || OPEN || ||
 ||<-6> '''Configuration Screens''' ||
 || Folders || Open || Open || Open || Open || ||
 || Task || Open || Open || Open || Open || ||
 || Classification Lists || Open || Open || Open || Open || ||
 || Classification Classes || Open || Open || Open || Open || ||
 || Classification Schemas || Open || Open || Open || Open || ||
 || Resource Subtypes || Open || Open || Open || Open || ||
 || Access privileges || Open || Open || Open || Open || ||

V2 Screen Layouts

V2Master | V2HighLevelDesign

To Do

  1. Review for correctness [ALL]
  2. Review headers and sub-headers (including font size)
  3. Add buttons with button titles, tune button colours (should be less glaring)
  4. Check widths of selects, to be consistent across screens
  5. Check links for consistent actions
  6. We plan to go to a single edit screen, instead of separate edit screens for the object data and classification.
  7. File Category will be internal only (user should not see)
  8. Introduce different header background colours for each object (using subtle tones)

Work Status

  • Item

    Draft

    Spec.

    Coding

    Review

    Notes

    Detail Screens

    Document

    Done

    Done

    OPEN

    OPEN

    Task

    Done

    Done

    OPEN

    OPEN

    Transmittal

    Done

    Done

    OPEN

    OPEN

    User

    Done

    OPEN

    OPEN

    OPEN

    File

    Done

    OPEN

    OPEN

    OPEN

    Dossier

    Done

    OPEN

    OPEN

    OPEN

    New/Edit Screens

    Document

    OPEN

    OPEN

    OPEN

    OPEN

    Task

    OPEN

    OPEN

    OPEN

    OPEN

    Transmittal

    OPEN

    OPEN

    OPEN

    OPEN

    User

    OPEN

    OPEN

    OPEN

    OPEN

    File

    OPEN

    OPEN

    OPEN

    OPEN

    Dossier

    OPEN

    OPEN

    OPEN

    OPEN

    List Screens

    Documents

    OPEN

    OPEN

    OPEN

    OPEN

    Tasks

    OPEN

    OPEN

    OPEN

    OPEN

    Transmittals

    OPEN

    OPEN

    OPEN

    OPEN

    Users

    OPEN

    OPEN

    OPEN

    OPEN

    Files

    OPEN

    OPEN

    OPEN

    OPEN

    Dossiers

    OPEN

    OPEN

    OPEN

    OPEN

    Folders

    OPEN

    OPEN

    OPEN

    OPEN

    Invitations

    OPEN

    OPEN

    OPEN

    OPEN

    Configuration Screens

    Folders

    Open

    Open

    Open

    Open

    Task

    Open

    Open

    Open

    Open

    Classification Lists

    Open

    Open

    Open

    Open

    Classification Classes

    Open

    Open

    Open

    Open

    Classification Schemas

    Open

    Open

    Open

    Open

    Resource Subtypes

    Open

    Open

    Open

    Open

    Access privileges

    Open

    Open

    Open

    Open

General Notes

Process

  1. If it's difficult to come to agreement then default to showing more data and then solicit real customer feedback for additional guidance
    1. Don't over think or waste time defining layouts
    2. Encourage customer feedback and interaction

Terminology

  1. Object - Refers to system objects such as documents, revisions, tasks, transmittals, users, etc.

    • Block ordering is applicable to following Objects:
    • Documents and Revisions
    • Tasks
    • Transmittals
    • Dossiers
    • Files
    • Project Team
    • (Folders - lower priority)
    • (Classification Fields - lower priority)
  2. Type - A field associated with the object that determines its classification class, and consequently:

    • The allowed set of classification fields and their properties
    • The screen display of the classification fields

Block Ordering

Not all blocks are relevant to all Objects.

{Object} {Type} {Code} - Page title

  1. Identification Block

    • Type - e.g. Document type

    • Code - e.g. Document code

    • Title - Title, which depending on the type, could be multiple lines

    • Author/Issuer - to review

    • Date - to review

    • Object specific fields
    • (Description/Summary) - suggest defining description as a classification field

    • (Status, Private/Public, External/ProjectTeam flags) - to be looked into

    • (Message) - used for Transmittals, move to its own Block

    • Classification fields assigned to identification block (for the given data type)
  2. Folder Block - for Team Members OBS Block, with multiple entries

  3. Responsibilities and Due Dates

  4. Classification Block

  5. Properties Block

Revision Files or Note Blocks - each revision or note has its own block

Reference Blocks:

  1. Links

  2. Subscribers

  3. Transmittals

Detail Screens

Document Detail Layout

  1. Document - {Type} {Code} - Page title. The code is the only document code, which excludes the revision code

  2. Identification {startOfTitle} - Document identification block

    • Type - Document type

    • Code - Document code

    • Title - 4-line document Title

    • Identification fields

  3. Folder {folderPath} - Folder block

  4. Classification - Document classification block

  5. Properties - Document data block. Only displayed if data fields are defined

  6. Revisions - Sub-header

  7. Revisions - Revisions Block with button +Revision

    1. Revision {revisionNumber} {date} {startOfTitle} - Revision sub-block with button Edit (for editing all blocks ***)

      1. Identification - Revision identification sub-sub-block

        • Type - Revision Type

        • Code - documentCode-revisionCode

        • Title - - 4-line document Title

        • Author

        • Date

        • Classification fields assigned to identification block (for the given data type)
          • (Description) - define description as a classification field assigned to identification block

      2. Responsibilities and Due Dates - Revision workflow sub-sub-block

      3. Classification - Revision classification sub-sub-block

      4. Properties - Revision Data sub-sub-block. Only displayed if data fields are defined

      5. Revision Files - Revision file list sub-sub-block, table with following columns, button +File

        • Type - File type

        • Author - Who uploaded

        • Date - Date/time stamp

        • Description

        • Filename

      6. Notes sub-header

      7. Notes sub-sub-block with button +Note/File

        1. {initials} {datetimeStamp} {startOfNoteText} - Revision notes sub-sub-sub-block

          1. {noteText}

          2. Attached Files - Attachment file list block, a table with following columns, with button +File

            • Type - File type

            • Author - Who uploaded

            • Date - Date/time stamp

            • Description

            • Filename

  8. References - Sub-header

  9. Links - Links block(including dossiers?)

  10. Subscribers - Subscribers block

  11. Transmittals - Transmittals block

Issues:

  1. See transmittal detail and how the files are displayed. Will it still be possible to easily transmit notes attachments files (instead of working files)?

  2. Editing of Revision blocks (see *** above): how to handle editing of individual notes? Probably best to have a separate Edit button on each Note.
  3. Clicking on Document Revision N in a List should open detail screen with Revision block and sub-block for Revision N open.

Task Detail Layout

  1. Task - {Type} {Code} - Page Title

  2. Identification {Title} - Task Identification block.

    • Type - Task Type

    • Code - Task Code

    • Title - Task Title

    • Issuer

    • Date - Date/time stamp

    • Classification fields assigned to identification block (for the given data type)
      • (Summary) - define description as a classification field assigned to identification block

  3. Folder {folderPath} - Folder block

  4. Responsibilities and Due Dates - Revision task sub-block

  5. Classification - Task classification block

  6. Properties - Task data block. Only displayed if data fields are defined

  7. Notes - Sub-header

  8. Notes block with button +Note/File followed by zero or more of the following:

    1. {initials} {datetimeStamp} {startOfNoteText} - Note sub-block

    2. {noteText}

    3. Attached Files - Attachment file list block, a table with following columns:

      • Type - File type

      • Issuer - Who uploaded

      • Date - Date/time stamp

      • Description

      • Filename

  9. References - Sub-header

  10. Links - Links block(including dossiers?)

  11. Subscribers - Subscribers block

  12. Transmittals - Transmittals block

Transmittal Detail Layout

  1. Transmittal - {Type} {Code} - Page title.

  2. Identification {status} - {title} - Identification block

    • Type - Transmittal type

    • Code - Transmittal code

    • Title

    • Status {dateAndTime} - pending, scheduled, sent, error. Date and time suppressed if status is pending

    • Classification fields assigned to identification block
  3. Folder - Folder block

  4. Responsibilities and Due Dates

  5. Classification - Classification block if defined

    • Classification fields assigned to Classification Block
  6. Properties - Properties block if defined

    • Classification fields assigned to Properties block
  7. Message - sub-header

  8. Message - Block. Header text present or not?

    1. Header - sub-block

      • Issuer

      • Date - Date only. No time. Only set if status is not pending

      • To

        • Initials - Last name, First name, primary email address

      • CC

        • Initials - Last name, First name, primary email address

      • BCC

        • Initials - Last name, First name, primary email address

      • Subject: {projectCode} Transmittal {type} {code} {title} - Read-only in edit screen

    2. Text - sub-block

    3. Attachments - sub-block. Contains a table (no column headers) with the following columns:

      • {sequenceNumber}

      • {documentCode}-{revisionCode}

      • {title}

      • Revision File or Note Attachment

      • {fileType}

      • {documentCode-revisionCode-sequenceAlpha} or {fileNamePrefixedByDocumentCode} - for respectively Revision File or Note Attachment

Issues:

Dossier Detail Layout

  1. Identification

  2. Items - Sub-header

  3. Revisions - Sub-sub-header. List with the following columns

    • Resource - Contains: {documentRevisionCode}

    • Resource Type - Contains: Revision

    • Description - COntains {revisionTitle}

  4. Tasks - Sub-sub-header?

    • todo

  5. Users - Sub-sub-header?

    • todo

User Detail Layout

  1. Profile

  2. Classification

  3. Data

  4. Quick Links

  5. Email Addresses

Issues:

  1. Currently the User Detail page is displayed in a two-column format
  2. Currently the blocks titles/uses do not relate very well to the other blocks in other detail screens

Suggestions:

  1. Consider the following blocks:
    • Identification - Name, etc.

    • Place in Organization

    • Email addresses

    • Classification

    • Data

    • Access Privileges - Rights and responsibilities?

File Detail Layout

  1. File ID={fileId}

  2. File Properties

Issues:

  1. Currently the blocks titles/uses do not relate very well to the other blocks in other detail screens

Edit Screens

Document Edit Layout

Task Edit Layout

Transmittal Edit Layout

Dossier Edit Layout

User Edit Layout

File Edit Layout

List Screens

Document List Layout

Task List Layout

Transmittal List Layout

Dossier List Layout

User List Layout

File List Layout

V2ScreenLayouts (last edited 2014-01-27 12:20:36 by gw)

Copyright 2008-2014, SoftXS GmbH, Switzerland