Chuck Tomasi
Tera Patron

My award winning loaner request system is public. I was honored that this entry won first place at the inaugural Innovation of the Year Award at Knowledge '10. After negotiations with my former employer, re-writing the product from the ground up, and a bit of beta testing (thank you everyone)... It is now available from the attachments list below. I hope you find it useful and I look forward to your feedback.

Product Description:

The Loaner Request system manages reservations for multiple types of items and multiple pick up sites (or depots.) The system features flexible configuration properties based on items in your CMDB to offer you a simple reservation management system based on your favorite platform.

Process Flow:

ESS users enter requests using the record producer "Loaner Items". The simplified form prompts for the type of item, start/end dates, which location to pick up the item, where it will be used, and additional comments. The user does not indicate which specific CI is available at request time. The process flow was designed around the same concept as renting a car. The customer indicates when they need the car and what type of car, but not the specific car.

Once submitted, the request is entered in the Loaner Request table with an initial state of "Requested". With the help of an advanced reference qualifier, a loaner admin identifies and locates a configuration item of the type requested and available at the desired depot. Once the CI is entered the request is automatically advanced to state Reserved. CI select can also be managed by using the Schedule application under the Loaner Requests to see a timeline of all requests.

Additional states are available to help manage the process of preparing items for disposition (e.g. deployment prep, ready for pickup, checked out, post deployment, closed complete, and closed skipped).

For any items in state "Ready for Pickup", a notification is sent to the requester reminding them to pick up the item at the desired depot 24 hours prior to the reservation start date. (This parameter is configurable with a system property described in the full documentation.)

For any items in state "Checked Out", a notification is sent to the requester reminding them to return the item by the indicated end date 24 hours prior to the reservation end date. (This parameter is configurable with a system property described in the full documentation.)

 

find_real_file.png



If the item is still checked out after the end date, the request list will indicate this with a red background on the end date. Every 24 hours after the item was due back, a notification is sent to the requester letting them know the item is overdue. (This parameter is configurable with a system property described in the full documentation.)

Once the item is returned, the loaner admin changes the state to Closed Complete and the request active field is changed to false, removing it from the default list of requests.

IMPORTANT!!!
Be sure to read the comments below and add this article to your watch list. There are periodic updates.

UPDATE 24-Dec-2013: v4.0 is available for Calgary/Dublin
The ZIP file below contains three files, the update set, the states and the process flow records. After previewing and committing the update set, import the XML from the states and process flow files. These are not captured in the update set so they won't interfere with existing states or process records you may already have.

If you get errors when previewing the update set, accept remote updates on all records.

UPDATE 24-Sep-2012: v3.0 is now available

v3.0 adds the following features:

  • Conflict checking - list only available CIs of a specific class, for a specific time frame, at a specific depot
  • Fixed a bug with the overdue (red) color on the End time on the list field.
  • Created cleaner properties page
  • Removed "Available" status for requests
  • Updated timeline (Schedule) page only show 'active' requests
  • Created "Items" section to the Loaner Request application (on the left nav) to make it easier to manage loaner items
  • Created a basic workflow for a laptop reservation. You can build more complex workflows or choose not to use them at all.
  • Created a loaner task table to help manage the day-to-day process without changing ownership of the loaner request (similar to change/change task)
  • Clean up work on withdrawn requests. If a request is withdrawn, loaner tasks are marked "Closed Incomplete" and the workflow is canceled
  • Added a form UI action link for loaner admins to manually trigger the "Ready to pickup" email rather than waiting for the scheduled job to get to it. This is great for quick turnaround requests
  • Notifications updated to support Berlin release
  • Security (ACLs) redefined for default-deny methodology.
  • Added the following notifications

    • When loaner request comments are updated, Assigned To gets a notification
    • When loaner request comments are updated, Requester gets a notification
    • When a new person is assigned to the request, send a notification to the new person assigned to the request
  • Fixed a bug with the record producer terminating with errors on a blank page. Date checks are now done on the client side and stays on the form page
  • Fixed a date calculation bug in the record producer
  • Overview, installation, and configuration instructions are now available as a series of tutorial videos 
