The integration process revolves around the extension life cycle. The process steps are executed in both OutSystems and third party IDE component environments. The illustration below depicts the most significant steps, showing them next to the component where they are executed.
These are the generic steps that you should take to implement and use a extension in OutSystems:
In Integration Studio, create a new extension module and set its name and the supported DBMS;
Define the new actions that will encapsulate your code. Also define any input and output parameters for your action(s), as well as any entities or structures;
Generate the stubs for the declared actions and edit the code implementing the logic of the actions using a third party IDE for .NET.
Integration Studio provides the necessary facilities to integrate with the IDE you specified in Integration Studio options, enabling you to:
- Implement the logic of your actions using the IDE;
- Edit the extension source code using the IDE;
- Update the extension source code with the extension definition in order to reflect the changes you have made in Integration Studio.
If your extension does not contain manually added actions, you can skip this step. However, the extension will still have source code files associated. See Extension Source Files for more information;
Publish the extension module to the Platform Server from Integration Studio by clicking 1-Click Publish in the File menu or Toolbar;
Use the created extension in any OutSystems applications where you want to use it, adding it as a dependency in Service Studio. Once the extension module is a dependency of your application, the logic that the module implements becomes available in the Logic tab of Service Studio.