0 Replies Latest reply on Aug 1, 2018 7:05 AM by Bjorn Calabuig

    Upgrade From 9.1.04p2 to 18.05 (9.1.05)

    Bjorn Calabuig
      Share This:

      Hi List,

      Few months ago we began to install 9.1.04p2 on a fresh machine (our new DEV environment).

      After installing, nothing uncommon done during this time (some tests exporting/importing some forms/workflow but not much more).

       

      Currently, we are upgrading this environment to 18.05 (9.1.05).

      We are stuck on step:

       

      Reconcile AR customizations

      https://docs.bmc.com/docs/brid91/en/upgrading-the-platform-610402613.html

      Adjusting customizations when upgrading

      https://docs.bmc.com/docs/brid91/en/adjusting-customizations-when-upgrading-610402612.html

      You must perform this procedure only in the following scenarios:

      • If you are upgrading from a version earlier than 8.1.xx
      • If you are upgrading from version 8.1.xx and have not already fixed object granularity level

       

      After re-reading this, we believe that, in our case, we can avoid this step.

      Or should we read this sentence this way?:

           if you are upgrading from version 8.1.xx or higher and have not already fixed object granularity level

       

      As said, we are trying to upgrade from a "very less touched" 9.1.04p2.

       

      In our case, should we have to make this "adjustments"?

      If YES to what? To all overlaid forms/als/alguides/filters/...

       

      Right now, we are doing some tests with Analyzer (after filtering by Customization Type=Overlay -> 153 forms) getting some messages:

       

      Message    Rules    Object Type    Name    Related Form Name

       

      Assignee Groups: Granular Components    Object Granularity Level    Field    Assignee Groups    AST:Attributes

          Current Other Definitions : Overwrite New Other Definitions : No Overlay

       

      instanceId: Granular Components    Object Granularity Level    Field    instanceId    AST:Attributes

          Current Other Definitions : Overwrite New Other Definitions : No Overlay

       

      AvailableDate: Granular Components    Object Granularity Level    Field    AvailableDate    AST:Attributes

          Current Permissions : Overwrite New Permissions : No Overlay

       

      Target_Assignee_Groups: Granular Components    Object Granularity Level    Field    Target_Assignee_Groups    AST:LoadAttributes

          Current Other Definitions : Overwrite New Other Definitions : No Overlay

       

      Status: Granular Components    Object Granularity Level    Field    Status    UTIL:PRM:Parametros

          Current Other Definitions : Overwrite New Other Definitions : No Overlay

       

      thf_Admin: Granular Components    Object Granularity Level    Field    thf_Admin    UTIL:PRM:Parametros

          Current Other Definitions : Overwrite New Other Definitions : No Overlay

       

      z5Text_AppTitle: Granular Components    Object Granularity Level    Field    z5Text_AppTitle    UTIL:PRM:Parametros

          Current Other Definitions : Overwrite New Other Definitions : No Overlay

       

      The last 3 ones can be avoided, the mentioned form is custom.

      For the rest of the messages, what should be done? Fix object granularity? One by one? Massively?

       

      And should we do the same for the rest of objects (alinks/alguides/filters/menus/...)

      And, after that, we would be able to begin with ITSM upgrading? That's the point, isn't it?

       

      If NOT, can we avoid the step and start directly with ITSM upgrading?

       

      Kind Regards,

      Björn.