V2 Screen Layouts

V2Master | V2HighLevelDesign

• Contents

  1. V2 Screen Layouts
  2. To Do
  3. Work Status
  4. General Notes
     1. Process
     2. Terminology
     3. Block Ordering
  5. Detail Screens
     1. Document Detail Layout
     2. Task Detail Layout
     3. Transmittal Detail Layout
     4. User Detail Layout
     5. File Detail Layout
     6. Dossier Detail Layout
  6. Edit Screens
     1. Document Edit Layout
     2. Task Edit Layout
     3. Transmittal Edit Layout
     4. User Edit Layout
     5. File Edit Layout
     6. Dossier Edit Layout
  7. List Screens
     1. Document List Layout
     2. Task List Layout
     3. Transmittal List Layout
     4. User List Layout
     5. File List Layout
     6. Dossier List Layout

To Do

1. Review button placement and titles on detail screens
2. Review block headers and sub-headers (including font size)
3. Review menu titles for configuration related menu items
4. Review for correctness [ALL]
5. Add buttons with button titles, tune button colors (should be less glaring)
6. Check widths of selects, to be consistent across screens
7. Check links for consistent actions
8. We plan to go to a single edit screen, instead of separate edit screens for the object data and classification.
9. File Category will be internal only (user should not see)
10. Introduce different header background colors for each object (using subtle tones). One or a combination of the following:
    1. Apply color based on object type
    2. Apply color based on block type

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
   • Users
   • Files
   • Dossiers
   • 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 block types are relevant to all Objects.

1. {Object} {Type} {Code} - Default page title

2. 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

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

   • Identification block classification fields (for the given data type)

     • (Description/Summary) fields should be defining as classification fields

3. Folder Block - for Team Members OBS Block, with multiple entries

4. Responsibilities and Due Dates Block

5. Classification Block - Only displayed if classification fields are defined or if one of the fields is as required

6. Properties Block - Only displayed if classification fields are defined or if one of the fields is as required

7. Message Block - For Transmittals

8. Revision Blocks - For documents, includes Files and Note sub-blocks

9. Note Blocks - For tasks

10. Reference Blocks: - Sub-header

11. Links Blocks

12. Subscribers Blocks

13. Transmittals Blocks

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 {lowestLevelFolderPath} - 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 - if required, define as a classification field assigned to the 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. Compare with transmittal detail screen layout and see 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 - if required, define as a classification field assigned to the identification block

3. Folder {{lowestLevelFolderPath} - Folder block

4. Responsibilities and Due Dates - 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 - Block with button +File. 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 {lowestLevelFolderPath} - 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, with display of time. The date is not set if status is 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:

User Detail Layout

1. Project Team - {Type} - {firstName lastName} - Page title.

2. Identification {firstName lastName}

   • Type - Team Member Type

   • First Name

   • Last Name

   • Initials

   • Primary Email

   • SecondaryEmail - if this is considered required, otherwise as classification field located in Properties

   • Company - as informational text

   • Classification fields assigned to identification block

3. Project Organisation {lowestLevelOrgansiationalBreakdown} - Organisation block

   • Project Position - displayed same as Folder is displayed

4. Classification - Classification block if defined

   • Classification fields assigned to Classification Block

5. Properties - Properties block if defined

   • Classification fields assigned to Properties block

6. Access Privileges - access privileges and responsibilities

   • Login / enabled Y/N

Issues:

1. Display the User Detail page in a single column format, with blocks consistent with other object detail screens
2. Quick Links block not needed, all links are already in banner menu

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

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

Edit Screens

Document Edit Layout

Task Edit Layout

Transmittal Edit Layout

User Edit Layout

File Edit Layout

Dossier Edit Layout

List Screens

Document List Layout

Task List Layout

Transmittal List Layout

User List Layout

File List Layout

Dossier List Layout