Creating an App from the PSA Analytics Template

The following templates are used to create dashboards in PSA Analytics:

The app template for FinancialForce PSA Analytics enables you to generate an app that contains dashboards and datasets. The PSA Analytics configuration wizard allows you to customize several values in your app before it is generated.

The app template for PSA Analytics Embedded Dashboards enables you to generate an app that contains dashboards optimized for embedding in PSA workspaces and pages. This app contains copies of the datasets held in your primary PSA Analytics app.

Note:

We've started to build support for the embedded dashboards template feature in Salesforce. When fully supported by Salesforce, this enhancement will streamline the process of embedding dashboards for users throughout your organization. Further improvements to this functionality will be announced in upcoming Salesforce releases.

For more information about dashboards and datasets, see the Salesforce Help for Analytics.

The length of time for your first PSA Analytics app to be generated depends on the volume of information stored within your PSA app and whether you have turned on specific features in Analytics, such as Data Sync and Incremental Load. Typically, you can expect the app to be generated within 10 minutes.

By default, the Data Sync and Incremental Load features are turned off in Analytics. Turning these features on can improve the performance of the app template generation. If the app takes a long time to be generated, contact Customer Support. Refer to the Salesforce Help for Analytics for more information about these features.

To create an app using the PSA Analytics template:

  1. Click Create in Analytics Studio.
  2. Click App.
  3. Select the FinancialForce PSA Analytics template, then click Continue.
  4. Provide your answers to each question. See below for a list of the questions included in the configuration wizard.
  5. Name your app, then click Create.

Your app is now available on the App Launcher page. You can view the app from the Analytics tab, or edit it from the Analytics Studio.

By default, when you generate an app the sharing settings are set to private. To give access to other users, click . This opens the app's Give Access tab. For more information about sharing Analytics apps, see the Salesforce Help.

Warning:

If the app creation process fails, you must re-run the app template after fixing the issue. You can re-run the app template by deleting the failed app or reconfiguring it.

You must first create your primary PSA Analytics app. This contains the datasets that are copied into your PSA Analytics Embedded Dashboards app.

No configuration wizard is used in the creation of this app. It is activated using Feature Console. For more information, see Enabling PSA Embedded Dashboards with Feature Console.

When you create a new PSA Analytics app you can customize several parameters by selecting the required value in the configuration wizard. To enable additional features you need to answer the questions prompted by the configuration wizard during the app creation, update or reconfiguration. Questions marked with an asterisk (*) are mandatory.

Configuration Wizard Settings

Question

 

Description
Enable the existing PSA object sharing model for the data displayed in PSA Analytics. *

We have detected that the org's sharing model for some of the FinancialForce PSA objects is Private. You can choose whether you want to enable the same model for the data displayed in the datasets and dashboards in PSA Analytics or not. If you choose to disable the sharing model, all your project related data will be displayed to all users sharing the app.

Note 1:

Select whether you want to apply the existing PSA object security model to your PSA Analytics app or not. If you enable the existing sharing model, users can only view records related to the objects they have access to. If you do not enable the existing sharing model, all users with access to Analytics that share the app can view the data for all PSA records.

Note 2:

PSA Analytics supports sharing with Salesforce public groups and their member users. If a group contains any subgroups, you have to share the access to each child group separately.

For more information, see PSA Analytics Object Sharing Model

.
Which month is the start of your fiscal year? *

Select the start month of your fiscal year.

Note:

PSA Analytics uses your time period records or your org configuration to identify which month you have assigned as the start of your fiscal year. You can accept the suggested month or you can manually select the start month of your fiscal year from the drop-down list in this section of the configuration wizard. The value you select determines the date ranges for the fiscal quarters and fiscal years displayed in PSA Analytics.
Do you want to add data derived from Services CPQ to the Project Reporting dataset and create the Services CPQ Estimator, and Services CPQ Estimate Manager dashboards in PSA Analytics?  

Data derived from Services CPQ is displayed in the Services CPQ Estimator and Services CPQ Estimate Manager dashboards in the PSA Analytics app. This step requires you to have Estimate, Estimate Task, and Estimate Role Request records in your Services CPQ data environment.

Note:

This question is displayed if you have assigned a Services CPQ license to the Integration User.
Do you want to create the Revenue Forecast dataset in PSA Analytics? *

This dataset is used to display data in the Revenue Forecast dashboard in the PSA Analytics app and the Revenue Forecast (Embedded) dashboard in the PSA Analytics Embedded Dashboards app. This dataset requires you to have Revenue Forecast and Revenue Forecast Version records in your PSA data environment.

Note:

Choose whether to create the Revenue Forecast dataset. This dataset is used by the Revenue Forecast and Revenue Forecast (Embedded) dashboards. These enable you to embed analytics to display key revenue forecasting key performance indicators (KPIs), including comparisons of forecast versions. This dashboard requires you to ensure the necessary data is available in your org's data environment. For more information about the data requirements, see Preparing the Data Environment for PSA Analytics. To create the Revenue Forecast (Embedded) dashboard, you must enable the PSA Analytics Embedded Dashboards feature in Feature Console. For more information, see Enabling PSA Embedded Dashboards with Feature Console.
Do you want to create the Billing Forecast Summaries and the Billing Forecast Details datasets and the Billing Forecasts dashboard in PSA Analytics? *

