Rule Action: Load To Feature
The purpose of the Load to Feature rule action is to populate the standard Features section on the Customer 360 (C360). The Features section displays a list of products and associated features for end users to quickly see what is licensed and what is enabled for individual customers. Below is an example of the C360 Features section:
(Optional) Reports and Dashboards Overview
Note: this action is not available for Relationships or the R360
We recommend completing the steps in the order presented below if this is the first time you’re setting up the Features section. If you have some elements in place already, you can skip to that step.
Add Feature Definitions
Your product’s features can be configured in Administration > Product & Features. Products represent a group of associated features. Features are considered the distinguishing components of a product.
To start creating feature definitions:
- Navigate to Administration > Product Features. The Features list will be blank by default for new orgs.
- Click New to configure a new feature.
- Complete the form to enable the creation of new product and features. To add new products, click the .
Note: All fields in the form are required. If you have already created a Product Name, use the dropdown “Select Product Name” to select an existing product.
- Continue adding feature definitions as required.
Add C360 Features Section
The 360 Features section allows users to quickly view the currently enabled product features for an individual account.
To add the section:
- Navigate to Administration > 360 Layouts, and select the View where you want to add the section.
- Drag the Feature section to the layout on the right.
Note: Once the section is added, it will appear at the bottom of the layout view within configuration. You can hold & drag it again to reposition within the layout.
- Click the pencil icon and enable the Show In locations where you want the Features section to display. Click Save.
Load to Features via Rules Engine
If you have source data that signifies whether a customer has an enabled feature or product, you can be leverage it to load product features automatically.
To configure a rule to load features:
Navigate to Administration > Rules Engine > click Create Rule.
You may configure a Bionic or Custom rule, but the final rule query should include something like Account:ID, Feature Type, and a field signifying that a feature is enabled, for the best results.
Note: Your rule query does not necessarily have to follow the principle above, as long it is understandable in context that a feature for an account is enabled.
- In the Rule Action: Load to Features page, you will see something like below. Currently, one action can only set one Product-Feature Combo at a time.
Constant and Show Field in Load to Features Rule
- Constant is used to manually set a value. This is usually combined with a Filter Criteria for the desired effect. For example, if an Account has positive report export counts, then set it as an enabled feature as shown in the image below. Constant enables you to pick a value from a simple list of possible options such as Is Feature X licensed or not?, Is Feature X enabled or not? and so on.
- Whereas Show Field enables you to pick the value directly from a field you have queried (by adding to 'Show' in the previous step). The benefit is that if there is a checkbox/boolean field already exist in your source data that shows whether or not it is enabled, the same value will be fetched directly. If you are using the Show Field option, the source field must be of “Boolean” Type, and must be added in Rule Setup “Show” section.
- You must save the configured actions and test the rule to check for expected results before scheduling.
Notes on Removing Features
In order to remove features, the source data and view completely, it needs to be removed by record id from the object via the SFDC Data Loader with an enabled delete operation before removing from Administration > Product Features. Overall data lives in an object called “Customer Features” (JBCXM__CustomerFeatures__c).
Below is a sample report that you could use to pull the Record Ids. Make sure to add a filter on the feature you want to delete. You would then need to export the report and later convert the file into CSV.
- With the CSV file, you can use a SFDC Data Loader to delete the records.