CA Service Management

  • 1.  ca sdm14.1 to 17.0 after upgaradtion customizations not working properly

    Posted Feb 19, 2018 12:25 AM

    hi

     

    We did ca sdm up gradation from 14.1 to 17.0.

    In previous version we already did customization based on customer requirement.

    after customization the windows forms effected automatically. but incidents,contacts forms are displaying empty forms.

    we already fallowed below document

    Customization Upgrade Utility - CA Service Management - 17.0 - CA Technologies Documentation .

    still empty pages are coming in incidents,contact forms.please give some other way to solve the issue.

     

    Regards,

    Vijaybabu



  • 2.  Re: ca sdm14.1 to 17.0 after upgaradtion customizations not working properly
    Best Answer

    Posted Feb 19, 2018 01:16 AM

    Hello Vijay,

     

    An empty form usually indicates that there is a syntax error in the form definition.  I suggest you compare the failing customised form with the out-of-box r17 form (from bopcfg\www\htmpl\web) using a visual file difference tool and re-apply the mods one at a time to the unmodified r17 form, testing the form after applying each mod.

     

    Regards,

    James

     

    PS: if it still doesn't work, post the form source to this thread and I'm sure someone will help out.



  • 3.  Re: ca sdm14.1 to 17.0 after upgaradtion customizations not working properly

    Posted Feb 19, 2018 02:45 AM

    Hi Vijay,

     

    1. As James has already mentioned, chances are that the problematic forms are incompatible with r17.0 as the r14.1 to r17.0 is total GUI revamp. The quickest way to check the root of your issues would be to disable customizations for the forms that are giving you trouble by renaming them to something else in the '~NX_ROOT\site\mods' path and run 'pdm_webcache -H'. This way the OOTB forms will take effect and you can redo the modifications on those forms one and time to validate which item on the forms breaks the functionality.

     

    2. Can you also share also the output\results file of the 'Customization Upgrade Utility' as this might also shed some light of the culprit forms?

     

    ===

    Kind Regards,

    Brian