Top of SRM | Index | Table of Contents | Feedback | ![]() |
CORF3000 - Maintain Incoming Correspondence
Purpose |
This form displays a list of all Incoming correspondence sent to Service Request Messaging Mailboxes. |
|
SubSystem | Correspondence | |
Normally Run by | Correspondence Specialist | |
Anticipated Frequency |
As required |
|
Structure | Block | Incoming Correspondence |
Tabs | Message Content | |
Other Details | ||
Attachments | ||
Comments | ||
Buttons | Delete | |
View All or View Unread | ||
Attach To Person Service Request | ||
Create(View) Service Request (SRMF1000) | ||
Create Person Service Request (SRMF2000) |
By default, this form displays all unprocessed correspondence (those with a status of 'UNREAD'). Users with update access to the context Correspondence Type can:
For further understanding of Incoming Emails, see Correspondence - Special Topics (CORINTR5). Security restrictions exist. A user is only able to Insert, Update, Delete and Select records from this table when able to perform the operations for the Correspondence Type. This form is accessed from the main menu. |
The Incoming Correspondence block contains:
Tabs Message Content
Other Details
Attachments
Comments
|
Rules/Notes: Validations include:
|
The Incoming Correspondence block. When opening this form, it displays all unprocessed correspondence (those with a status of UNREAD). It is also possible to enquire on Incoming Correspondence records with different statuses and other fields on the form. For further information on the View All/View Unread button, see the first table titled, 'View All' below. |
Rules/Notes: The Include pop list. 'Unlinked Correspondence Only' is the default value. This pop list is used to query the Incoming Correspondence records. If it is 'Unlinked Correspondence Only' , the Incoming Correspondence block will include 'Unlinked Correspondence Only’ ; similar with the other two options. This 'Include’ pop list also operate in conjunction with all type of search (F7/F8 and toolbar initiated searching) - e.g. query on a specific Person ID for all correspondence not attached to a request. The 1st Image (Correspondence to Person) indicates that Person ID is not null. If no Person ID, the image is invisible. The 2nd Image (Potential Person Matches) indicates the existence of any potential Person records or the Person ID is not null. The 3rd Image (Correspondence to Service Request) indicates whether the Incoming Correspondence is attached to Service Requests. The table at the bottom of the page describes the various criteria in which an image is visible or invisible. The four images displayed in this block after the 'Subject' field are (See further information under heading 'Images 1, 2 and 3' below): The 1st image
(i1) is 'Correspondence is Mapped to a Person' The 2nd image
(i2) is 'Potential Person Matches Exist' The 3rd image
(i3) is 'Correspondence is Attached to Service Request' (See 4th image below) The next image
is a paper clip If there is non-person Service Request linked to the context Incoming Correspondence, the Create Service Request button will change to View Service Request. |
The Person Service Request block. |
Rules/Notes: The Attach Corresp. and Remove Corresp. check boxes are for attaching or removing correspondence to the request. The image after the Target Response Date and before the Attach Corresp check box is the 'Request Attached to Correspondence' image. The
4th image (i4) is 'Attached Correspondence' If no records are created or deleted, a warning message showing that no records are attached or detached will be displayed. This message fires when the user presses the 'OK' button that results in no records are attached or detached. The message text will be 'No records are attached and detached'. |
The Service Request Enquiry Detail block is only a display block. | Rules/Notes: |
The Incoming Correspondence Potential Person block is only a display block. | Rules/Notes: |
The Message Content tab. | Rules/Notes: The 'Open Message' button takes the user to CORF2710 - Incomingl Message Detail to display the full details of the selected Incoming Correspondence. |
The Other Details tab. |
Rules/Notes: The Find Person button is always visible. The second button, Potential Person Matches is enabled when there are potential Person records and takes the user to the 'Incoming Correspondence Potential Person block. When the 'Select' button is selected, the context Incoming Correspondence record will be populated with the selected Person ID and the form will close. |
The Attachments tab. | Rules/Notes: The 'Open' button opens a new browser window and displays attachments to the correspondence |
View All
The View All and View Unread buttons operate independently of any other search criteria that the user may enter - the buttons should only be used 'globally'. For example, if a name is entered in Sender Name and the user then selects View All, then the value in Sender name is ignored and the query returns all READ and UNREAD correspondence, not just for the specified person. If a user wanted to view all correspondence for a specific person, they would need to perform a standard query on Sender Name with NULL status.
Button Label | Pop list Include | Action |
View All | Unlinked Correspondence Only | Query incoming correspondence block where s_correspondence_status = ‘READ’ or “UNREAD’ and record(s) do not have Service _Request (person or non-person) attached |
View All | Linked Correspondence Only | Query incoming correspondence block where s_correspondence_status = ‘READ’ or “UNREAD’ and record(s) have Service _Request (person or non-person) attached |
View All | Linked & Unlinked Correspondence | Query incoming correspondence block where s_correspondence_status = ‘READ’ or “UNREAD’ |
View Unread | ‘Unlinked Correspondence Only’ or ‘Linked Correspondence Only’ or ‘ Linked & Unlinked Correspondence’ | Query incoming correspondence record where s_correspondence_status = ‘UNREAD’ |
Images 1, 2 and 3
Incoming Correspondence Person ID Populated | Potential Person Record/s Exist |
Service Request Attached | Image 1 Correspondence To Person | Image 2 |
Image 3 Correspondence to Service Request |
---|---|---|---|---|---|
Yes | Yes | Yes | Visible | Invisible | Visible |
Yes | Yes | No | Visible | Invisible | Invisible |
Yes | No | Yes | Visible | Invisible | Visible |
Yes | No | No | Visible | Invisible | Invisible |
No | Yes | Yes | Invisible | Visible | Visible |
No | Yes | No | Invisible | Visible | Invisible |
No | No | Yes | Invisible | Invisible | Visible |
No | No | No | Invisible | Invisible | Invisible |
Field Source | Prompt | Display Type | Comments |
---|---|---|---|
Incoming Correspondence Block | |||
N/A | Include | Pop list | Non database field, initially value is 'Unlinked Correspondence Only'. This pop list is used to query the Incoming Correspondence records. |
ICOR.REFERENCE_NUMBER | Reference Number | Text Item | Located on Incoming Correspondence block |
ICOR.SENDER_NAME | Sender Name | Text Item | Located on Incoming Correspondence block |
ICOR.RECEIVED_DT | Date Received | Display Item | The date component of ICOR.RECEIVED_DT. Format is DD/MM/YYYY. Located on Incoming Correspondence Block |
ICOR.RECEIVED_DT | Time | Display Item | The time component of ICOR.RECEIVED_DT, Non query field. Format is HH24:MI, Located on Incoming Correspondence Block |
ICOR.S_CORRESPONDENCE_STATUS | Status | Pop list | Located on Incoming Correspondence Block |
CORD.SUBJECT | Subject | Display Item | Value obtained on Post-query trigger from table CORRESPONDENCE_DTL |
N/A | No Prompt | Item | Image 1. Located on Incoming Correspondence block. See example above |
N/A | No Prompt | Item | Image 2. Located on Incoming Correspondence block. See example above |
N/A | No Prompt | Item | Image 3. Located on Incoming Correspondence block. See example above |
N/A | No Prompt | Item | Image 4. Located on Incoming Correspondence block. See example above |
CORD.MESSAGE_CONTENT | Message Content | Display Item | Value obtained on post-query trigger from CORD. MESSAGE_CONTENT . Located on Tab Message Content |
ICOR.PERSON_ID | Person ID | Item | Item located on Tab Other Details |
PDV.CONTEXT_BLOCK_NAME | No Prompt | Display Item | Value obtained on post_query trigger from view PERSON_DISPLAY. Located on Tab Other Details, next to the two buttons |
ICOR.CORRESPONDENCE_TYPE | Correspondence Type | Text Item | Item located on Tab Other Details |
CORT.DESCRIPTION | No Prompt | Display Item | Value obtained on Post-query trigger from table CORRESPONDENCE_TYPE. Item located on Tab Other Details, next to Correspondence Type |
ICOR.SENT_DT | Date Sent | Text Item | Item located on Tab Other Details |
ICOR.SENDER_ADDRESS | Sender Address | Text Item | Item located on Tab Other Details |
ICOR.SENDER_REPLY_TO | Reply to Address | Text Item | Item located on Tab Other Details |
CDA.FILENAME | File Name | Display Item | Item located on Tab Attachments |
ICOR.COMMENTS | Comments | Text Item | Item located on Tab Comments |
Incoming Correspondence and Person Service Request Block | |||
ICOR_REFERENCE_NUMBER | Reference Number | Display Item | This field is copy from icor.reference_number. Item located on Incoming Correspondence section |
ICOR.RECEIVED_DT | Date Received | Display Item | This field is copy from icor.received_dt Format TO_CHAR (icor.received_dt), ’DD/MM/YYYY. Item located on Incoming Correspondence section |
ICOR.RECEIVED_DT | Time | Display Item | This field is copy from icor.received_dt Format TO_CHAR (icor.received_dt,’HH24:MI’). Item located on Incoming Correspondence section |
N/A | Sender Name | Display Item | This field is copy from icor.sender_name. Item located on Incoming Correspondence section |
SERRPV._REQUEST_PERSON_ID | Person ID | Display Item | Display one record at a time. Item located on Incoming Correspondence section |
SERRPV.REQUEST_PRSN_NAME | No Prompt | Display Item | Display one record at a time. Item located on Incoming Correspondence section |
Person Service Request | |||
SERRPV._REQUEST_ID | Request ID | Text Item | Item located on Person Service Request section |
SERRPV.S_SERVICE_REQUEST_CAT | Category | Text Item | Item located on Person Service Request section |
SERRPV.S_SERVICE_REQUEST_STATUS | Status | Text Item | Item located on Person Service Request section |
SERRPV.REQUEST_DT | Request Date | Text Item | Item located on Person Service Request section |
SERRPV.TARGET_RESPONSE_DT | Target Response Date | Text Item | Item located on Person Service Request section |
N/A | No Prompt | Item (Image) | This image is only visible when incoming correspondence linked to the context service request |
N/A | Attach Corresp | Check box | Non database field, initially unchecked. |
N/A | Remove Corresp | Check box | Non database field, initially unchecked. |
Service Request Enquiry Detail Block | |||
ED.ENQUIRY_DETAIL_ID | Enquiry ID | Text Item | Item located on Service Request Enquiry Detail Block |
ED.SERVICE_REQUEST_CAT_TYPE | Enquiry Type | Text Item | Item located on Service Request Enquiry Detail Block |
ED.S_ENQUIRY_DETAIL_STATUS | Status | Text Item | Item located on Service Request Enquiry Detail Block |
ED.DESCRIPTION | Description | Text Item | Item located on Service Request Enquiry Detail Block |
Incoming Correspondence Potential Person Block | |||
ICPPV.PERSON_ID | Person ID | Display Item | Item located on Incoming Correspondence Potential Block |
ICPPV.PERSON_NAME | Person Name | Display Item | Item located on Incoming Correspondence Potential Block |
Last modified on 30 May, 2012 8:15 AM
History Information
Release Version | Project | Change to Document |
11.1 | 1505 | corrected colour and font styles |