Clarity Service Management

Expand all | Collapse all

CA SDM, Additional Search Arguments

Jump to Best Answer
  • 1.  CA SDM, Additional Search Arguments

    Posted 04-15-2019 10:52 AM

    Hey all,

     

    We have ran into an interesting problem upon migration from 17.1.01 into 17.1.02.

     

    After completing the migration we appear to be getting default values being set in the additional search arguments location of SDM when looking up and using a template from which to create a R/I ticket.

     

    For example my default values are set as:

    Whereas another user may have default values as such:

     

    It does not seem to be consistent. In that some people seem to get the additional organization ID and some do not. The problem is that with all of this additional data in the search parameters people can no longer find a full list of template results easily. Having to delete this additional argument every time they perform a search. 

     

    We currently have a support case open with CA on this topic. But wanted to know if anyone else had ran into this and if you did what you did to fix it. 

     

    If not I will post the solution to this issue as well once we isolate what it is.

     

    Thanks!



  • 2.  Re: CA SDM, Additional Search Arguments

    Posted 04-18-2019 06:38 AM

    Hi Jordan,

     

    Do you have 'Service Contracts' enabled or in place? For me, this is one area where the logged in user's data may be restricted based on organization.

     

    ===

    Kind Regards,

    Brian



  • 3.  Re: CA SDM, Additional Search Arguments

    Posted 04-18-2019 06:47 AM

    Another Idea: whats about data partitions?



  • 4.  Re: CA SDM, Additional Search Arguments
    Best Answer

    Posted 04-18-2019 10:02 AM

    It is an option in SD, Request - Change - Issue section.

     



  • 5.  Re: CA SDM, Additional Search Arguments

    Posted 04-18-2019 10:08 AM

    Great finding , Pier-Olivier. Thanks !



  • 6.  Re: CA SDM, Additional Search Arguments

    Posted 04-18-2019 10:20 AM

    Agreed. Great find. This has resolved the problem.