Layout changes in the new tools

The notes component will be added

• to the account widget as the second tab
• to the transaction widget as the second tab
• with the label "Notes"

The edit fields will also use the notes as per http://iceberg.clubpenguin.net/confluence/display/MS/Account+Details+Tab (Editable Input Field Control).  This means that the notes will also be needed for the summary tab.

Internal storage of the notes will work as follows (Technical details follow)

• All notes will be stored in a note models based on the context that the notes model is in. 
• These models will not be synced and each time a component within the specific context requires notes, a new request will be done. This will be the onclick event in the datagrid since at that moment we will need to know the notes to display them on whatever tab is showing below.  
• The following contexts will have a notes model.
  • Transactions Context
  • Account Context  

The notes model will contain a collection for each type of note, plus a collection of all notes grouped together. There are three notes type:

1)      Account Notes

2)      Financial Notes

3)      Avatar Notes 

NOTE: Financial Notes my be attached to the accounts notes request. In that case, only two separate requests will be needed. Waiting for clarification on this.

Types of Notes Stored in the System

Guest initiated changes

1.      Password
2.      Email
3.      CC Information and billing address changes
4.      Chat Settings
5.      Change subscription (Cancel – change to monthly, etc)

Support team initiated changes

Any changes made to the guests information (avatar, accounts and financial).  Examples include (but are not exhausitive)

• Username changed from ___ to _____ by ___ on such and such a date
• Payment refunded b/c of _reason__ with the extra note of ____
• Bans forgiven

Gathering Notes

On selection of an avatar, a request for financial and avatar notes will be executed.

The result of each search will be a collection of noteVOs.  A noteVO has the following properties

                noteId
                dateTime
                action
                field (example username)
                adminID (0 for guest, otherwise it is the internal id of the support staff member)
                priority (Currently if the note is sticky or not - this will be a number.  0=non-sticky, 10=sticky)
                System or User Note
                type: (Avatar, Financial, Account). (In the future this could grow to many possibilities - most notably flurry, phone and mod reports)

Once the data is returned,  two collections in the notes model will be updated.

1) Collection of notes for the specific type (ie financial)

2) Collection of all notes collaborated together.  This will massage the data by adding the day (in default timezone) so it can be grouped together)

Once the model is updated, the view will automatically update.

Display Notes

Any new notes added to the notes model that are flagged as sticky will display an alert before the user can take any future action on the account.

All notes will be displayed in an advanced datagrid, grouped by date. The following columns displayed are:

 By
 Date
         Action

One or more filter can be applied to the results in the notes datagrid. On filter change, a filter will be applied to the full notes collection within the notes model. The filters are:

                • System Notes
                • Admin Notes
                • By Guest (example guest changed email address)
                • By Admin (CSR changed the email address)
                • Financial Based Notes
                • Account Based Notes
                • General Notes

 Notes will be color coded based on the type of note

1)      Account Notes – Background Color Blue

2)      Financial Notes – Background Color Green

3)      Avatar Notes – Background Color Green

4)   Admin Notes - Background Color Yellow

  
If a note is an admin note, the admin color code will trump the Account and Financial Notes

Notes can be deleted by the note creator or a team lead.

Entering Notes

                Notes can be entered into an account by selecting the add button. A note field will be displayed below the datagrid. The saved note will be saved in the context the widget. (eg, Financial).  The note will be sent to the server as a noteVO

On saving of the note, the server will return the updated noteVO as it is saved.  The client will then push it to the array and rebuild the appropriate models and refresh the view.