Hello All,
I would like to ensure that I am following the correct procedure for deploying an application, such as moving it from the development (DEV) environment to the testing (TEST) environment. This is particularly challenging when dealing with numerous dependencies. Currently, the manual process involves spending half an hour reviewing and managing all the modules, refreshing dependencies, republishing. For instance, if I modify an extension, I often need to refresh up to 10 modules before deploying it to the TEST environment. I'm curious if there is a simpler approach in OutSystems. I would appreciate it if someone could explain or provide suitable links to help me understand and manage these dependencies more efficiently. Thanks
Kind regards,
Abdul
Hi Khani,
I think this link may help https://www.outsystems.com/forums/discussion/58145/automatically-update-dependancies/
Best regards,
Khuong
Thank you for your valuable answer.
Hi Khani,Hope you are doing well.
from your question it seems you have multilayer architecture where you have alot of dependent modules.
I will suggest to use service action instead of server as this create loose couplingalso the name itself suggests the usage. Server actions are more suitable for tightly coupled architecture kind of functionalities where any changes required a refresh at the consumer level too. While service actions are more for the service oriented architecture or the loosely coupled architecture. Let me know if you are looking for any other specific details. You can always Google for articles around these for better understanding.
Also you may refer to this link
https://www.outsystems.com/forums/discussion/51035/service-action-vs-server-action/
https://www.outsystems.com/forums/discussion/58145/automatically-update-dependancies/
Thanks and regards,Deepali Nayak
Hello Deepali,
Thank you for your valuable answers. I will discuss all these possibilities internally to adhere to the principles of teamwork ;)
Hi Khanji,
You can create a Solution in service center and add all modules to the solution, then prior moving to the next environment publish the solution.
Other approach if change was in a specific module, is in the module you have the option to refresh all consumers.
Hope that it helps you