This dataset is used to display data in the Revenue Forecast dashboard in the PSA Analytics app and the Revenue Forecast (Embedded) dashboard in the PSA Analytics Embedded Dashboards app. This dataset requires you to have Revenue Forecast and Revenue Forecast Version records in your PSA data environment.

Note:

Choose whether to create the Billing Forecast Summaries and the Billing Forecast Details datasets and the Billing Forecasts dashboard. This dashboard allows you to visualize your PSA Enhanced Services Forecasting data in Analytics and drill down into the data to gather business insights.

This dashboard requires you to ensure the necessary data is available in your org's data environment. For more information about the data requirements, see Preparing the Data Environment for PSA Analytics.
Do you want to create the Project Margin dataset and the Total Project Margin (Workspace) dashboard in PSA Analytics? *

This dataset is used to display data in the Total Project Margin (Workspace) dashboard in the PSA Analytics app. This dataset requires you to have Project Actuals Converted records in your PSA data environment.

Note:

Choose whether to create the Project Margin dataset and the Total Project Margin (Workspace) dashboard. This dashboard can be integrated with the project manager workspace in LightningPSA, enabling your project managers to get a smart vision of their total margins for their assigned projects.

This dashboard requires you to ensure the necessary data is available in your org's data environment. For more information about the data requirements, see Preparing the Data Environment for PSA Analytics.
Do you want to create the Utilization Results dataset in PSA Analytics? *

This dataset is used to display data in the Utilization Analytics dashboard in the PSA Analytics app and the Utilization Analytics (Embedded) dashboard in the PSA Analytics Embedded Dashboards app. This dataset requires you to have access to the Utilization Result object in your org.

Note:

Choose whether to create the Utilization Results dataset. This dataset is used by the Utilization Analytics and Utilization Analytics (Embedded) dashboards. These enable you to visualize detailed information about your resources' scheduled or actual hours logged and calendar hours. This dashboard requires you to ensure the necessary data is available in your org's data environment. For more information about the data requirements, see Preparing the Data Environment for PSA Analytics To create this dashboard, you must enable the PSA Analytics Embedded Dashboards feature in Feature Console. For more information, see Enabling PSA Embedded Dashboards with Feature Console
Apply permission controls from PSA to the Revenue Forecast dataset and dashboard. *

We have detected you have applied user permission controls to your active Revenue Forecast Setup record. You can choose whether to enable the same user permission control model in your dataflow to control the data displayed in the Revenue Forecast dataset and dashboard. If you choose to disable this model, all your revenue forecast related data is displayed to all users sharing the app.

Note:

Choose whether to apply user permission controls in your active Revenue Forecast Setup record in your dataflow to control the data displayed in the Revenue Forecast dataset and dashboard. If you choose to disable this model, all your revenue forecast related data is displayed to all users sharing the app. For more information, see Preparing the Data Environment for PSA Analytics.
Which additional fields from the Project object do you want to import?  

You can select one or more additional fields from the Project object. These are added to the Backlog, Billings, Billing Forecast Details, Project Reporting, Revenue Forecast and Total Project Margin (Workspace) datasets. Encrypted and multi-select drop-down fields are not supported. Only user-generated dimension fields can be added to the Project Reporting dataset. You must assign read-access permission to the Integration User to add user-generated additional fields to these datasets. When you import packaged additional fields, they are prefixed with the originating object's name, unless this is already present in the field name. Lookup packaged fields are appended with "Name", and ID fields are appended with "ID", unless already present in the field name.

Note 1:

Select one or more additional fields from the Project object to include in your PSA Analytics datasets. These are stored on the following datasets:

  • Backlog
  • Billings
  • Project Reporting

Note 2:

If you decided to enable additional features in the previous wizard question, the additional fields from are also added to the optional datasets that contain project data:

  • Billing Forecast Details
  • Total Project Margin (Workspace)
  • Revenue Forecast

Note 3:

To properly visualize the data in Analytics, ensure that the integration user and the user have the necessary permissions to view the selected fields. If you select a field that is a lookup to an object outside of PSA, the integration user also requires a license that provides access to that object.

Note 4:

Encrypted, multi-select drop-down fields are not supported. These fields are not displayed in the list of available fields for import. Only user-generated dimension fields can be added to the Project Reporting dataset.

Note 5:

The additional fields you import from the PSA package receive a label identifier that states which object (Project or Resource) the field belongs to. For example, if you import an additional field from the Resource (Contact) object called "Start Date", after importing it to Analytics the label identifies the field as "Resource Start Date" in PSA Analytics. If the imported field already contains an identifier as part of its regular label this feature does not apply. For example, if you import an additional field from the Project object called "Project Manager Name", after importing it to Analytics the label for this field remains the same in PSA Analytics.

