This page (revision-22) 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
22 26-Nov-2021 10:22 8 KB JEscott to previous
21 26-Nov-2021 10:22 8 KB JEscott to previous | to last

Page References

Incoming links Outgoing links
IERQ
IERQ

Version management

Difference between version and

At line 5 changed one line
The Manage All Requests for User (IERQ) screen is used
The Manage All Requests for User ([IERQ]) 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 changed one line
The Manage All Requests for User (IERQ) screen has been designed to make it function more like an email client.
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 9 added 5 lines
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.
For more information on requests see the page titled [Request Facility|REQUEST FACILITY]
At line 16 changed one line
!!Inbox
!!Inbox tab
At line 23 changed one line
o The Context tab will display an embedded form for the request if one has been defined in IMRT.
o The Context tab will display an embedded form for the request if one has been defined in [IMRT].
At line 26 changed 12 lines
;[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
;[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.
At line 40 changed one line
!Activity
If an [embedded form|EMBEDDED FORMS] was associated to the [Request Type|REQUEST_TYPE_CODE] in [IMRT], this section will display the [embedded form |EMBEDDED FORMS].
At line 42 changed one line
!!Outbox
!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.
----
!!Outbox tab
At line 49 changed 16 lines
;[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
!!Archived
;[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.
----
!!Archived tab
At line 68 changed 8 lines
;[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
;[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.
At line 78 removed 4 lines
;[Added On|]:This field identifies
;[Type|]:This field identifies
;[Entered On|]:This field identifies
;[Description|]:This field identifies
At line 96 added 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.
At line 84 removed one line
[{If var='loginstatus' contains 'authenticated'
At line 86 removed 3 lines
----
![Discussion|Edit:Internal.IERQ]
[{InsertPage page='Internal.IERQ' default='Click to create a new discussion page'}]
At line 90 changed one line
}]
----
![Notes|Edit:Internal.IERQ]
[{InsertPage page='Internal.IERQ' default='Click to create a new notes page'}]
This page (revision-22) was last changed on 26-Nov-2021 10:22 by JEscottTop