CA Service Management

 View Only
  • 1.  17.3 RU17 - xFlow (manual) Notification - Contact-Search - Contacts not found

    Posted Dec 08, 2022 09:12 AM
    Edited by Peter Schmidt Dec 09, 2022 02:09 AM
    Hi,
    in different 17 RU17 I have differen behaviour ...

    In a ticket I want to notify 'Schmidt, Peter'
    1. Installation-env: 
    It's not possible to find him, because he is not under the first 6 Schmidt-Contacts. when I type
         Schmidt, --> no contacts
         Schmidt Peter --> no contacts
         Schmidtpeter --> no contacts
         Schmidt%p --> no contacts

    2. Installtion-env
         Schmidt, --> no contacts
         Schmidt Peter --> no contacts
         Schmidtpeter --> Schmidt, Peter   is listed
         Schmidt%p --> all Schmidt-contacts having a p somewhere after Schmidt

    Strange list contact behaviuor.
    Is there anything missing on Installation?

    pdm_es_rebuild_index.bat:  Does not help

    Regards,
    Peter


  • 2.  RE: 17.3 RU17 - xFlow (manual) Notification - Contact-Search - Contacts not found

    Broadcom Employee
    Posted Dec 09, 2022 07:56 AM
    The only explanation that I could have for this is that you search MS configuration might be different, or the contact is missing from Elastic Search - I know you mentioned that, pdm_es_rebuild_index.bat:, does not resolve the issue, but I would check directly in ES and see if you see the contact.

    Maybe check and confirm that the HTTP request is sent to search MS as well.

    Sebastian



  • 3.  RE: 17.3 RU17 - xFlow (manual) Notification - Contact-Search - Contacts not found

    Posted Dec 15, 2022 01:33 PM
    Hi Sebastian,
    in xFlow's general search it is running ok. So we don't have an elasticsearch- or index-Problem.

    The problem only occurs when using 'search' (autosuggest) in manual notification.

    Regards,
    Peter


  • 4.  RE: 17.3 RU17 - xFlow (manual) Notification - Contact-Search - Contacts not found

    Broadcom Employee
    Posted Dec 15, 2022 04:29 PM
    Hi Peter,

    I looked in my environment, RU18, and enabled some logging. It seems that whatever is typed is sent to the database and the where clause is against DB specific fields. I don't see a where clause for the combo name,  only for first, middle or last names or user ID.

    I can reproduce only the environment in env #1​. My findings explain why it behaves the way it does. I will check internally with the rest of the engineering team and see if I'm missing anything, or if it should match against the combo name as well.

    Regards,
    Sebastian


  • 5.  RE: 17.3 RU17 - xFlow (manual) Notification - Contact-Search - Contacts not found

    Posted Dec 16, 2022 07:49 AM
    Hi Sebastian,
    many thanks for your answers.
    Meanwhile I have created a Case#33306649 for it.

    Autosuggest in this place should work as known.
    And only 5 contacts there? It should be scrollable as in standard-GUI.
    All other beviour makes no sense and customers wan't work with it.

    Regards,
    Peter