When using Google Drive or Office 365 with Matik, Admins can choose default save locations for generated content on the enterprise, user group, and template level. Additionally, end-users have the ability to choose a custom folder for an individual and bulk generation.
Prioritization of Default Save Locations
When multiple defaults are configured, Matik will resolve to the most granular setting. Matik uses the following priority to resolve to a single default folder for the generation:
- Template-specific default: If the template has a default folder, it will be used.
- User group default: If the generating user's group has a default folder, it will be used.
- Enterprise default: If the enterprise has a default folder, it will be used.
- Matik Presentations folder: If none of the above are set, the generation will default to the user’s "Matik Presentations" folder in Google Drive or Office 365.
If a user is part of multiple User Groups with different save folders, Matik will select one of those groups randomly. Therefore, if you expect to frequently assign users to multiple user groups, we recommend using template-level or enterprise-level settings to configure default folders.
Here is the logic as a diagram:
End users can manually override any defaults during the generation process by selecting a different folder.
Template Specific Save Locations
Navigate to the template and click on the ellipsis menu in the top right. Select Generation Settings.
Click on the Folder option and specify where you want presentations to be saved. Be sure to click on Update Settings when finished.
The Folder card gives you two ways to set the destination:
- Select Folder: Browse your connected Google Drive or Office 365 account and pick a folder.
- Set Folder URL: Paste a folder link instead of browsing. The link can point at one fixed folder, or it can reference dynamic content and inputs so that each generation resolves to a different folder.
Example use cases
Template-specific save locations cover two different needs:
- One fixed destination. Everything generated from your QBR template should land in a shared QBR folder, whoever generates it. Pick that folder under Select Folder, or paste its link under Set Folder URL.
- A different destination for each account. Each QBR should be saved in the folder that belongs to that account, and the folder link is already stored as a field on the Account record in Salesforce. Build a text dynamic content that returns that field, then reference it in the folder URL so each generation routes itself.
The second case is what folder URLs with dynamic content are for. In a bulk generation each row resolves its own folder, so a single run can file decks for 50 accounts into 50 different folders.
Setting a folder by URL
Beta Feature: Setting a template's save folder by URL is currently in beta. Contact your Technical Account Manager if you are interested in access.
Select the Set Folder URL tab and paste a folder link into the Folder URL field. For one fixed destination, paste the link as it is:
https://drive.google.com/drive/folders/1A2B3C4D5E6F7G8H9Matik reads the folder out of the link when you save, so a fixed URL behaves the same way as a folder you picked from the browser.
Routing each generation to a different folder
To send each generation somewhere different, reference dynamic content or an input inside the URL. Matik replaces the reference at generation time, then saves to whatever folder the finished link points to.
| Reference | What it does |
|---|---|
{{dynamic_content_name}} |
Inserts the value returned by a text dynamic content. That content's query runs as part of the generation. |
&:input_name |
Inserts the value of an input. No query runs. |
References can appear anywhere in the field and can be mixed with ordinary text, so the whole value can be one piece of dynamic content, or dynamic content can supply only part of the link. For the Salesforce example above, a text dynamic content that returns the account's folder link is referenced on its own:
{{account_folder_url}}If the Salesforce field stores only the folder ID rather than the full link, compose the link around it:
https://drive.google.com/drive/folders/{{account_folder_id}}Example: saving each QBR to its account's folder
This walks through the Salesforce case above, where each account's folder link is stored on the Account record in a custom field called Matik_Folder_URL__c.
-
Create a text dynamic content that returns the folder link. Add a new Dynamic Content, name it
account_folder_url, select your Salesforce data source, and set the output type to Text. On the API tab, set Source API to Objects and fill in:-
Select Salesforce Object:
Account. - Fields to return: the field that holds the folder link, for example a custom field named Matik Folder URL. Select one field only, since a folder link has to resolve to a single value.
-
Filters: filter the Account on the field that identifies the account you are generating for, and enter your input as the value by typing
&:account_name. -
Result Limit:
1.
For more complex lookups you can use the Query tab and write SOQL instead. See Using Salesforce (SFDC) in Dynamic Content.
-
Select Salesforce Object:
- Preview the dynamic content. Run it against a sample account and confirm it returns one folder link that looks correct. If it returns several rows or a blank value, tighten the filter before continuing.
- Open the template's folder settings. Go to the template, click the ellipsis menu in the top right, select Generation Settings, and open Folder.
-
Select the Set Folder URL tab and enter the reference on its own:
{{account_folder_url}} -
Click Validate URL. Because the dynamic content needs an account to run, Matik asks for a sample value for
&:account_namefirst. Enter a real account name, and Matik resolves the link and reports the folder it found. - Click Update Settings to save.
Generating for a single account now saves the deck to that account's folder. In a bulk generation each row supplies its own &:account_name, so every deck lands in its own account folder in one run.
Office 365 templates
Office 365 templates support fixed folder URLs. Paste a SharePoint or OneDrive sharing link, which is the link you get from Share or Copy link on the folder.
Coming soon: dynamic content and inputs in the folder URL are not yet supported for Office 365 templates. If you include them, Matik tells you they are not supported yet and does not save the URL. Use Select Folder or a fixed folder URL on Office 365 templates in the meantime.
Validating a folder URL
Click Validate URL to check a link before you rely on it. Matik confirms that the link is a folder it can read and reports the folder it found, for example URL verified. Folder found: Account QBRs.
When the URL references dynamic content or inputs, Matik asks you for a sample set of input values, resolves the link against them, and then checks the resulting folder. This tests one example, not every account, so a link that validates can still fail for an account whose data is missing or wrong.
Note: Validation confirms that the link is a real folder and that you can reach it. It is a single check at the time you run it, so it will not catch every problem. Anyone generating from the template still needs access to the destination folder at generation time, and a folder that is later moved, deleted, or reshared is not rechecked.
Validation is optional. You can save a folder URL without validating it first, though Matik still rejects a link it cannot read as a folder.
What end users see
When a template saves to one known folder, the generation form names that folder and lets the user pick a different one.
When a template routes by dynamic content or inputs, there is no single folder to name, so the form says that presentations will be saved to folders based on the input values provided, and offers a Change Folder button instead. Choosing a folder there overrides the template's routing for that generation, and every presentation in that run is saved to the chosen folder. Clearing the choice hands routing back to the folder URL.
Limitations
- Standard folder links only. Use a Google Drive folder link or a SharePoint or OneDrive sharing link. File links, My Drive browser URLs, and direct SharePoint site paths are rejected.
- Dynamic routing is Google Drive only for now. See Office 365 templates above.
- Dynamic content must return a single value. Text dynamic content that returns a blank value, multiple rows, or a non-text result cannot be used to build a folder link.
- Template level only. Folder URLs are set per template. Enterprise and user group defaults continue to use the folder picker.
- Unresolved folders fall back. If Matik cannot work out the folder for a generation, that presentation is saved in the default folder for that user instead of failing, and Matik records a warning on the generation so you can see that it happened. In a bulk generation this affects only the rows that could not be resolved.
-
Inputs are cheaper than dynamic content. An
&:inputreference is substituted directly, while{{dynamic_content}}runs a query. Where the value is already available as an input, referencing the input keeps large bulk generations faster.
User Group Default Save Locations
If you are using user groups within Matik you can specify a folder where a specific user groups generated presentations are saved to. Note that you must be a producer admin to edit user groups and their save locations.
Go to Enterprise Settings > Groups and create or select an existing group. At the bottom of the modal window that pops up specify a save location for that group.
.
Enterprise Default
Set a location for your entire enterprise on Matik. Note that you must be a producer admin to edit Enterprise Settings. Go to Enterprise Settings and scroll down to Custom Folder for Generated Presentations. Specify where you want your generated presentations to save.
User Level Default - Matik Presentations Folder
If no other folders are specified, generated presentations will be located in a Matik created folder on each users Google Drive of Office 365 account called "Matik Presentations". End users can override this by specifying a custom generation location before each generation.
Comments
0 comments
Please sign in to leave a comment.