Template Folder Structure

(top directory)

• template-info.json

  Don’t change the name of this file; processing depends on it.

• variables.json
• ui.json
• template-to-app-rules.json

  We recommend this naming convention as the best way to manage your rules files.

• app-to-template-rules.json

  We recommend this naming convention as the best way to manage your rules files.

• releaseNotes.html
• dashboards

  Subdirectory containing one or more dashboard JSON files corresponding to each dashboard in the source app. If the source app has no dashboards, this subdirectory doesn’t exist.

• lenses

  Subdirectory containing one or more lens JSON files corresponding to each lens in the source app. If the source app has no lenses, this subdirectory doesn’t exist.

• dataflows

  Subdirectory containing the dataflow JSON files corresponding to each dataflow in the source app. If the source app has no dataflows, this subdirectory doesn’t exist.

• recipes

  Subdirectory containing the recipe JSON files corresponding to each recipe in the source app. If the source app has no recipes, this subdirectory doesn’t exist.

• external_files

  Subdirectory containing one or more CSV dataset and related JSON files, such as schema and user XMD files, corresponding to each dataset in the source app. If the source app has no CSV datasets, this subdirectory doesn’t exist.

• dataset_files

  Subdirectory containing User XMD files for SFDC datasets. If the source app has no SFDC datasets with User XMD defined, this subdirectory doesn’t exist.

• images

  Subdirectory containing one or more image files. If the source app has no images, this subdirectory doesn’t exist.

• folder.json
• auto-install.json

  Optional file to create the app with an auto-install request. You must create this file, It is not generated at template creation. The template must be installed as a managed package for app creation.