155 Comments
Gauri Sharma
Mega Contributor

Hey Chuck,

 

Thank you for the response, could you please help me to understand whether I can raise a loaner request from service portal like we raise request for Catalog forms from portal.

If it is possible, please guide us to implement.

Thanks,

Gauri

DanielCordick
Mega Patron

Hi Gauri,

both myself and chuck suggested you go the record producer route as this would be the best way to implement the loaner request system into the service portal. 

check out these docs to get you started on creating a record producer 

https://docs.servicenow.com/bundle/orlando-it-service-management/page/product/service-catalog-manage...

Gauri Sharma
Mega Contributor

Thank you Danny and Chuck, We will try to implement the record producer for SP.

Will let you know how is works in our instance.

 

Thanks again,

Gauri

Gauri Sharma
Mega Contributor

Hello Danny/ Chuck,

Thank you for the above suggestion. 

We used record producer for SP and Loaner request can be raised from SP now.

Could you please also help me to map my instance cmdb_ci table with the 'item' field in the loaner request of scoped application.

When I click on 'item' field, blank window pop-ups however the 'item' field configuration we have referenced to cmdb_ci.:

Please find attached screenshots for the reference:

 

find_real_file.png

 

 

 

find_real_file.png

 

 

Thanking in anticipation.

-Gauri

DanielCordick
Mega Patron

Hi Gauri,

If I'm not mistaken, you can go to the list layout option screen and move the Loaner column over to selected

find_real_file.png

 

you will be given the option to set either true or false, Changing the Loaner column to TRUE for the selected CI on the cmdb_ci table should make it available in the "item" reference field. 

 

hope this helps

 

thanks 

Chuck Tomasi
Tera Patron

In addition to Danny's comments, you may also want to configure the Depot field on the list (or form) so each loaner item that has the loaner field set to true, also has a location.

The "Item" field on the loaner form uses the following fields to determine what to display (i.e. how to configure the reference qualifier)

  • Item type (value) matches the CI class (e.g. cmdb_ci_computer)
  • Depot matches the CI's depot
  • CI has "loaner" field set to true
  • Start/end time do not conflict with any other requests (upcoming or overdue)
Arun87
Giga Contributor

Hi Chuck,

When we are trying to create a new loaner request we found that task and workflow is missing. Could you please help me on this how to bring the workflow and tasks are back to the loaner request

Chuck Tomasi
Tera Patron

The laptop workflow is provided as a sample. It's included with the update set. If your update set ran in to issues, check there. 

It really wasn't a very complicated workflow and I don't recommend building new workflows using the legacy workflow editor, but rather Flow Designer. I just haven't had a chance to make a new update set. It's a pretty small effort to build one of these using Flow Designer. Here's a couple videos on how I would rebuild in 2020:

(Re)Building the Loaner Request App - Part 1

(Re)Building the Loaner Request App - Part 2

 

 

Arun87
Giga Contributor

Hi Chuck,

We have created other two custom tables but the workflows are not attached to it. Could you please help me to add the workflows for the custom tables for loaner request in servicenow

Sky1
Kilo Explorer

Hi Chuck,

Great application. We cannot wait to implement it. However, I've hit a wall I cannot seem to get over. 

I've followed the guided setup and have successfully configured 95% of everything. Except, I cannot get additional choices in the "What would you like to reserve?" dropdown menu. I was able to successfully connect "Laptops" to the drop down menu using the "cdmb_ci_computers" table.

I've attempted to add "Mobile Devices" to the dropdown menu but failed. I did create a table named "u_cmdb_mobile_phone" and linked the "Hardware" extension table. I created a module named "Mobile Device" and set the table to "u_cmdb_mobile_phone". From the Loaner Request menu, "Mobile Device" is visible under the "Items" menu. Additionally, I created a configuration item then set the loaner status to "True". That option is visible in the "Mobile Device" option under "Items". 

So, could you give me insight as to why I cannot get "Mobile Device" to appear in the "What would you like to reserve?" dropdown menu. I have a suspicion it's a configuration within the "u_cmdb_mobile_phone" or the "Mobile Device" module but I'm not sure where. 

Thanks,
Skylar