Template definition with a Template name and Group name which already exists leads to incorrect inventory being collected
search cancel

Template definition with a Template name and Group name which already exists leads to incorrect inventory being collected

book

Article ID: 54448

calendar_today

Updated On:

Products

CA Client Automation - IT Client Manager CA Client Automation

Issue/Introduction

If we create 2 templates definitions with the same template name and/or group name, some problems may occur when the inventory is imported to the database.
The System Engine cannot handle properly this efficiently and this may lead to corrupt template inventory for the machines.

Environment

Client Automation - All versions

Resolution

The following example outlines what is not recommend.

Consider the 2 template definitions named 'Sample1' and 'Sample2.

For template 'Sample1', the template name and group name in the Template Editor is 'TemplateName' & 'TemplateGroup' respectively.

For template 'Sample2', the template name and group name in the Template Editor is also 'TemplateName' & 'TemplateGroup' respectively.

 

In this scenario, there are 2 templates with the same Template name & Group name.

The value of the Template name and Group name in the 'Template Editor' is used as a key by UAM.
Therefore, if you create template definitions with the a Template name and Group name which already exists, UAM cannot handle the template correctly.
Inventoried items from these 2 templates will be mixed in the MDB database.

Attachments