Opening v11 code

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 

To view the AA11x code you need to AA11x environment i.e AA 11x Client connected to respective CR

Welcome @joyner 

Anyways Check with AA once by placing a support case for any alternates.

 

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. » 

 

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!

**edit**

We select the Administration tab and then click the migration wizard it think. Is it different from the one that you referring to?

 

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. 

 

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

Most welcome.