[{TableOfContents }] 

!!!MANAGE ALL REQUESTS FOR USER

The Manage All Requests for  User ([IERQ]) screen works like an email client with an Inbox, Outbox, and Archived requests section; this provides a familiar interface for users and encourages them to use requests more often in their daily work. A menu has been added to the form toolbar to make it easier for users to create new requests for a subject, as well as provide the convenience of viewing all relevant requests. Embedded forms which show the context of each request will be visible on [IERQ] such that when a user is viewing outstanding requests; all information is available on [IERQ] and opening other screens to understand the source of the request is no longer necessary.

Although requests are similar to email, there is no similar way to respond to a request; requests should not be replied to with another request.  Instead, a user can add an activity to the current request and as long as the request remains open, the sender can see it and all activities in the Outbox of their [IERQ] screen

A user can complete or deny requests assigned to them. If a request is not assigned to them, then at most they can add an activity to the request for others to see.

For more information on requests see the page titled [Request Facility|REQUEST FACILITY]


There are three tabs in IERQ: 
*Inbox tab where incoming requests are received
*Outbox tab where new requests can be created and sent to an employee
*Archived tab where all completed or canceled requests are stored.

The definition data for the Manage All Requests for User screen is stored in the [P2K_AM_REQUESTS] and [P2K_AM_REQUEST_ACTIVITIES] tables.

!!Inbox 
The Inbox:
*Contains all requests received by the user which are still ‘open’.
* Provides the ability to complete or deny requests, as well as the ability to change the status from New to In Progress.
* Users can respond to a request by adding activities, they would not respond by sending another request.
* If the request type was defined as requiring action the Action Required toggle will be checked.
* The bottom portion of the screen contains two tabs; Context and Activities.
      o The Context tab will display an embedded form for the request if one has been defined in [IMRT].
      o The Activities tab is a view of all activities for the request. The date the activity was added, by whom, the type of activity and the text of the activity can all be seen in this tab. 
      
;[Sent On|DATE_SENT]:This field identifies the date the request was created. 
;[From|IDENTITY_NAME_AND_CODE]:This field identifies which employee created the created the request. 
;[Status|REQUEST_STATUS]:This field identifies the status of the request.
;[Type|REQUEST_TYPE_CODE]:This field identifies the type of request that was created. 
;[Priority|PRIORITY]:This field identifies the request's priority. 
;[Synopsis|REQUEST_SYNOPSYS]:This field identifies the synopsis of the request. 
;[Action Req'd|REQUIRES_ACTION]:This field identifies if action is required of the recipient of the request. Requests may vary in nature, some require action to be taken and others are comments regarding a record.   
;[Description|REQUEST_TEXT]:This field identifies the actual text of the request.
;[Mark as 'In Progress'|ACT_MARK_IN_PROGRESS]:This is an action button that allows the request recipient to mark the request as in progress. 
;[Complete Request|ACT_COMPLETE_REQUEST]:This is an action button which allows the request recipient to complete the request by changing the [status|REQUEST_STATUS] to 'completed'. Once completed, the request will be transferred to the Archived tab.
;[Deny Request|ACT_DENY_REQUEST]:This is an action button which when pressed will deny the request. The [status|REQUEST_STATUS]will change to Denied, and the request will be transferred to the Archived tab. 
;[Add Activity|ACT_ADD_ACTIVITY]:This is an action button that allows the request recipient to add an activity to the request. When pressed the [Request Activity|MMRA] dialog will appear prompting the user to select an [action type|ACTION_TYPE] and allow them to add text describing the activity. Once completed, the activity will be visible in the Activity tab within the Inbox tab.  

!Context
If an [embedded form|EMBEDDED FORMS] was associated to the [Request Type|REQUEST_TYPE_CODE] in [IMRT], this section will display the [embedded form |EMBEDDED FORMS]. 

!Activity
;[Added On|CREATE_DATE]:This field displays the date the activity was created. 
;[Type|ACTION_TYPE]:The type of action fulfilled of the request activity is displayed here. 
;[Entered By |IDENTITY_NAME_AND_CODE]:The name and person code of the individual who entered the activity is displayed here. 
;[Description|REQUEST_ACTIVITY_TEXT]:The text of the activity is displayed in this field. 

!!Outbox
The Outbox tab:
* Contains all requests sent by the user which are still ‘open’.
* Similar to Inbox features, except not allowed to cancel or complete request.
* If a request was created with a status of ‘Draft’, the creator of the request can change the status to New and send the request to the directed individual.
* Activities can also be added here and the details of the activity are listed in a table below the request.

;[Sent On|DATE_SENT]:This field identifies 
;[Status|REQUEST_STATUS]:This field identifies 
;[Type|ACTION_TYPE]:This field identifies 
;[Priority|PRIORITY]:This field identifies 
;[Synopsis|REQUEST_SYNOPSIS]:This field identifies 
;[Action Req'd|]:This field identifies
;[Description|]:This field identifies 
;[Mark as 'New' and Send|]:This field identifies  
;[Add Activity|]:This field identifies 
!Activity
;[Added On|CREATE_DATE]:This field displays the date the activity was created. 
;[Type|ACTION_TYPE]:The type of action fulfilled of the request activity is displayed here. 
;[Entered By |IDENTITY_NAME_AND_CODE]:The name and person code of the individual who entered the activity is displayed here. 
;[Description|REQUEST_ACTIVITY_TEXT]:The text of the activity is displayed in this field. 


!!Archived
The Archived tab:
* Contains all requests sent or received by the user which have been completed or denied.
* This tab is a view only of the historical requests, therefore the user does not have the ability to modify the request or its activities. 
;[Sent On|DATE_SENT]:This field identifies 
;[Sent From|]:This field identifies 
;[Sent To|]:This field identifies 
;[Status|REQUEST_STATUS]:This field identifies 
;[Type|ACTION_TYPE]:This field identifies 
;[Priority|PRIORITY]:This field identifies 
;[Synopsis|REQUEST_SYNOPSIS]:This field identifies 
;[Description|]:This field identifies

!Activities

;[Added On|CREATE_DATE]:This field displays the date the activity was created. 
;[Type|ACTION_TYPE]:The type of action fulfilled of the request activity is displayed here. 
;[Entered By |IDENTITY_NAME_AND_CODE]:The name and person code of the individual who entered the activity is displayed here. 
;[Description|REQUEST_ACTIVITY_TEXT]:The text of the activity is displayed in this field. 



[CLEANUP]


[{If var='loginstatus' contains 'authenticated'

----
![Discussion|Edit:Internal.IERQ] 	
[{InsertPage page='Internal.IERQ' default='Click to create a new discussion page'}] 	

}]