CA Service Management

  • 1.  xflow issue

    Posted Jan 17, 2018 09:32 AM

    Hello Team

    We encounter few issues while using Xflow interface

    1.unable to execute 'update status' of the ticket in xFlow. Error message: command execution failed. 

    2. Unable to populate details under suggested experts.

    3. Notification button is not updating real time.

     

    Please advise 



  • 2.  Re: xflow issue

    Broadcom Employee
    Posted Jan 17, 2018 10:03 AM

    What version of SDM and patch level do you currently have installed?

     

    Is xFlow installed on a separate server?

     

    What are the hardware specs of the server where xFlow is installed?



  • 3.  Re: xflow issue

    Posted Jan 17, 2018 10:09 AM

    Hi Paul

     

    We are using SDM 17.0 and no any patch installed currenty.

     

    We have setup advance availability and xflow is installed on application

    server ..

     

    Specification is 16 GB Ram 4 core cpu

     

    On 17-Jan-2018 8:03 pm, "Paul_Coccimiglio" <



  • 4.  Re: xflow issue
    Best Answer

    Broadcom Employee
    Posted Jan 17, 2018 10:47 AM

    Aamir,

     

    For your issue with the Suggested Experts functionality, what details are you having issues populating? The Suggested Experts feature normally just recommends up to five analysts/administrators who have resolved similar tickets, so it's not clear what details you would need to set manually. Suggested Experts won't work without a properly configured Search Server - do you have the Search Server set up and configured in this environment, and have you performed the initial load procedure on it? You may want to consult our documentation on configuring the Suggested Experts search (which selects which experts are shown on a ticket), and the related documentation on performing the initial load and index process on the Search Server (both linked below).

    Configure Suggested Experts Search

    Perform Initial Load and Refresh Index and Data on the Search Server



  • 5.  Re: xflow issue

    Broadcom Employee
    Posted Jan 18, 2018 02:22 PM

    In regards to the "update status" issue, is anything getting logged in CA\xFlow\APPS\logs\incidentMS.log



  • 6.  Re: xflow issue

    Posted Sep 15, 2018 12:35 PM

    We also faced the update status issue. it is caused by having call_back_date as a dependent attribute control.

    it's now accepted as a defect



  • 7.  RE: Re: xflow issue

    Broadcom Employee
    Posted Nov 20, 2020 03:40 AM
    @Martin Müller - Do you have the case and/or defect number? I have a customer that is facing issues with the  call_back_date as a dependant attribute control.

    I just want to understand what solution was implemented?

    ------------------------------
    Kind Regards,
    Brian
    ------------------------------