Skip Navigation LinksALVAO 11.0Extension modulesALVAO Standard HW/SW Request Forms Skip Navigation Links.

ALVAO Standard HW/SW Request Forms

This module supports the process of requesting pre-approved hardware and software.

Technical Requirements

  • ALVAO Asset Management
  • ALVAO Service Desk


In the application ALVAO WebApp - Administration - Licenses select Insert Activation Key and enter the activation key that you obtain from your Alvao system vendor.

On the server where the ALVAO WebApp is installed, run the installation package AlvaoStandardHWSWRequestForms.msi and follow the instructions in the wizard.

The module is only in Czech and is not localized to other languages.

Create a custom HW request form

Copy the Custom/Templates/StandardHwSwRequestForm/StandardHwSwRequestForm_Hw_NewTicket.cshtml file to the Custom/<function_name> folder and the Custom/Templates/StandardHwSwRequestForm/Code/StandardHwSwRequestForm_Hw_NewTicket.cs file to the Custom/<function_name>/Code/ folder. You can rename the files, but name both files (.cshtml and .cs) the same.

  1. In the namespace name at the beginning of the .cs file, replace the trailing "Templates.StandardHwSwRequestForm" with the name of the functionality, i.e. Alvao.ServiceDesk.ServiceDeskWebApp.Custom.<functionality_name>.
  2. If you have renamed the .cs file, change the class name (at the beginning of the file by the keyword class) to <filename>Controller.
The file names of all forms used must be unique. If you use multiple different forms, you need to ensure that the name of the StandardHwSwRequestForm_Hw_NewTicketController class is unique.

Devices offered

In the object tree, first define a list of categories and devices from which users will be able to select devices, e.g.:

  1. HW Request (type HW Request - Catalog)
    1. Notebooks (type HW request - category)
      1. Standard Laptop (type HW Request - Item)
    2. Desktop computers (type HW request - category)
      1. Standard PC (type HW request - item)
    3. Monitors (type HW request - category)
  2. Standard Monitor (type HW Request - Item)

On the form, catalog items (of type HW Request - Item) show users all properties of the objects that have a value filled in, except for the system properties Order, User Groups, and Hidden Properties. You can add additional properties to the HW Request - Item object template as needed to display to users in the catalog.


If you want to record additional properties in the item objects for catalog management purposes, but they should not be displayed to users in the form, in the HW Request - Catalog object in the Hidden Properties property, provide a comma-separated list of these properties, e.g. "Last updated (date), Url in supplier's e-shop".

Categories and items are displayed on the form in alphabetical order by object name. If you want to display objects in a different order, use the Order property. The objects will then be primarily sorted by the value of the Order property in ascending order, with objects that do not have this property filled in being displayed last. Objects with the same value in this property will be sorted secondarily alphabetically by object name.

We recommend writing values in the form e.g. "10 152" to the Price property. Before submitting the request, the total price of the ordered items will then be displayed to the user at the bottom of the form.


If you want to offer some categories or items on the form only to some users, in the User Groups property, provide a comma-separated list of user groups to which the category or item should be offered. The user to whom the devices are intended is the decisive one. The Requester of the request can be someone else. If the User Groups property has an empty value, the object is displayed to all users.


If you need to offer users items with significantly different properties in the catalog, you can define other object types in addition to the system type HW Request - Item. In the form, objects of any type are displayed to requesters as items.

Device images

Create a note in the object log and insert the device image as an attachment. Images must be in JPG or PNG format. The recommended image size is 150x150 px.

If a facility's log contains multiple notes with images attached, the form will display the image from the most recent note. If the note contains multiple images, the most recently inserted image is displayed. If there is no such note in the journal, the object is displayed on the form without an image.

Edit HW Request Form

In the .cs file before starting the LoadPage() function, you can edit the values of the variables:

  1. folderName - enter the name of the folder including the path in the tree that contains each category of devices offered, e.g. "HW request".
  2. categoryObjectKind - specify the type of objects that represent the categories, e.g. "HW Request - Category". Sub-objects of these categories will appear on the form as offered devices. Objects that do not have a categoryObjectKind will not be displayed on the form as category objects (and their subobjects will not be displayed).
    The user can request any child of the object specified by the folderName and categoryObjectKind variables (i.e., even an object that they would not have access to in the Asset Managment tree).
  3. categories - specify the category names (e.g. "Monitors, Laptops") to be displayed on the form. If the variable is empty, all categories are displayed.

The display of objects and their properties can be edited in the .cshtml file. For more information on editing forms, see Custom form for submitting a new request.

Create your own SW request form

Follow the same steps as creating a custom HW request form, but use the Custom/Templates/StandardHwSwRequestForm/Code/StandardHwSwRequestForm_Sw_NewTicket.cshtml and Custom/Templates/StandardHwSwRequestForm/Code/StandardHwSwRequestForm_Sw_NewTicket.cs files.

The form displays software products that are in approved state, for more see product status.

It is not possible to set the display of images for individual products in this form.


For more information on editing forms, see Custom form for submitting a new request.

Service Settings

In ALVAO WebApp - Administration - Service Desk - Services, create a service (for example, IT/Request for New HW), that will use the form, or use an existing one. Use one service for each form. Set up the form for this service.

  1. In ALVAO WebApp - Administration - Service Desk - Services, in the service tree, select the service (IT/New HW Request) and use the Edit - New Request Form command.
  2. Change the Form design section to Custom Form (URL) and set the value to the address used by the request form, for example ~/Custom/<feature_name>/<form_name>.
If the address begins with http or https, it is used as is. Otherwise, the path to the root of the ALVAO WebApp is automatically added to the beginning.

Set the service process. You can use an existing process or create a new one.

The status entered by creating a request must not have any mandatory items.


Did not find what you were looking for? Ask our technical support team.