Change Management module existing tickets are not migrated to Codeless

Hi experts,

I have recently upgraded HPSM from 9.34 non-pd to 9.41. Once I have successfully upgraded to 9.40 app version, I run the enablepd command to change it to Codeless mode.

From what I have checked, Change Management workflows are upgraded to PD Workflows automatically, and the upgrade workflows still will use format control, and other traditional tailoring components. 

However, I found that my previous change management module existing tickets are still in the non-pd form. Any advice how to migrate these change tickets to the pd form?

Also, I have an enquiry: Which is the correct process? To enablepd first, only upgrade to 9.41app version or it is okay to upgrade to 9.41app version first then only enablepd? 

Will there be any difference between the two processes above?

Kindly advice

  • Hi dear,

     

    I am afraid that you have taken the wrong steps to upgrade system, that may be the reason why the error is happening. The correct step is to install PD to SM 9.34 first, and then upgrade 9.34PD to I.41 codeless.

    Hope it helps!

     

    Thank you and Best regards,

  • Hi Ngoc_Ngo_SM,

  • It is perfectly fine to upgrade a Classic 9.3x Application system to 9.4x Classic Applications using the Application Upgrade Utility. Then you run enablepd, which should convert everything to Codeless (Process Designer) unless it involves custom legacy categories. Are the Change records that don't appear to be "converted" using custom Change Categories? If so, this may be related to an existing Enhancement Request, which I have included below:

    https://softwaresupport.hpe.com/group/softwaresupport/search-result/-/facetsearch/document/LID/QCCR1E132850

    If you find that this or any other post resolves your issue, please be sure to mark it as an accepted solution.
    If you are satisfied with anyone’s response please remember to give them a KUDOS by clicking on the "thumbs up" at the bottom left of the post and show your appreciation.

  • hi Mike_Gross,

    Thanks for your reply. Yes, the Change records which don't appear to be "converted" is using custom legacy Change categories.

    Do you mean this is a known issue for upgrading from SM 9.3x custom legacy categories to 9.4x? From the link, it seems that this issue is still under investigations since April 2016.

    Any experts have solutions for this already?

    Kindly advice.

  • It is not a known issue, it is working as designed. That is why there is an Enhancement Request open. The system wasn't designed to convert custom Change Categories to Process Designer. You have to do this manually. There is a workaround that can be used to do part of the work for you. It will create an empty Workflow with the Phases, but you will have to create all other components needed for the Workflow such as Rulesets, Actions, Transitions, etc.

    The workaround involves executing the upgradeCategory function of the processDesignerChangeUpgrade ScriptLibrary record. You can test this in a test or development environment. An example usage could be creating a ScriptLibrary record that calls this function:

    system.library.processDesignerChangeUpgrade.upgradeCategory(name, type)

    Where "name" is the name of the category and "type" is the type of category, in this case it would be change.

    If you find that this or any other post resolves your issue, please be sure to mark it as an accepted solution.
    If you are satisfied with anyone’s response please remember to give them KUDOS by clicking on the "thumbs up" at the bottom left of the post to show your appreciation.

  • hi Mike_Gross,

    Thanks for your reply. I have just started using HP Service Manager 2 months back and I'm not familiar with the script within.

    With the assistance from HPE Support, below is the screenshot for how I call the upgradeCategory function. However, after executing the script, nothing happens. 

    Can you advice if the above script is correct? Also, is it possible to migrate the data using the migrationSetting function? (like how we did for Interaction, Incident modules...)

    Thanks in advance.

  • 1. The PD content pack just migrates the existing, custom change categories and workflows to Codeless, but still uses the legacy forms and business controls (format control, etc.)

    2. You CAN use the migrationSettings utility to remap your legacy change and change task tickets to new PD workflows. It worked perfectly in the systems where customers chose to rebuild to new workflows as part of the Codeless conversion.

  • Verified Answer

    Hi all,

    Just to update my solution for this issue in case someone else faced the same problem.

    Actually, after upgraded to SM 9.4x version and enablepd, just have to assign a workflow to the change category and the ticket will be in codeless format.

    Thank you