Categories
Best Practice System Best Practices Ivanti Ivanti Administrator

Don’t make this newbie HEAT Request Offering Configuration mistake!

Spread the love

You will be in a world of pain when you try to search, filter, or report on Service Request Parameters. In the example above you can see the unique id for the Approving Manager for example is combo_10. That’s not meaningful now is it.

Spread the love

Best Practice for designing Request Offerings is to always set a Unique ID for your Request Offering form controls.

Unique ID plays a critical Design & Architecture Role

Unique ID is the Parameter Name which in turn is used for searches, filters, and reporting for Service Requests.

Don’t Do This!

What if you don’t set unique id? You will be in a world of pain when you try to search, filter, or report on Service Request Parameters. In the example above you can see the unique id for the Approving Manager for example is combo_10. That’s not meaningful now is it.

You always want to set a your Unique ID to a meaningful name.

Do That!

But that’s not all… You have many request offerings which have many service request parameters. So you need to use consistent unique id’s across all your request offerings.

Use a Data Dictionary for your Service Request Parameters and use it whenever you’re defining Unique IDs to look up existing Unique IDs and to add new ones.

Data Dictionary

Contact me for a copy of my Data Dictionary!

By Ivanti Neurons Consultant

Ivanti Best Practices & Latest Solutions by Ivanti Consultant and Systems Developer providing Ivanti Professional Services for Ivanti Neurons, Ivanti Service Manager (formerly HEAT by Frontrange) and Asset Manager since 1996 in the ITxM Space (ITSM, IT Service Management, ITAM, IT Asset Management) in the US, Canada, US, Europe, Asia, Australia, New Zealand; former Kifinti Solutions Consultant