Migrating forms across, from Service Catalog version 12.9 to Service Catalog version 17.1.
On an SC-Form, the dropdown of a specific Select Component has un-necessary leading space character.

 

NA

Windows
CA Service Catalog 17.1.RU1

Defect DE42295 has been created for this. To be worked on by our Engineering Team.
Depending on the results of the analysis, the solution for this is possibly to be expected as a patch or fix or a future release.
In other words, there is no permanent solution at this time.
The issue is currently being researched.
Additional information will be provided as it becomes available. 

CA Product impacted
=====================
CA Service Catalog(SC)

Versions/Release and any patches
================================
CA SC R17.1

OS/Environment
==============
Windows

Description
===========
Migrating forms across, from Service Catalog version 12.9 to Service Catalog version 17.1. 
On an SC-Form, the dropdown of a specific Select Component has un-necessary leading space character. 
Please see screenshots of the form in both 12.9 and 17.1. 
Please advise how I can correct this in version 17.1. 

Work around
===========
NA

Analysis
========
Opening a form with a dropdown. Hit the F12-debug for the browser.
Choose the 'select an element' in the top-left-corner.
Select the drop down in the form and see the 'select.css' details.
I was able to change the background color instantly (select.css.328).
Unfortunately, I was not able to change the leading space, in front of the value in each dropdown-row.

C:\Program Files\CA\Service Catalog\view\webapps\usm\explorer\scripts\catalogux\resources\css
select.css Lines 279-288
.ui-select-bootstrap .ui-select-choices-row>span {
    cursor: pointer;
    display: block;
    padding: 3px 20px;
    clear: both;
    font-weight: 400;
    line-height: 1.42857143;
    color: #ffffff; 
    white-space: nowrap;
   /* -webkit-text-fill-color: #ffffff; */

Expectation
===========
Defect DE has been created for this. To be worked on by our Engineering Team.
Depending on the results of the analysis, the solution for this is possibly to be expected as a patch or fix or a future release.
In other words, there is no permanent solution at this time.
The issue is currently being researched.
Additional information will be provided as it becomes available.