FS 295942 LD-8QNKTV Implement Supervisor Message Handling
DHL
Implement Supervisor Message Handling
CALIDUS Portal
1st Mar 2012 - 0.1
Reference: FS 295942 LD-8QNKTV
Contents
Functional Overview
Client Requirement
Implement Supervisor Message Handling within CALIDUS Portal and Implement Problem Resolution emails within Portal As per FS 294817, SCR-294817-6: Implement Supervisor Message Handling within CALIDUS Portal & SCR-294817-7: Implement Problem Resolution emails within Portal. Please take under consideration all comments for this section from attached "CT Global Order Well v0 3 - initial spec.rtf"
Solution Overview
The CALIDUS Portal Web Application will be modified to include Message Creation and Message Processing pages which will allow the user to perform the following:
- Create a message (email) to report an Issue/Problem.
- Add additional messages onto the same problem thread.
- Show the message thread/history
- Respond to a user problem (admin only)
- Close a message thread (admin only)
- Re-Open a problem thread (admin only)
See the Functional Description for details.
Scope
- A new Calidus Portal table PORTAL_MESSAGES will be created to hold the messages.
- A new EMAIL_ADDRESS field will be added onto the PORTAL_USERS table to hold the users email address.
- A new EMAIL_ADDRESS field will be added onto the PORTAL_GROUPS table to hold the groups admin email address(es).
Functional Description
A new page within CALIDUS Portal will allow the entry of an email message from the inbound/outbound processing pages described elsewhere and the message processing page described later in this document.
The page will display a header section with relevant information - for all messages the message type, status ('open') and user and then specific information dependent on the message type e.g. for an order message the owner/order number.
Under the header will be the email entry section. This will consist of the following fields:
- From - the email address from i.e. the email address of the user raising the message
- To - this will be the admin email address from the users group and if different the originator of the message i.e. the from address <as the message will not be sent by the user - TBC>.
- Cc - an additional box so the user may include other emails they wish to send the message to.
- Subject - the subject for the email.
Note: The From and To boxes will in nearly all circumstances be pre-populated, and non-amendable. The subject will only be editable on the initial creation of a message thread, for all responses and additional messages on the thread, it will be read-only to ensure the thread subject is consitent.
The final section will be a series of buttons:
- Send - this will send the message, leaving the status of the message 'Open', and will take the user into the Message Processing page which will automatically show the message thread.
- Send & Close - this will only appear for admin users. It will send the message and set the stauts of the original to 'Closed' so that the message thread can no longer be added to.
- Cancel - this will not send the message and will return the user to the previous page.
Appendix A: Quote & Document References
Cost Details | ||||
Activity | Estimate No. of Days |
No. of Days | Rate per Day (£) | Cost (£ Exc. VAT) |
Requirements | 0.00 | 0.00 | 525 | £0.00 |
Change Request Evaluation | 0.00 | 0.00 | 525 | £0.00 |
Functional Specification | 1.50 | 1.50 | 525 | £787.50 |
Technical Specification | 0.00 | 0.00 | 525 | £0.00 |
Development | 4.00 | 4.00 | 500 | £2,000.00 |
Testing and Release | 1.25 | 1.25 | 500 | £625.00 |
Implementation | 0.00 | 0.00 | 500 | £0.00 |
Project Management | First argument to "number_format" must be a number. | First argument to "number_format" must be a number. | 500 | £First argument to "number_format" must be a number. |
TOTAL | First argument to "number_format" must be a number. | First argument to "number_format" must be a number. | £First argument to "number_format" must be a number. |
Estimate excludes training, release to live and go live support. |
A.1 References
Ref No | Document Title & ID | Version | Date |
1 |
A.2 Glossary
A.3 Authorised By
OBS | OBS Product Manager | _____________________________ |
DHL | DHL Representative | _____________________________ |