What is the purpose of template keys in IGEL UMS?


So I took a look at template keys and value groups today for the first time. And while it sounds good, I don’t see what the difference is between managing 50 profiles vs 50 template key values. It doesn’t seem like I am saving any work?


I have also been struggling to find a good use for them. I think potentially if you have a lot of settings for 1 specific field, you could create template keys for that and create different options slightly quicker. Another option would be better RBAC options. Limit specific people to only be able to modify/create specific settings in a profile.


Example: 20 branches and 20 background pictures. Normally 20 profiles are needed. With templates you need one profile and just have to upload the 20 background pictures.

Second one is language. Only one language profile but in the template you set EN or DE or Swiss German etc.


It could be an incredibly powerful feature if it was improved a little bit. Allow us to use system attributes like IP octets, site values {$Site}, department values, etc – natively without having to add them to a template key and I could get tons of value from it.

Changing background pictures or languages has no relevance in my environment. And I know it can do more than that, but it just isn’t enough in its current implementation.

Continue reading and comment on the thread ‘What is the purpose of template keys in IGEL UMS?’.  Not a member? Join Here!

Learn more, search the IGEL Knowledge Base



Ask a question or comment on the above messasge thread?

Join or log in to the IGEL Community to ask us anything and meet other IGEL customers, partners, and EUC enthusiasts.

Submit a question, or Join Today!


Popular Message Threads


Categories & Tags: