Bug 1344520

Description of problem:
The YAML file that is generated when a Service Dialog is exported that has one or more tag control elements contains the category_id of the tag category in the VMDB. If the exported file is imported into another appliance where the tag category has a different category_id in the VMDB no tag category is set on the element. To correct this the user must edit the Service Dialog and manually select the tag category from the drop-down list.

I think the export should use the name of the category instead of the category id. The category name has to be unique and the id will be able to be found through a lookup of the categories. If the category name can't be found then the Service Dialog should act as it does today.

Version-Release number of selected component (if applicable):
5.5.4

How reproducible:
Always (as long as the id of a tag category is different between two VMDB's)

Steps to Reproduce:
1. Install and configure a CF appliance
2. Create a tag category and values on the appliance created in step 1
3. Create a Service Dialog that has a Tag Control element that is set to use the category created in step 2
4. Export the Service Dialog
5. Install and configure another CF appliance. When setting up the database pick a different region number than the appliance created in step 1
6. Create the same tag category and values, on the appliance created in step 5, as was created in step 2
7. Import the Service Dialog exported in Step 4 on the appliance created in step 5.
8. Edit the Service Dialog on the appliance created in step 5. The Category drop-down will be <Choose> instead of the Category that was assigned to the drop-down on the other appliance.

Actual results:
Tag Control element does not have a Category selected.

Expected results:
Tag Control element has the Category selected that was selected when the export was performed.

Additional info:
The easiest way to reproduce this is to use two appliances with their own VMDB and have different Region numbers. It is possible to encounter this even with the region numbers of the VMDB's being the same.