Appendix

The reference section of this document contains detailed examples, attribute lists and descriptions, and other in-depth reference materials that build on the concepts we have discussed up to this point.

• Add a Recipe to a CRM Analytics Template

  Data prep recipes are a unique CRM Analytics asset, as they aren’t stored in folders like dashboards, lenses, and datasets. The only way to connect a recipe to an app is via the relationship of the datasets in the folder to the recipes that consume or output those datasets.

• Configure Recipe Execution

  Data Prep recipes can be complex and add to app creation time if they sync and execute while the templated app is generating. Recipes can also change the shape of your existing data. The executeCondition attribute for recipe entries allows you to specify if a templated recipe syncs and executes during templated app creation or not.

• Add an Einstein Discovery Story to a CRM Analytics Template

  Einstein Discovery stories can be added to an app template by referring to the story in the template-info.json file.

• Add a Remote Connector to a CRM Analytics Template

  Add remote connectors to the digest node of a template dataflow by referencing connectors in variables.json and editing ui.json and rules.json.

• Use Live Datasets in a CRM Analytics Template

  Use live datasets in your CRM Analytics template with the liveConnection attribute to bring in live connections to Snowflake source tables. Creating a template from a source app with live datasets generates the dataset information, but there are considerations for successful app creation for your users.

• Work with Embedded App Auto-Install Requests

  Embedded app templates can create apps without any custom code, but you can add customizations to your embedded app lifecycle. Create Apex classes that use the CRM Analytics auto-installer to create and manage auto-install requests for your embedded app.

• Feature Parameters for Analytics Templates

  Feature parameters are available to control behavior in the template-to-app process for CRM Analytics apps. Feature parameters are defined as metadata that is deployed as part of the managed package. When feature parameters are deployed with the template, the parameter values are set using the LMA application.

• template-info.json Attributes

  The template-info.json file is the main file that describes the template. It includes or references all the information required to create a downstream app.

• template-info.json Example

  Here are two example template-info.json files.

• ui.json Attributes

  The ui.json file attributes are:

• variables.json Attributes

  Named nodes, each representing a single variable. Each node contains the following attributes:

• org-readiness.json Attributes

  The org-readiness.json file attributes are:

• folder.json Attributes

  The folder.json file attributes are:

• auto-install.json Attributes

  The auto-install.json file attributes are:

• rules.json Example

  Refer to this example of the rules.json file.

• rules.json Attributes

  The rules.json file attributes are:

• Rules Testing with jsonxform/transformation endpoint

  Test the results of a rule before deployment by calling the jsonxform/transformation endpoint.

• VisualForce Events for Customizing the Wizard UI

  This reference section explains the details of using VisualForce for customizing the Wizard user interface.