A Task Request is a request for a technician to do something, either in IRM or in some other software. Task Requests are usually created automatically by IRM integration services or other server components. As of IRM v1.9, Task Request is now a Super Category and is supported by the Object Grid.
When creating or editing a Task Request, the following properties are defined:
Name is defined on Task Request creation and can also be edited later
Target Application- can be one of the applications IRM integrates with, or IRM itself.
Variety - type of Task Request, can be one of the following. Note that not all varieties apply to every integration service.
Create - Create the set of objects indicated by the objects or object Names and type Name fields in the given target Application. For Linkware, an incoming Task Request with object Names and a type Name is set.
Review - Review the set of objects indicated by the objects or object Names.
Update - Update the set of objects indicated by the objects or object Names.
Test - Test the set of objects indicated by the objects or object Names. For Linkware, we expect to have outgoing Task Requests for technicians to test a set of Cables given in the "objects" field.
Action required in column indicates which application or hardware needs to be used in order to complete the Task Request (that is, Linkware, ServiceNow, CommScope, IRM, etc.)
Test Setup is a test configuration item defined in Linkware Live; it is also selected when creating a Task Requestand can be changed later
User and Time Created are populated automatically by IRM.NOTE: By default, the grid is sorted by Time Created, but sorting can be done on all columns.
Lifecycle Stage indicates what is currently happening with the Task Request and what can or should be done next.
Below is an example of the Task Request Properties General tab:
o
The Subtasks tab lists any lower-level Task Requests associated with the current Task Request. Currently Subtasks are used only in the CommScope integration and are generated automatically by the CommScope integration service.
Note: While Task Request is a general-purpose mechanism, specific semantics are defined for each Target Application and Variety combination. In other words, a specific Target Application may only support certain Varieties. See the documentation for various IRM integration services for further details.
o