CA Service Management

  • 1.  Attach unicode file name

    Posted Nov 05, 2018 06:06 AM

    Dear all,

    My user attach english file name and unicode file name on request screen. After post , english file name stay comment but unicode file name change to insert prefix-name("1002.txt|....") and move attach file above block. I need english file name and unicode file name that they stay same comment. Please help me.

    Unicode file name



  • 2.  Re: Attach unicode file name

    Broadcom Employee
    Posted Nov 05, 2018 07:31 PM

    Komgrit,

     

    I would suggest raising this as a support case for one of us to look into this further

     

    thx

    _R



  • 3.  Re: Attach unicode file name

    Posted Nov 06, 2018 08:21 AM

    I agree with Raghu.Rudraraju

     

    If this is a bug? It should be easily reproducible internally...

     

    My 2-cents...

     

    ===

    Kind Regards,

    Brian



  • 4.  Re: Attach unicode file name

    Broadcom Employee
    Posted Nov 06, 2018 08:39 AM

    Good Afternoon.

     

    I can not reproduce:



  • 5.  Re: Attach unicode file name

    Posted Nov 06, 2018 10:32 AM

    Hi, 

     

    You must attach the files after the ticket created.   We have 3 Service Desk Systems (Prod, UAT, Test).  They are all the same problems. 

     

    We have updated the UAT and Test to the 17.1.0.1 latest too.  

     

    Komgrit. 



  • 6.  Re: Attach unicode file name

    Posted Nov 06, 2018 10:34 AM

    It is also separate display location between those English and Other files too.   We have tested the Japanese file name, it shows the same. 



  • 7.  Re: Attach unicode file name
    Best Answer

    Broadcom Employee
    Posted Nov 07, 2018 01:42 AM

    Good Morning Komgrit.

    Please check on the following, somewhat formal kind of statement:
    This 'Community' functionality is meant for relatively simple questions&(quick)answers for CA Service Catalog.
    Looking into this one, it seems/appears that a 'quick answer' can not be made available within this community thread.
    More likely, 'investigation' and/or 'debugging' is needed to find a possible cause and solution for this.
    Therefor I need to ask you to consider to open a 'standard' case.
    Through which you can get 'standard' and 'full-service' follow-up by our Support Teams.

    Thanks in advance for your understanding and kind regards, Louis.