Description of problem:

While ordering the service via API, tag_control array is not getting parsed.

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

How reproducible:
Always

Steps to Reproduce:

1. Create a service catalog and provide a service dialog with values based on tag_control filter.

2. When we pass classificaiton ID in the API query, it gives the response as "Classification::<classification ID>"

3. Now try to pass classification description in the payload and it will give you blank value in the API response

Below is an example:

vmdb_production=# select * from classifications where id='93000000000283';
       id       | description | icon | read_only | syntax | single_value | example_text |     tag_id     |   parent_id    | show | default | perf_by_tag 
----------------+-------------+------+-----------+--------+--------------+--------------+----------------+----------------+------+---------+-------------
 93000000000283 | common      |      | f         | string | f            |              | 93000000000304 | 93000000000165 | t    |         | 
(1 row)

vmdb_production=# select * from tags where id='93000000000304';
       id       |                name                
----------------+------------------------------------
 93000000000304 | /managed/asip_application/0_common
(1 row)



https://<cfmehost>/api/service_catalogs/93000000000002/service_templates/93000000000027

{
  "action" : "order",
  "resource" : {
    "href" : "https://<cfmehost>/api/service_catalogs/93000000000002/service_templates/93000000000027",
    "option_0_asip_vlan" : "middle",
    "name_0_asip_application" : "93000000000283",
    "tag_0_asip_environment" : "bt_dev1",
    "tag_0_asip_role" : "JDK 6",
    "option_0_extra_storage_size" : "5",
    "option_0_extra_storage_path" : "/data"
  }
}

"options": {
        "dialog": {
            "dialog_option_0_cname": "",
            "dialog_option_0_asip_vlan": "middle",
            "Array::dialog_name_0_asip_application": "Classification::93000000000283",
            "dialog_tag_0_asip_environment": "bt_dev1",
            "Array::dialog_tag_0_asip_role": "",
            "dialog_option_0_extra_storage_size": 5,
            "dialog_option_0_extra_storage_path": "/data"
        },




https://<cfmehost>/api/service_catalogs/93000000000002/service_templates/93000000000027
{
  "action" : "order",
  "resource" : {
    "href" : "https://<cfmehost>/api/service_catalogs/93000000000002/service_templates/93000000000027",
    "option_0_asip_vlan" : "middle",
    "name_0_asip_application" : "common",
    "tag_0_asip_environment" : "bt_dev1",
    "tag_0_asip_role" : "JDK 6",
    "option_0_extra_storage_size" : "5",
    "option_0_extra_storage_path" : "/data"
  }
}


 "options": {
        "dialog": {
            "dialog_option_0_cname": "",
            "dialog_option_0_asip_vlan": "middle",
            "Array::dialog_name_0_asip_application": "",
            "dialog_tag_0_asip_environment": "bt_dev1",
            "Array::dialog_tag_0_asip_role": "",
            "dialog_option_0_extra_storage_size": 5,
            "dialog_option_0_extra_storage_path": "/data"
        },,
Actual results:

Dialog parser is not able to parse the tag_control type variables. Though this kind of behavior is not observed in other datatypes


Expected results:
Dialog Parser should be able to parse the tag_control type variables' values.

Additional info: