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

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
8 26-Nov-2021 10:22 8 KB jmyers to previous
7 26-Nov-2021 10:22 8 KB JMyers to previous | to last
6 26-Nov-2021 10:22 6 KB JMyers to previous | to last
5 26-Nov-2021 10:22 6 KB JMyers to previous | to last
4 26-Nov-2021 10:22 5 KB JEscott to previous | to last
3 26-Nov-2021 10:22 5 KB JEscott to previous | to last
2 26-Nov-2021 10:22 5 KB JMyers to previous | to last
1 26-Nov-2021 10:22 4 KB JMyers to last

Page References

Incoming links Outgoing links
WERQ
WERQ

Version management

Difference between version and

At line 5 changed one line
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.
The Request functionality in Self Service is very similar to that in [{$applicationname}]. 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.
At line 7 changed one line
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
!!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.
At line 9 changed one line
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 ‘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.
At line 11 changed one line
The Manage All Requests for User (IERQ) screen has been designed to make it function more like an email client.
!!Self Service Form Toolbar Menu#
Similar to the menu in [{$applicationname}], the ‘View All My Requests’ menu item in the Self Service menu calls the WERQ screen (where as in [{$applicationname}] 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 [{$applicationname}].
At line 13 changed one line
There are three tabs in IERQ:
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:
At line 43 removed 3 lines
!Context
!Activity
At line 89 removed one line
This page (revision-8) was last changed on 26-Nov-2021 10:22 by jmyersTop