--- title: Activate Request Queue slug: activate-request-queue createdAt: 2025-06-11T20:26:19.221Z --- Activate has the ability to view open jobs for a task (or set of tasks) as a queue. This can allow business users to manage the open jobs as a 'queue'. Common actions include:- - View common Properties for the open jobs as a list - Search open jobs by these properties - Assign Jobs to specific users - Set custom data on the Job for the purposes of fulfilment. Activate has an example of this at //Tasks/Services/Order/Managed. These tasks are designed to be used as 'Order Processes' for services instead of the 'Service Desk Ticket' order process. ## Accessing the Queue The queue is normally accessed from a link. This link could be on the Home Page or on a Toolbar. The Services/Order/Managed queues are accessed from //Tasks/System/Tasks/Jobs/Web.Toolbar. Below is the definition for this.               \ | | | | -------------- | -------------------------------------------------------------------------------------------------------------------------------- | | Property | Description | | Link | This can be a Task or a Root of a set of Tasks. | | StartPage | BrowseInstances - This tells the system to start managing the Jobs or the Tasks rather than show the properties or run the task. | | Browse | This tells the system to Browse the Tasks if there are multiple values. | | ExtendedRights | Access\:VIEW-SELF - this means the button will only show if the user as rights to view jobs other than their own. See below. | ## Security A user must have 'VIEW' rights on the task to be able to view the jobs in the queue for that task. By default, users have 'VIEW' rights for SELF (meaning their jobs only) - so they will not be able to view the queue. Users must be granted VIEW access to be able to view the queue. For example, 'Service Desk' may be granted 'VIEW' rights at the root //Services/Order/Managed - this woudl enable the Service Desk members to view all Jobs for tasks under that root. The 'Procurement Managers Role' may only be granted access at //Services/Order/Managed/Procurement Order. Therefore, when they click on the link above, they do not have access to the root, so the system will attempt to find a sub-task that they do have rights to (ie Procurement Order). If the user has access to multiple sub-tasks (queues) (ie Procurement and Building) they will be presented with a selection and they must select which task (queue) they wish to view to jobs for. ## Properties It is assumed that all jobs that can be viewed as a queue have a common set of properties. These properties can be searched and shown in the selection list as required. All Jobs under //Tasks/Services/Order/Managed are assumed to have a common set of properties that are managed and viewed. The default queue form consists of three major components. - Web.Instance.ToolBar - this has the common actions for managing the queue - Web.Instance.Search - this web form has the form a setup for allowing users to search the queue - Web.Instance.List - this defines the columns that are shown in the queue ### Additional Properties The queue can also manage additional information against each job for the purposes of the queue only. The example properties are:- - AssignedUser - each job can be assigned a specific user that is handling the job/request - Status - a manual status that can be assigned to the request - this is visible to the user in the job view - TargetDate - a manual estimated completion date - Comments - additional comments that are shown to the user in the Job view. For example, "Supplier delay - will be at least 2 weeks". These are updated on the 'ApprovalForm' for the task. ### Web.Instance.ToolBar The default tool bar has links to common queries and allows the users to quickly query the queue. Example queries include - Jobs assigned to me - Unassigned Jobs - All Pending Jobs The queries are defined in the Web.Instance.Search definition. ### Web.Instance.Search This form is used to define the search form for the queue and the queries for the form. It uses standard Activate properties search syntax and a standard form. Additional standard queries can also be defined (as above) for the purposes on use from a toolbar link. ### Web.Instance.List This property overrides the columns that are shown in the Queue List. It is a standard Activate table column definition with a Job for each row. ## Request Queue Task Set up Each Task that is being managed as a queue will have the following attributes. - A Workflow Approval step that waits the resolving team to action the request. - A custom ApprovalForm to allow the resolver to change specific properties for the request/job. - A Web.Job.View can be provided that shows specific information to the user from the additional properties. There are also a number of overrides in the Web.Wizard to enable different functionality.   \     \       \ \ **- Name the decline button 'Cancel Request'**         \ \ **- Name the approve button 'Complete Request'**         \ \ **- Disable Save button **         \ \  **- Enable Save on Ribbon**        \ \ **- Allow the user to add notes to the request**         \ \ **- Allow the user to suspend the request**         \       \ \System/Form.aspx\ **- Once approved move straight to the ResponseForm below rather than return to the queue**     \     \       \Send Response Email       \       \
=//Job/ResponseForm\
      \Cancel\     \   \ ## Tasks/Services/Order/Managed/Service Request This task is set up to emulate a simple Service Desk Request Queue. It allows a Request Type to be set up under //Resources/Service Desk/Categories/Request. To use this Service Request Queue on a Service.  - Set 'OrderProcess' = '=//Tasks/Services/Order/Managed/Service Request'  - Set 'OrderFrom' = Name of Category under //Resources/Service Desk/Categories/Request The Category then has the following properties that can be set - RequestTeam - the Role etc that the request will be sent to - ResponseEmail - an Email template that can be used to automatically respond to the user once the request is complete.