58
Views
4
Comments
Solved
Transfer app from a personal environment to other
Application Type
Reactive

Hello everyone!

I was looking for the best way to transfer my app I developed in my personal environment to other personal environment. Came across some solutions but I am hesitant on what is the best approach. Can anyone help and describe the steps I need to take? 

Thank you

2016-04-22 00-29-45
Nuno Reis
 
MVP
Solution

Hello.

On paper Personal Environments are for personal use so you don't need to share modules. If you buy a license, you can ask OutSystems to migrate them there.

Having said so, there are at least 4 ways of doing migrations.

One is by using the IPP (only for paying customers) .

Two go against the code of conduct so you shouldn't do them (probably the ones you heard).

Finally, you can freely copy actions and screens between Service Studio and ODC Studio and vice-versa.

So you open your free Personal Environment and your free ODC environment. Copy everything there. Then open the other Personal Environment and do the opposite.

Some features of ODC differ from O11, but unless you are going to publish, you can work around them.

2023-03-31 06-39-46
Asad Sheikh

Hi @Helga Afonso


    1.Open the application you want to transfer.

   2.Click on "Module" > "Export..." and select Export Application (.oap).

   3.Save the exported .oap file to your local machine.

After that You have to do the IPP configuration for that, as you need to publish application which is created in personal environment in licensed environment. You can use below link to do the configuration. 

https://www.outsystems.com/homeIpp/IPP_Page.aspx

For better understanding you can refer the below link. 

https://success.outsystems.com/support/licensing/outsystems_intellectual_property_protection_ipp
/

Hope this will help,

Asad

2024-10-12 12-11-20
Kerollos Adel
Champion

If you must do this due to a compelling reason, it is highly discouraged. As @Nuno Reis  mentioned, these methods should be used.

Have you tried uploading the project to the Forge and then downloading it again

However, I believe these methods should never be used except in extreme cases, to avoid violating the rules of the free environment.

2021-11-19 11-12-44
Rui Mendes

Hello @Helga Afonso,

I can share my understanding of the topic, which was once validated by OutSystems. 

The IPP (Intellectual Property Protection) is designed to protect the rights of authorship of applications. Transferring between two personal environments conflicts with these rights, as the personal environment is meant for developing applications for use within that environment and not for others. 

However, there are cases that may not conflict with the use of a personal environment when transferring to another environment. 

For example: 

- When I develop an application for training a specific concept and make it available for my student to practice. In this case, I do not conflict with the IPP, as it is not the provision of a product or functionality. 

- Another scenario is the validation of applications from the Forge for later installation at a client, where I may have made specific adjustments for that client during the validation. 

For such transfers, I always use the official method of transferring rights, indicating the serial number of the source and destination environments, avoiding conflicts with policies that could lead to the respective blocking of the environments due to non-compliance. 

If your scenario fits these examples, I believe you can proceed with the transfer without issues. If it does not fit or if you have doubts, you can send a clarification request to OutSystems. Although the personal environment does not have access to support, they do provide clarification in these cases. 

Lastly, regarding this type of matter, I do not advise, but rather discourage, the use of unofficial methods that could lead to problems. 

Best regards, 

Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.