Skip to main content
J
joyner
Cadet | Tier 2
February 5, 2023
Solved

Opening v11 code

  • February 5, 2023
  • 16 replies
  • 488 views

Hi All, just want to check if it’s possible to open v11 code in a360? We migrated from the v11 to a360 last year and i need to revisit a v11 code to double check its functionality. The migrated a360 bot has so many line of codes due to migration tool which make it very difficult to read. Hope that someone can help. Thank you

Best answer by Padmakumar

 

Thanks for the quick response, I still have the ATMX files but I’m unable to open it and read the old code, is there a way to open it in A360 or do I really need v11 control room to open it?

 

@joyner

here is the path in A360 Dev server for A11.3 code

 

 

 

 

Hi @joyner ,

 

Have you tried with the Bot Migration package?

 

 

Hey @Padmakumar 

He tried it, checkout his description

«  The migrated a360 bot has so many line of codes due to migration tool which make it very difficult to read. » 

 

No. He was referring to the Migration wizard and not the Migration package. Even though the Migration package will not migrate dependencies and other entities such as credential variables, AAApplicationPath system variable, and global values that are required to run the migrated bot, he can at least try and see the Bot functionality once it’s got migrated.

Hi Padkumar,

 

This is the migration tool that we use, I’m not sure if this is different from the one that you referring. Can you please confirm. Thanks!

 

 

 

Yes. I am referring to an A360 action package called Bot Migration and not the Migration tool.

Thank you for your confirmation. Can you point me in the right direction as I’m unable to locate that package in our control room?

 

 

**Edit**

 

Thanks, I already located the package it is in my development environment and not in production. 

 

Are the environments on different builds? If not, you should see it on both.

16 replies

Show previous replies
Padmakumar
Premier Pathfinder | Tier 7
Padmakumar
Premier Pathfinder | Tier 7
February 6, 2023

 

Thanks for the quick response, I still have the ATMX files but I’m unable to open it and read the old code, is there a way to open it in A360 or do I really need v11 control room to open it?

 

@joyner

here is the path in A360 Dev server for A11.3 code

 

 

 

 

Hi @joyner ,

 

Have you tried with the Bot Migration package?

 

 

Hey @Padmakumar 

He tried it, checkout his description

«  The migrated a360 bot has so many line of codes due to migration tool which make it very difficult to read. » 

 

No. He was referring to the Migration wizard and not the Migration package. Even though the Migration package will not migrate dependencies and other entities such as credential variables, AAApplicationPath system variable, and global values that are required to run the migrated bot, he can at least try and see the Bot functionality once it’s got migrated.

Hi Padkumar,

 

This is the migration tool that we use, I’m not sure if this is different from the one that you referring. Can you please confirm. Thanks!

 

 

 

Yes. I am referring to an A360 action package called Bot Migration and not the Migration tool.

Padmakumar
    J
    joynerAuthor
    Cadet | Tier 2
    February 6, 2023

     

    Thanks for the quick response, I still have the ATMX files but I’m unable to open it and read the old code, is there a way to open it in A360 or do I really need v11 control room to open it?

     

    @joyner

    here is the path in A360 Dev server for A11.3 code

     

     

     

     

    Hi @joyner ,

     

    Have you tried with the Bot Migration package?

     

     

    Hey @Padmakumar 

    He tried it, checkout his description

    «  The migrated a360 bot has so many line of codes due to migration tool which make it very difficult to read. » 

     

    No. He was referring to the Migration wizard and not the Migration package. Even though the Migration package will not migrate dependencies and other entities such as credential variables, AAApplicationPath system variable, and global values that are required to run the migrated bot, he can at least try and see the Bot functionality once it’s got migrated.

    Hi Padkumar,

     

    This is the migration tool that we use, I’m not sure if this is different from the one that you referring. Can you please confirm. Thanks!

     

     

     

    Yes. I am referring to an A360 action package called Bot Migration and not the Migration tool.

    Thank you for your confirmation. Can you point me in the right direction as I’m unable to locate that package in our control room?

     

     

    **Edit**

     

    Thanks, I already located the package it is in my development environment and not in production. 

    Padmakumar
    Premier Pathfinder | Tier 7
    PadmakumarAnswer
    Premier Pathfinder | Tier 7
    February 6, 2023

     

    Thanks for the quick response, I still have the ATMX files but I’m unable to open it and read the old code, is there a way to open it in A360 or do I really need v11 control room to open it?

     

    @joyner

    here is the path in A360 Dev server for A11.3 code

     

     

     

     

    Hi @joyner ,

     

    Have you tried with the Bot Migration package?

     

     

    Hey @Padmakumar 

    He tried it, checkout his description

    «  The migrated a360 bot has so many line of codes due to migration tool which make it very difficult to read. » 

     

    No. He was referring to the Migration wizard and not the Migration package. Even though the Migration package will not migrate dependencies and other entities such as credential variables, AAApplicationPath system variable, and global values that are required to run the migrated bot, he can at least try and see the Bot functionality once it’s got migrated.

    Hi Padkumar,

     

    This is the migration tool that we use, I’m not sure if this is different from the one that you referring. Can you please confirm. Thanks!

     

     

     

    Yes. I am referring to an A360 action package called Bot Migration and not the Migration tool.

    Thank you for your confirmation. Can you point me in the right direction as I’m unable to locate that package in our control room?

     

     

    **Edit**

     

    Thanks, I already located the package it is in my development environment and not in production. 

     

    Are the environments on different builds? If not, you should see it on both.

    Padmakumar
      C
      Most Valuable Pathfinder
      ChanduMohammadMost Valuable Pathfinder
      Most Valuable Pathfinder
      February 6, 2023

       

      Thanks for the quick response, I still have the ATMX files but I’m unable to open it and read the old code, is there a way to open it in A360 or do I really need v11 control room to open it?

       

      @joyner

      here is the path in A360 Dev server for A11.3 code

       

       

       

       

      Hi @joyner ,

       

      Have you tried with the Bot Migration package?

       

       

      Hey @Padmakumar 

      He tried it, checkout his description

      «  The migrated a360 bot has so many line of codes due to migration tool which make it very difficult to read. » 

       

      No. He was referring to the Migration wizard and not the Migration package. Even though the Migration package will not migrate dependencies and other entities such as credential variables, AAApplicationPath system variable, and global values that are required to run the migrated bot, he can at least try and see the Bot functionality once it’s got migrated.

      Agreed

      Chand
      J
      joynerAuthor
      Cadet | Tier 2
      February 6, 2023

      @Padmakumar Thanks for the help, the package migrate legacy bot is much cleaner compared to the migration wizard! This is a big help for me.

       

       

        Padmakumar
        Premier Pathfinder | Tier 7
        Padmakumar
        Premier Pathfinder | Tier 7
        February 6, 2023

        @Padmakumar Thanks for the help, the package migrate legacy bot is much cleaner compared to the migration wizard! This is a big help for me.

         

         

        Most welcome.

        Padmakumar
        Terms & ConditionsAccessibility statement