Having problems with your account or logging in?
A lot of changes are happening in the community right now. Some may affect you. READ MORE HERE
Highlighted
mike_se Contributor.
Contributor.
146 views

PPM Support Tip: Improved behavior of SQL Drop-Down/Auto-Complete Fields

When upgrading to 9.22 version, improved behavior of SQL Drop-Down/Auto-Complete Fields

Platform issue - Feature to help with a previous Multilingual User Interface (MLU) Guide


Starting from PPM Center version 9.22, custom drop-down fields and auto-complete fields validated by "List" and "SQL - Custom" behave the same in the MLU, as follows:

If a custom drop-down/auto-complete list has multiple values, then a drop-down/auto-complete field with an existing value is shown in your current session language, even if your session language is different than the language in which the value was originally selected from the drop-down/autocomplete list.

Example. A custom drop-down/auto-complete list with multiple values has been created for requests. A user logged on to PPM Center in a German language session creates a request, and in doing so, selects a value for the custom drop-down/auto-complete list. A different user logs on to PPM Center in a Korean language session and opens the new request, which was defined in German. The value in the drop-down/auto-complete field is shown in Korean.

Note: PPM Center does not support auto-complete fields validated by "SQL - User" in the MLU.




To ensure a SQL drop-down/auto-complete field behaves correctly,

1. In the PPM Workbench, open the request type which contains the drop-down/auto-complete field.

2. On the Fields tab, select the drop-down/auto-complete field and click Edit.
The Field: <Field Name> window opens to the Attributes tab.

Note: If the drop-down/auto-complete field is a column of a table component, select and edit the table component.

3. In the Search Validation field, specify a list validation which contains:
* All the values potentially returned by the drop-down/auto-complete field
* Potential translations of the returned values. If translations are not provided, the returned values will be used.

Note: If a table component contains several SQL drop-down/auto-complete columns, the list validation should include values potentially returned by all the columns together with translations of the returned values.

4. Click OK.

“HP Support
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.”
Labels (1)
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.