- Hit Domo APIs outside of the App Framework.
- Hit APIs external to Domo.
- Run Python or JavaScript code securely server-side.
packageMapping definition to your app’s manifest file and then wire up a code engine function to the app in the wiring screen. To be able to test your code engine function locally, please also make sure that you have configured your app with a proxyId.
Manifest
Add a
packageMapping property to the manifest.json file that defines the workflow(s) using the following format:
packageMapping property takes an array of package mappings. A package mapping is an array of objects with the following properties:
- An
alias(string) - the alias you’d like to use when you reference the Code Engine function in your code. - A list of input
parametersrequired to start the Code Engine function. These parameters include the following properties:alias(string) - the alias of the parameter you are passing in to the functiontype(string) - type of the parameter you are passing into the function. The valid options are:booleandatedateTimedecimaldurationnumberobjectpersondatasetgrouptexttime
nullable(boolean) - whether the input parameter acceptsnullinput.isList(boolean) - whether the input parameter is a list or not.children(package mapping object) - if the parameter is a definedobject, you can define the nested properties here.
Calling a Code Engine Function: Code Example
alias parameter in the startFunction function is the alias that you defined in your manifest.
The body parameter is an object where the keys match the alias keys defined in the parameters property of the package mapping definition in your manifest.
Wiring Screen
After publishing your app, you will need to wire it to the Code Engine function you want to hit by editing an existing app card, or creating a new one.

packageMapping array in your manifest