Warning:

If the Data Sync feature is enabled, do not withdraw the fields permissions assigned to the integration user after the App's creation is complete. This might cause the App to crash when running the dataflow. To fix this, re-assign the necessary permissions to the integration user, or disable the affected fields in the dataflow nodes.

To disable custom fields from a node in the dataflow:

  1. Navigate to Data Manager | Connect.
  2. Open the affected node and deselect the affected fields from the list.
  3. Click Continue.
  4. Run the Dataflow.
Do you want to include the amount of revenue recognized and the amount of cost amortized for projects in the Project Reporting dataset?  

The fields that contain the recognized to date and the amortized to date values are determined using the Revenue Management settings record for the Project object. This requires access to Revenue Management objects and fields in your org. It also requires access to the fields that contain the values on the Project object.

Note 1:

Choose whether to include Revenue Management fields in the Project Reporting dataset. Depending on how your org is set up, up to four fields might be included

  • Project Cost Amortized
  • Project Revenue Recognized
  • Project Total Cost Amortized
  • Project Total Revenue Recognized
Note 2:

The source of these fields is determined using your Revenue Management settings for the Project object. If a source field is not specified in the settings records, the field is not included in the Project Reporting dataset. In addition, if you have multiple settings records for the Project object, you must ensure that all of the records have the same values for the relevant source fields. For more information about these fields and how they are populated, see Project Reporting Flow Intermediate Processing and Project Reporting Dataset PSA Analytics Output Fields.

Note 3:

This requires access to Revenue Management objects and fields in your org. It also requires access to the fields that contain the values on the Project object. Both you and the Integration User must have PSA and Revenue Management licenses, as well as access to the relevant objects and fields.
Which additional fields from the Contact object do you want to import?  

You can select one or more additional fields from the Contact object. These are added to the Billings, Capacity, Utilization, and Utilization Results datasets. Encrypted and multi-select drop-down fields are not supported. You must assign read-access permission to the Integration User to add user-generated additional fields to these datasets. When you import packaged additional fields, they are prefixed with the originating object's name, unless this is already present in the field name. Lookup packaged fields are appended with "Name", and ID fields are appended with "ID", unless already present in the field name.

Note 1: Select one or more additional fields from the Contacts object to include in your PSA Analytics datasets. These are stored on the following datasets:
  • Billings
  • Capacity
  • Utilization

Note 2:

To visualize the data in Analytics, ensure that the Integration User and the user have the necessary permissions to view the selected fields. If you select a field that is a lookup to an object outside of PSA, the Integration User also requires a license to that object.

Note 3:

The additional fields you import from the package receive a label identifier that states which object (Project or Resource) the field belongs to. For example, if you import an additional field from the Resource (Contact) object called "Start Date", after importing it to the label identifies the field as "Resource Start Date" in Analytics. If the imported field already contains an identifier as part of its regular label this feature does not apply. For example, if you import an additional field from the Project object called "Project Manager Name", after importing it into Analytics the label for this field remains the same in PSA Analytics.
Do you want to append your user-generated custom field labels with a suffix? *

You can choose whether to append your custom fields with a suffix. This suffix indicates that they are user-generated custom fields, and the object they are derived from. For example, a user-generated custom field "Location" from the Project object would have the label "Location [ProjectCustomField]".

Note 1:

Choose to append the custom fields you import into PSA Analytics with a suffix tag to easily identify them.

This suffix only applies to the custom fields you create for PSA objects. If you import a managed field from the PSA, the suffix is not applied. Instead, managed fields receive a label identifier.

When you run the PSA Analytics app template to create an app, a dataflow is generated. This dataflow is named according to the app name you provide. During the app creation, you can use the configuration wizard to enable several optional features such as additional dashboards and datasets.

The following dashboards, datasets, and lenses are generated:

Generated Assets

Package

App Template

Dashboard

Dataset
Business Analytics PSA Analytics
  • PSA Utilization Analytics
  • PSA Utilization Analytics Capacity and Demand Planning
  • PSA Skills Capacity and Demand Planning
  • PSA Backlog
  • PSA Billing Forecasts
  • PSA Billings
  • PSA Capacity
  • PSA Capacity and Demand Planning
  • PSA Overview
  • PSA Project Burnup
  • PSA Project Burnup (Embedded)
  • PSA Revenue Forecast
  • PSA Utilization
  • Total Project Margin (Workspace)
  • Backlog
  • Billing Forecast Details
  • Billing Forecast Summaries
  • Billings
  • Capacity
  • Currency ISO Code
  • Project Margin
  • Project Reporting
  • Resource Skills
  • Revenue Forecast
  • Utilization
  • Utilization Results

When you enable the PSA Analytics Embedded Dashboards app in Feature Console, the following dashboards are created:

Generated Assets

Package

 App Template Dashboards Datasets
Business Analytics PSA Analytics Embedded Dashboards

Revenue Forecast (Embedded)

Utilization Analytics (Embedded)


  • Revenue Forecast
  • Utilization Results