Configure the check for the uniqueness of product values

By default, IXIASOFT CCMS checks that product names are unique within a deployment, but you can configure it so that other values in the .product file are unique as well.

For example, consider the following template file for a product:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE product PUBLIC "-//IXIA//DTD CMS Product//EN" "product.dtd">
<product id="id" base="">
	<name/>
	<productmeta>
		<code/>
		<description/>
		<aliases/>
		<productlines/>
		<components/>
	</productmeta>
	<relatedproducts/>
	<releases/>
</product>

The name (specified in the <name> element) must always be unique within a deployment. You can configure the CCMS to check the uniqueness of any other element in the .product file.

You define the list of unique values in the releasemanagement.xml file, inside the <uniquekeys> element. For example, let's say that you also wanted the product code to be unique within a deployment. In this case, you add the following <key> element to the releasemanagement.xml file:

<uniquekeys>
   <key type="PRODUCT" index="index_name" xpath="xpath"/>
</uniquekeys>

Where:

`index_name`	Is the name of the index defined for this field in the Index Definition document.
`xpath`	Is the XPATH of the element that must be unique.

For example:

<uniquekeys>
   <key type="PRODUCT" index="code" xpath="//*[contains(@class, ' product/code ')]"/>
</uniquekeys>

Note: You should make these configuration changes in the Test environment and test them before copying them to the Production environment. In a dedicated SaaS deployment, after testing the changes, ask IXIASOFT Customer Support to copy the changes to the Production environment.

In the TEXTML Administration perspective, connect to your server.
Locate the releasemanagement.xml file in the repository's /system/conf collection.
Check out the file and open it for editing.

Locate the <uniquekeys> element.

In the initial configuration, this field is commented out. For example:

<!-- index is name of index defined in system index -->
<!-- 
<uniquekeys>
   <key type="PRODUCT" index="code" xpath="//*[contains(@class, ' product/code ')]"/>
</uniquekeys>
-->

If necessary, uncomment the <uniquekeys> element.
Add a <key> element for each product value that must be unique within a deployment.
Save, close, and check in the file.
Inform users of the changes.
The changes will be applied automatically once users close and then reopen their CCMS Desktop. Users can also apply the changes without restarting their CCMS Desktop by clicking IXIASOFT CCMS > Synchronize Configuration. Additionally, have an administrator refresh IXIASOFT CCMS Web so that users will see the change reflected there.