MANAGE ALL REQUESTS FOR USER#
The Request functionality in Self Service is very similar to that in the Professional application. Users in Self Service will use the WERQ screen instead of the IERQ screen to review their outstanding requests or to create new requests. The only difference between these two forms is that the WERQ does not have the Context tab or Activities tab as Self Service at this time does not support the use of tabs within tabs. Other than that one difference, both forms have the same functionality.
For more information on requests see the page titled Request Facility.
Self Service Splash Menu##
The Splash menu in Self Service displays the ‘Internal Requests I Need to Respond to’ menu item. This menu item will display on all of the roles associated to the user signed in. This menu item is the VERQ_SPLASH function which will display five new requests at a time, once the status changes from new it will be removed from this window.The ‘Click Here To Access Your Requests’ link will direct the user signed in to their WERQ screen where they can manage all of their outstanding and historical requests.
Self Service Form Toolbar Menu##
Similar to the menu in Wiki, the ‘View All My Requests’ menu item in the Self Service menu calls the WERQ screen (where as in Wiki it calls IERQ). The other difference is that the shortcut keys do not appear in the Self Service menu as these are not supported in Self Service. The dialogs are the same as those called from the menu in Wiki.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.
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 WERQ 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.
There are three tabs in WERQ:
- 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 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
- 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
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
Screen captures are meant to be indicative of the concept being presented and may not reflect the current screen design.
If you have any comments or questions please email the Wiki Editor
All content © High Line Corporation