* template-info.json manages all elements of your template, including metadata information about the template, the Analytics objects that define dashboards and lenses, and the other files that are part of the template.
* ui.json manages the configuration wizard that drives app creation. It defines the number of wizard pages, the order of wizard questions, and any messages you want the user to see.
* variables.json contains all template variables, including text for wizard questions and specifications for the answers. Variables also define conditional questions. For example, you may want some questions to appear in the wizard only if an org contains certain data. Or you might want to add more specific questions based on the answers to more general wizard questions.
* template-to-app-rules.json defines the rules the template follows. For example, you could define a rule that specifies that if an org doesn't use certain Salesforce objects, the app won't refer to them in dashboards or include them in the dataflow. Rules also define how variables are handled. For example, if the wizard asks which fields to include in filters for accounts, template-to-app-rules.json determines how that choice is reflected in dashboards.

To maintain consistency and ease of updates across multiple dashboards, creating or editing a component for the widgets is the most effective method. This approach:
Efficiency in Updates: Allows changes to be made in one place, which automatically propagates to all instances where the component is used across dashboards.
Consistency: Ensures uniformity in the appearance and functionality of the widgets across different dashboards.
Simplicity: Reduces the need for redundant work, where each widget would otherwise need to be updated individually.

To determine whether a subscription is new or a renewal from the Opportunity records in Salesforce, the consultant should utilize a Custom Formula in the data transformation process. Here's the rationale:
Custom Formula Usage: By employing a custom formula, the consultant can create a logical expression that checks the historical data associated with each account. If an account has previous closed-won opportunities, any new opportunities can be labeled as renewals; otherwise, they are considered new subscriptions.
Data Insight: This method provides a straightforward way to derive new insights (new vs. renewal) directly from existing data without altering the data structure itself, making it a non-invasive and efficient solution.
Implementation: The custom formula can be applied in a recipe or directly within a dataflow in CRM Analytics, offering flexibility in how and where the transformation is executed.