The Matik App for Salesforce enables your Matik end users to generate presentations directly from Salesforce (SFDC) without having to log in and locate a template within Matik. Presentation inputs can be auto-populated from mapped salesforce fields, saving time for end users by ensuring everything they need is all in one place.
When set up using the recommended configuration in this guide, a "Generate Matik Presentation" action button will be placed on the Account object in your Salesforce instance. Upon clicking, an in SFDC modal allows users to select a template, modify and review inputs, and generate a Matik presentation. Additionally, a "Presentations" list will display all presentations generated for a specific account in the Related Lists section of the Account.
The Matik App for Salesforce is compatible with all template types except Mail.
To set up the Matik App for Salesforce, you must be a Salesforce Admin with permission to install application packages and configure Salesforce objects and layouts. A User with a System Administrator profile or User with “Customize Application” Profile permission will suit. The Matik App for Salesforce only works with Salesforce Lightning and is not supported on the classic version of Salesforce. You must also be a Matik Producer Admin to set up and configure. All end users using the Matik App for Salesforce must have an active Matik seat and will have to sign in to the Matik web application at least once to authorize their Matik account on Salesforce.
The setup of the Matik App for Salesforce mapped to the Account object includes these steps, which are detailed in this article:
- Install the Matik Package in Salesforce
- Assign Permission Sets
- Connect to your Matik Instance
- Authorize your Matik User
- Add Matik Application Components to your Object's Layout
- Map Matik Inputs to Salesforce Fields
There is additional information in the sections below on:
- Generating Presentations
- Managing Users and Presentations
- Presentation Reporting in SFDC
- Mapping the Matik Application for Salesforce to Additional Objects
- Common Error Messages
Install the Matik Package in Salesforce
Navigate to the Matik Salesforce AppExchange Page. (Or search for Matik on the SFDC AppExchange Website)
Click "Get It Now" and follow the onscreen instructions to sign in to SFDC and install the app on your desired Salesforce instance.
When the Matik Application is installed, it will create a few new SFDC components: A Presentation object, a lookup relationship between the Presentation object and the Account object, a "Create Matik Presentation" action on the Account object, and Matik Admin and Matik User permission sets.
The Matik Application will also create a 'Matik Presentation' record type on the Task object. If you do not already have a record type on the task object you will need to also create a default record type for your existing Tasks and backfill. Please also ensure your profiles have access to both record types so users can see and create tasks.
Assign Permission Sets
For Admin Users in Matik, assign the “Matik Admin” permission set for Salesforce Users. For End Users in Matik, assign the “Matik User” permission set for Salesforce Users. This task may be delayed if you do not want users to have access until the Matik App is properly configured. Please ensure users setting up the Matik app have the proper permission set at this time (including yourself, if applicable). See this SFDC help article for more details on assigning permission sets.
Note: Permission Set must match Matik’s user permissions for the app to work correctly.
Connect with your Matik Instance
Once the Matik package has been installed in Salesforce, the Matik App will be available in the App Launcher. A Salesforce Admin with Permission set “Matik Admin” will have access to the Setup Tab and can proceed with App configuration.
Open up the Matik SFDC App and navigate to the Setup tab. Copy the Redirect URI that is displayed there. Click on the link above redirect URI, "Matik Client Settings" and on the opened page, click “Add New Client”.
Populate Name, Scope, and redirect URIs with needed values and click “Add Client”. Note: For new Clients, it is required to add both values from the “Scope” picklist, so Admins and End Users will be able to generate presentations.
After clicking "Add Client", Matik will provide you with a “Client Secret” and a Client ID. Copy and paste those into the “Client ID” and “Client Secret” fields within Matik Setup in Salesforce. After populating “Client ID” and “Client Secret”, click “Save” to save the credentials:
Authorize Users
Next, navigate to the authorize users section. Ensure you are signed into Matik on the same browser as Salesforce and click "Authorize User".
A new window will open to a Matik page asking if you would like to allow Salesforce to access Matik. Click "Grant Access"
Map Matik Inputs to Salesforce Fields
If desired, you may skip this step for now. Note that it is necessary for Matik to pull information into Matik Inputs from the object page it is on.
The next step is to map Salesforce fields to Matik inputs. Mapping fields to inputs allows Matik to auto-populate presentation values based on the SFDC object page that the Matik app is called from by the end user. For example, let's say I want end users to generate Matik presentations from an Account object page and my presentations in Matik have the inputs: Customer Success Rep, Account Name, and Number of Seats. Mapping those inputs to Salesforce fields allows them to auto-populate from the Salesforce object when a presentation is generated.
Mapping by All Inputs vs. Mapping by Template
Input <> SFDC mapping can be done with either all inputs, which will apply to all templates in Matik, or on a template-specific basis. Mapping to all inputs will apply the mapping to every template in your Matik instance, whereas mapping by Template will only map inputs in the selected template, even if that input exists in other templates.
Map Matik Inputs to SFDC Fields
- Select either (1) "All Inputs" or "By Template"
- (If By Template) Select the Template you would like to map inputs (3)
- Select the Matik input you would like to map
- If you want to allow users to override the value received from the mapping, toggle the "Enable Value Override" switch on. When this switch is toggled off, end-users creating a presentation cannot change the input value pulled from salesforce. "Read Only" will be displayed next to these inputs
- Under the Fields Mapping section, select the appropriate object you would like to map to
- Search for a field or select one from the dropdown. If you select another Salesforce object, you must select a field from the object.
- If your input is a Matik Mapped input (e.g. a different value is inserted in dynamic content than what is displayed to the end-user), map your input in SFDC directly to the final field entered in your dynamic content.
- (Optional) Enter a Default Value for the field. This value will be populated if the mapped salesforce field is empty. This may also be filled out for any unmapped fields, however, if value override is enabled, end users will not be able to change this value.
- Click "Save"
Repeat the above steps for all inputs and all templates you wish to be mapped. End users will have to fill out any inputs required for a presentation that are not mapped when generating the presentation.
The values in Salesforce mapped to Matik inputs must be an exact match for input mapping to work properly. For example, Consider an "Account_Name" Matik input mapped to "Account Name" in Salesforce. In Salesforce, there is an account named "Google LLC", however, in the data sources that use the input, the account is listed as "Google". This will likely cause errors when generating the presentation depending on how Matik is configured. If possible, use identifiers for mapping, such as Account ID, rather than names, and perform data quality checks on all mapped fields to ensure matching.
Add Matik Application Components to your Object's Layout
You will need to be a Salesforce Administrator to perform the following tasks. Please refer to SFDC's documentation on Page Layouts for SFDC specific details.
First, add the presentation related object to "Related Lists"
- Go to the "Setup" -> "Object Manager"
- Select the object you would like to add the button to (ex. Account) -> Page Layouts -> Click "edit" on needed layout* -> Add "Presentation" Related list to related lists section of the layout.
*You will likely have several layout configurations in your instance of Salesforce. Work with your Salesforce Admin to determine which layouts are appropriate for Matik features.
Next, add the "Generate Matik Presentation" action button to the Account layout (or layout you are adding the Generate Matik Presentation action to)
- Go to the "Setup" -> "Object Manager"
- Select the object you would like to add the button to (ex. Account) -> Page Layouts -> Click "edit" on needed layout* -> Mobile and Lightning Actions -> Add “Create Matik Presentation” button to the buttons section of the layout.
*You will likely have several layout configurations in your instance of Salesforce. Work with your Salesforce Admin to determine which layouts are appropriate for Matik features.
Generating Presentations
Once the Matik App for Salesforce is configured, generate test presentations to ensure the application and input mappings are configured correctly. See Generating Presentations with the Matik App for Salesforce.
Managing Users and Presentations
Users are added to the Matik Application for Salesforce by being assigned the Matik Application Permission set and being a part of a Page Layout with the "Create Matik Presentation" button added. Each user must have their own Matik account and will be required to authorize their account with SFDC.
The presentations available to that user in Matik will mirror the presentations available to the user in Matik. Admins are still required to manage the presentation view status to end users through the Matik website.
Presentations Import
Presentations created in the Matik app outside of the Matik App for Salesforce will not be automatically be displayed in the corresponding SFDC object. They can, however, be imported into salesforce and mapped to the correct object. Imported presentations will appear as new presentation objects in SFDC.
To import presentations into Salesforce:
- Go to the Matik App for SFDC Setup page.
- Scroll down to the Presentations Import section.
- Apply any desired filters to locate the presentation(s) you want to import, then click Search.
- Note: Only presentations with inputs that contain values matching the relevant Salesforce Object ID can be directly mapped and imported into that specific Salesforce record.
- Presentations without a matching input can still be imported, but they will not be linked to a specific Salesforce object.
- Select the input(s) you'd like to use to map presentations to the appropriate SFDC object.
- If you want to exclude any non-mapped presentations, check the "Import mapped presentations only" box.
- Click Import to start the process.
Presentation Reporting in SFDC
The Matik App for Salesforce will install three new report types, which can be used to track Matik usage and presentation effectiveness. Note that only presentations generated from within SFDC will be reflected in these reports. Presentation report types can be found by searching "Presentations" in the "All" Category.
Mapping the Matik Application for Salesforce to Additional Objects
When the Matik app for Salesforce is installed, the Account object is automatically configured for mapping. Mapping to additional objects allows an SFDC user to generate presentations from the object page based on input mappings to the object.
You must be a Salesforce administrator to add additional objects to be mapped to Matik inputs.
Setup
Manually create the lookup relationship between the Presentation object and the Object you wish to map to and create the generated presentation action using the steps below:
Create the Lookup Relationship
- Go to the "Setup" -> "Object Manager"
- Select"Presentation"(matik__Presentation__c) Object
- Go to the "Fields & Relationships" and create a new field
-
- Step 1: Choose Data Type: Lookup Relationships
- Step 2: Related To: (Select the object you wish to generate a presentation from e.g. Account if you want the "Generate Matik Presentation" button on the account page)
- Step 3: API Name for the Lookup object: Name it in accordance with the desired object. e.g. "Account__c" or "MyCustomObjName__c" (Salesforce will append "__c" automatically)
- Steps 4-6: (Label should match desired object name)
-
Add Create Presentation Action
- Go to the "Setup" -> "Object Manager"
- Select the object you wish to map to
- Go to "Buttons, Links, and Actions"
- Create "New Action":
-
- Action Type: Lightning Web Component
- Lightning Web Component: matik:createPresentation
- Label: Create Matik Presentation
-
When completed, follow the steps under Add Matik Application Components to your Object's Layout and Map Matik Inputs to Salesforce Fields for your respective object. When additional objects have been added for mapping, Matik inputs must be mapped to all objects a presentation is desired to be generated from.
Health Check
The Health Check section of the Matik App for Salesforce setup page will alert admins when there is an issue with the Matik App. The most common issue is the Matik status refresh job getting suck. Using the Matik logs you can identify and resolve issues by checking the job queue or forcing a manual refresh Matik presentation statuses.
Common Error Messages
Something goes wrong!
An external endpoint error occurred: [401]
This error message typically occurs when your Matik account has been disconnected from the Salesforce app. To resolve, refresh Salesforce. When you press the "Generate Matik Presentation" button again, you will be prompted to authorize Matik.
Ensure you are signed into your Matik account on the same browser and click "Authorize Now".
If this does not resolve your issue, please reach out to Matik Support (support@matik.io) for assistance.
Comments
0 comments
Please sign in to leave a comment.