skip to Main Content


When should I run apexcl?

As changes are made in the APEX Application (using the APEX Builder), you need to decide when to run APEXcl so that those new changed are tracked under version control.

The best time to run APEXcl is after a piece of functionnality is completed, that way you can tie in the APEXcl files to a particular ticket from your ticketing system (Jira, GitHub, GitLab, etc.).

After you have run the APEXcl process (cloud or onprem), commit and push those changes to your version control system.

How do I configure APEXcl to support multiple APEX applications?

You can structure your repository with one folder per APEX application:


Then export each application individually:

cd /path_to_project/application/101
apexcl export

✔ Export was successful

cd /path_to_project/application/102
apexcl export

✔ Export was successful

Why do I see "(Whitespace Conflict)" in my files?

If you drop the APEXcl files on a cloud service, conflicts can occur. For example, Dropbox will sometimes add « Whitespace conflict » if you have two nearly identical file names. A whitespace conflict means that two files names are identical except that one has an extra space at the end of the file name.

To correct, remove the export files and remove the extra space from the component.

Ideally, do NOT put APEXcl files on a cloud enabled directory. Use version control instead.

Do people at Insum have access to my application when I send it to the APEXcl Cloud service?

Absolutely not. When it comes to the security of your data, using APEXcl Cloud is just like using Google Docs. The APEXcl Cloud service runs autonomously and no one is allowed to connect to the database outside of APEXcl Cloud scheduled maintenance, in which case the service will be taken down temporarily. We also monitor database connections and we can provide those logs to you if you request them. The APEXcl Cloud Service is secure and keeps no trace of your application once you have received your files. Conceptually, the APEXcl Cloud Service does the following:

  • Receives your application export files
  • Installs the application
  • Reads the application and generates the output files
  • Sends back the output files
  • Deletes the files from the Cloud
  • Deletes the application from the Cloud
  • We take Intellectual property very seriously and have designed a service that reflects those values.
Back To Top