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 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.
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.
At line 7 added 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
At line 8 removed 13 lines
For more information on requests see the page titled [Request Facility|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 Personality, the ‘View All My Requests’ menu item in the Self Service menu calls the WERQ screen (where as in Personality 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 Personality.
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
At line 23 changed one line
There are three tabs in WERQ:
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:
At line 37 changed 2 lines
**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.
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.
At line 40 changed 12 lines
;[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.
;[Sent On|DATE_SENT]:This field identifies
;[From|ACTION_FROM_DATE]: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 'In Progress'|]:This field identifies
;[Complete Request|]:This field identifies
;[Deny Request|]:This field identifies
;[Add Activity|]:This field identifies
!Context
!Activity
At line 59 changed 16 lines
;[Sent On|DATE_SENT]:This field identifies the date the request was sent to the recipient.
;[Sent To|DRV_SENT_TO]:This field identifies the employee the request was sent to.
;[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 'New' and Send|ACT_MARK_AS_NEW]:This is an action button that allows the user to mark the request as NEW and to send the request to the selected recipient.
;[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 Outbox tab.
!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.
;[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|]:This field identifies
;[Type|]:This field identifies
;[Entered By|]:This field identifies
;[Description|]:This field identifies
At line 80 changed 8 lines
;[Sent On|DATE_SENT]:This field identifies the date the request was sent to the recipient.
;[Sent From|IDENTITY_NAME_AND_CODE]:This field identifies the employee who sent the request.
;[Sent To|DRV_SENT_TO]:This field identifies the employee who the request was sent to.
;[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.
;[Description|REQUEST_TEXT]:This field identifies the actual text of the request.
;[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
At line 90 changed 4 lines
;[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.
;[Added On|]:This field identifies
;[Type|]:This field identifies
;[Entered On|]:This field identifies
;[Description|]:This field identifies
At line 87 added 5 lines
[CLEANUP]
[{If var='loginstatus' contains 'authenticated'
At line 96 changed 2 lines
![Notes|Edit:Internal.WERQ]
[{InsertPage page='Internal.WERQ' default='Click to create a new notes page'}]
![Discussion|Edit:Internal.WERQ]
[{InsertPage page='Internal.WERQ' default='Click to create a new discussion page'}]
}]
This page (revision-8) was last changed on 26-Nov-2021 10:22 by jmyersTop