This page (revision-13) was last changed on 26-Nov-2021 10:22 by JEscott

This page was created on 26-Nov-2021 10:22 by JMyers

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
13 26-Nov-2021 10:22 10 KB JEscott to previous
12 26-Nov-2021 10:22 10 KB JEscott to previous | to last
11 26-Nov-2021 10:22 10 KB JEscott to previous | to last
10 26-Nov-2021 10:22 11 KB JEscott to previous | to last
9 26-Nov-2021 10:22 11 KB JEscott to previous | to last REQUEST_FACILITY ==> REQUEST FACILITY
8 26-Nov-2021 10:22 11 KB JMyers to previous | to last
7 26-Nov-2021 10:22 11 KB JMyers to previous | to last
6 26-Nov-2021 10:22 11 KB JMyers to previous | to last
5 26-Nov-2021 10:22 11 KB JMyers to previous | to last
4 26-Nov-2021 10:22 10 KB JMyers to previous | to last
3 26-Nov-2021 10:22 10 KB JMyers to previous | to last
2 26-Nov-2021 10:22 11 KB JMyers to previous | to last
1 26-Nov-2021 10:22 10 KB JMyers to last

Page References

Incoming links Outgoing links
REQUEST FACILITY
REQUEST FACILITY

Version management

Difference between version and

At line 3 added one line
At line 5 added one line
At line 7 added one line
At line 9 added one line
At line 7 changed one line
When to Use Requests
!!When to Use Requests
At line 9 changed 15 lines
 To involve other participants in an approval process.
 To reduce emails and phone calls.
 For changes that users cannot make directly in the product.
 To document additional information that can be attached to a record for future reference.
Features of the Request Facility in ePersonality
Manage all Requests for User - IERQ
The Manage All Requests for User (IERQ) screen has been redesigned 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, and the Archived tab where all completed or cancelled requests are stored.
• Inbox tab
 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.
*To involve other participants in an approval process.
*To reduce emails and phone calls.
*For changes that users cannot make directly in the product.
*To document additional information that can be attached to a record for future reference.
!!Features of the Request Facility in ePersonality
!Manage all Requests for User - IERQ
The Manage All Requests for User (IERQ) screen has been redesigned 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, and the Archived tab where all completed or cancelled requests are stored.
Inbox tab
*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.
**The Context tab will display an embedded form for the request if one has been defined in IMRT.
**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.
At line 26 removed one line
At line 28 changed 4 lines
 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.
*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.
At line 35 changed 2 lines
 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.
*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.
At line 38 removed 2 lines
At line 43 changed 2 lines
Form Toolbar Menu
Form Toolbar Menu
This page (revision-13) was last changed on 26-Nov-2021 10:22 by JEscottTop