Login to follow
ExternalLogicStudio

ExternalLogicStudio (ODC)

Stable version 0.1.4 (Compatible with ODC)
Uploaded on 04 May 2025 by valantic LCS
ExternalLogicStudio

ExternalLogicStudio (ODC)

Documentation
0.1.4

The tool was built to help developers when they are creating new ODC External Logic libraries or migrating them from OS11.


Features:

  • Project and Unit Test generation
  • Action management
  • Structure management
  • GitHub integration
  • XIF Migration
  • AI action content generation


The application can run on DEV.


GitHub Integration


Different from OS11 Extensions, the only resources uploaded to the ODC Portal are the compiled files. The library source code is never uploaded, so any mistake in handling the source code might cause a huge loss. Thinking on that, the tool provides the developers with a built-in integration with GitHub, enforcing the versioning of the library source code.

Although using GitHub to version the source code is recommended, this feature is not required when using the tool.

The integration is very straightforward: the OAuth App integration must be created on GitHub, to allow External Logic Studio to call the REST Api using the user’s credentials. The whole process is documented on Settings  - GitHub:


After the first generation and if the Repository URL is configured, the code must be committed to GitHub before generating new versions. The new source code will be merged with the GitHub files to only modify the method's signature and keep the content.



Project

The first page of the tool is a list of all Projects in the environment. This list is very similar to the Extensions list in Service Center.


There’s a simple search by name and owner and it’s possible to edit a new Project or create a new one.

The Project detail screen has multiple tabs, containing all data necessary to manage the External Logic on ODC.

The first tab has the basic information about the Project: Name, Description, Icon, and the GitHub Repository URL.

The icon can be changed by clicking on the default project icon.



The repository in GitHub Repository URL must not exist at this point. The application will create it at the first generation:


It’s important to correctly set the toggle for “Is it an organization repository?” since the APIs are different for Organization and Private repositories.

The repository will be created with the auto_init flag set to True.



Actions

It’s possible to manage all Actions the library will expose to other ODC applications. The UI is very intuitive and it’s possible to add/remove Actions and configure the input and output attributes:

The icon can be changed by clicking on the default action icon.



Structures

And, the same way we do for Actions, it’s possible to manage all Structures the library will expose to other ODC applications. The developer can add and remove structures and define their attributes.



Project Generation

Hitting Generate button will validate the project and generate the files. After it’s done a new version will be ready to be downloaded or cloned using the GitHub Repository URL.

The raw zip file with the C# solution can be downloaded — source code without merging with GitHub and clicking on the version number will preview the files.



Settings — Icons

The icons are shared by all Projects and in this screen it’s possible to manage all of them.




Settings — GitHub

Under this page, you can find all the documentation related to the GitHub configuration



Settings — AI Templates

Under AI Templates you can tweak the AI prompt. The values between brackets “{{}}” are replaced by the application to build the full prompt for the AIs.