List-type property fields seem truncated in xFlow
search cancel

List-type property fields seem truncated in xFlow

book

Article ID: 377038

calendar_today

Updated On:

Products

CA Service Management - Service Desk Manager ServiceDesk CA Service Desk Manager

Issue/Introduction

List-type property fields do not appear correctly in xFlow.  Before choosing the category (area) and loading the properties, the options are displayed normally.  After loading the properties, no list-type field correctly displays the options, they are displayed behind the feed as shown in print .

Steps to reproduce:

Setup:

  1. Login to Service Desk.  Change your role to Administrator if necessary
  2. Navigate to Administration -> xFlow Interface -> Command Bar -> New Ticket
  3. Add ticket attributes to the list.  In my test case I selected to add Category, Impact, and Owner because those are all drop-down listbox fields.

(You can also reproduce by adding new properties to a request area in Administration -> Service Desk -> Requests/Incidents/Problems/Areas)

Reproduce:

  1. Login to xFlow
  2. (If your screen resolution is lower, you may need to zoom the browser to 80% or so to provide enough "real-estate" in the browser window to see the problem.)
  3. In the "Search" field type ServiceDesk
  4. Click the "New Tickets" button
  5. In the command bar type a description and hit <Enter>
  6. The first field, ticket status, is automatically set to "Open".  Click the arrow to expand the list and note that it displays normally.
  7. Next to the second attribute, click the arrow to expand the list of options and note that it displays normally.  Select an option from the list.
  8. Next to the third attribute, click the arrow to expand the list of options and note that this time the list is partially hidden behind the white "ticket notes" field on the screen.  This is the problem.
  9. Next return to the second or first fields and expand those lists.  Note that the same problem is now happening for these fields as well.

Environment

Service Desk 17.4.x

Resolution

The fix for this problem will be included in RU4 for SDM 17.4