Working with Corticon.js samples and configurations
- Last Updated: June 12, 2023
- 2 minute read
- Corticon.js
- Documentation
Progress Software provides a GitHub repository of Corticon.js sample projects at https://github.com/corticon/corticon.js-samples. You will see several references to samples in the Corticon.js documentation.
Accessing sample JavaScript (.js) files
Corticon.js JavaScript files are easily downloaded from their repository location. They might be updated occasionally as that examples listed in the documentation might have changed.
To access a sample's configuration file:
- For a configuration file, click on the active link noted as CODE, as
illustrated in a PDF file:

- The link opens
github.comat the file's location in the repository:
- Click Raw to open the file as a
.jsfile:
- Save the file locally, and then open it for editing in your preferred text editor.
Accessing sample Corticon.js projects
Corticon projects are a collection of several asset types. The samples repository
includes several projects.
- Connect to the repository at https://github.com/corticon/corticon.js-samples
- On the repository's page, click Code, and then click Download ZIP,
as illustrated:

- Expand the downloaded ZIP file into a staging area on your local machine
- In Corticon.js Studio, choose File > New > Rule Project, and give it your preferred name, such as bar.
- In the file system, locate the project you want to import. Drill into the tree
until you have a list of files that include a Vocabulary, an
.ecorefile. - Select all the files at that location, and then drag to the empty project,
bar, and drop them there. - In the Studio:
- Right-click on the project, and then choose Properties.
- Choose Corticon.js Extensions, and then click Add From Project. In the left panel, click the checkbox to select all resources. Click OK, and click Apply and Close.
- Right-click on the project, and then choose Upgrade Rule Assets.
- Right-click on the project, and then choose Validate Project.
- It is a good practice to open the sample's Ruletest (
.ert) file, and then run it. After taking a few seconds for the first compile, the Output should match the Expected.