detailSearch (Type)

Available for the following scopes:

• searchDetailPage

Attributes:

• criteriaForAllTypeOfContacts
  Boolean field. When set to true, the search will include the main customers and the additional customers of tickets. When set to false (default), the search will apply the search criteria only to the main customers of tickets.
• duplicatedCustomFieldLabelFormat
  It allows to customize the label format used when several ticket fields have the same localized name. There are four values which can be used to create a unique label:
  • fieldName
  • groupName
  • fieldTechnicalName
  • groupTechnicalName
  The values fieldName and groupName are localized.
  Default format: ${fieldName} (${groupName}) (java.lang.String)
  This helps distinguish different ticket fields or customer fields with the same name, e.g., when they are offered in the drop-down menu in the detail search.
  Example:
  SalesProcess - Priority
  HelpdeskProcess - Priority
• enableRowSelection
  Boolean. Switches on the row selection functionality in the result tables, i.e. a checkbox will be available for each line, one checkbox to (de-)select all lines is available. Default value true. The checkboxes are only displayed if search actions are defined for the respective object type. The search action script will only be executed for the rows which have been selected (by the engineer) using the checkboxes.

  

  Figure 156: ConSol CM Web Client - Search result table with detailSearch/searchDetailPage, enableRowSelection = true

  

  Figure 157: ConSol CM Web Client - Search result table with detailSearch /searchDetailPage, enableRowSelection = false

• enableSearchForDeactivatedEnums
  

  Boolean. If true deactivated enum and MLA values will be accessible in the drop-down menu in Detailed Search.

  

  Figure 158: 'enableSearchForDeactivatedEnums' set to true in searchDetailPage: deactivated enum value is displayed

  

  Figure 159: 'enableSearchForDeactivatedEnums' set to false in searchDetailPage: deactivated enum value is not displayed, but next active value is displayed in list

• enableSearchForOtherUsersTickets
  Boolean. Decides if an engineer can search CM for all tickets (true) or only for tickets which are assigned to himself (false). Default true.
  This attribute has to be set on the (sub-)scope level, i.e., for the (sub-)scope detailSearch/searchDetailPage.
  The value of this attribute only influences the layout of the drop-down menu in the Detailed Search (see figures below). It does not have any influence on the results of the Quick Search.

  

  Figure 160: ConSol CM Web Client - Detailed Search for engineers with enableSearchForOtherUsersTickets = true

  

  Figure 161: ConSol CM Web Client - Detailed Search for engineers with enableSearchForOtherUsersTickets = false

• excludedUserNames

  (usually has to be set for searchDetailPage)
  Login names provided here will be filtered out in engineers' criteria selector

  

  Figure 162: Pull-down menu in engineer detail search before excluding user names

  

  Figure 163: Using the page customization attribute excludedUserNames for two user names

  

  Figure 164: Pull-down menu in engineer detail search after two user names have been excluded from the list
  

• maxGridTicketsNumber
  Maximum number of tickets shown in grid view, i.e., in the entire grid, not in one column. The default value is 120.

  

  Figure 165: ConSol CM Web Client - Using page customization to adapt maximum number of tickets shown in grid

  

  Figure 166: ConSol CM Web Client - Maximum number in ticket grid with maximum 7

  The maximum number of tickets displayed in the ticket grid view can also be role-specific. For example, an engineer with the role Teamlead would see 100 tickets, whereas an engineer with the role Helpdesk would see 50 tickets. In the following simple example, all engineers with the role ServiceDesk see ten tickets, all others see 5. The configuration uses a script which is defined for the page customization type. The script is stored in the Script and Template Administration of the Admin Tool.

  

  Figure 167: ConSol CM Web Client - Defining a script for maximum number of tickets in grid view using page customization

  

  Figure 168: ConSol CM Admin Tool - System, Scripts and Templates: Script for maximum number of tickets in grid

  

  Figure 169: ConSol CM Web Client - Number of tickets in ticket grid for different engineer roles