This is version 1 2 3 4 5 6 7 8 . It is not the current version, and thus it cannot be edited.

Back to current versionRestore this version

MANAGE ALL REQUESTS FOR USER#

The Manage All Requests for User (WERQ) 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.

The Manage All Requests for User (IERQ) screen has been designed to make it function more like an email client.

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

This field identifies

From

This field identifies

Status

This field identifies

Type

This field identifies

Priority

This field identifies

Synopsis

This field identifies

Action Req'd

This field identifies

Description

This field identifies

Mark as 'In Progress'

This field identifies

Complete Request

This field identifies

Deny Request

This field identifies

Add Activity

This field identifies

Context#

Activity#

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

This field identifies

Status

This field identifies

Type

This field identifies

Priority

This field identifies

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

This field identifies

Type

This field identifies

Entered By

This field identifies

Description

This field identifies

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

This field identifies

Sent From

This field identifies

Sent To

This field identifies

Status

This field identifies

Type

This field identifies

Priority

This field identifies

Synopsis

This field identifies

Description

This field identifies

Activities#

Added On

This field identifies

Type

This field identifies

Entered On

This field identifies

Description

This field identifies

CLEANUP