| Creates a link to the Vault document with an ID of 20. Creates a link to the Vault document with an ID of 87. |
Welcome to our Presentation
``` ```css body { font-family: Arial, sans-serif; margin: 20px; } h1 { color: #336699; } #content-area { margin-top: 20px; padding: 15px; border: 1px solid #cccccc; background-color: #f9f9f9; } ``` ```javascript /* Veeva Multichannel JavaScript Library (Conceptual) */ // This is a placeholder for the actual Veeva library functions. // In a real scenario, you would import or include the Veeva library. var Veeva = { CLM: { getData: function(callback) { // Simulate fetching data setTimeout(function() { callback({ "slideTitle": "Introduction", "slideText": "This is the first slide of our CLM presentation." }); }, 500); }, openLink: function(url) { console.log("Opening link: " + url); window.open(url, '_blank'); } } }; /* Custom script.js */ function renderSlide(data) { document.getElementById('content-area').innerHTML = \ '' + data.slideTitle + '
' + \ '' + data.slideText + '
'; } function nextSlide() { // In a real CLM, this would navigate to the next slide data. // For this example, we'll just re-render with new dummy data. Veeva.CLM.getData(function(data) { renderSlide(data); }); } // Initial slide load Veeva.CLM.getData(function(data) { renderSlide(data); }); ``` -------------------------------- ### Reference Shared Resource in HTML Source: https://vaultcrmhelp.veeva.com/doc/Content/CRM_topics/Multichannel/CLM/CreatingContent/SharedResources Demonstrates how to reference shared resources like images, scripts, and stylesheets within HTML files using a specific path structure. This method is used by Content Creator Users to link to externally managed assets. ```html
```
--------------------------------
### Landing Page JavaScript for Multichannel Activity Tracking
Source: https://vaultcrmhelp.veeva.com/doc/Content/CRM_topics/Multichannel/ApprovedEmail/ReportAE/TrackMCActivitesAE
This HTML snippet containing JavaScript must be added to the external, customer-owned landing page. It ensures that Multichannel Activities are appropriately tracked by embedding an iframe viewer for the multichannel message. The script dynamically loads the necessary Veeva JavaScript and initializes the Multichannel Message frame.
```html
```
--------------------------------
### Define AR Scene Structure in JSON
Source: https://vaultcrmhelp.veeva.com/doc/Content/CRM_topics/Multichannel/CLM/CreatingContent/DefineAR
This JSON snippet demonstrates the structure for defining an AR scene within the AR_configuration.json file. It includes the scene's ID, name, and a placeholder for associated models. This configuration is fundamental for setting up AR presentations.
```json
"scenes" : [
{
"id" : "scene.L001",
"name" : "Veeva Codesign",
"models" : [...]
}
]
```
--------------------------------
### Touch Trigger Configuration in JSON
Source: https://vaultcrmhelp.veeva.com/doc/Content/CRM_topics/Multichannel/CLM/CreatingContent/DefineAR
Sets up touch triggers for interacting with models, specifying the trigger type, ID, associated object name, and a list of actions (e.g., animations, audio playback) to perform upon activation.
```json
"touch_triggers":[
{
"type":"trigger",
"id":"trigger.left.door",
"obj_name":"NovaSeq_2_a_Left_Door",
"actions":[
{
"type":"animation",
"id":"NovaSeq_2_a_Right_Door-anim"
},
{
"type":"audio",
"id":"audio.right.door.start"
}
]
}
]
```
--------------------------------
### Token Syntax for Vault CRM Speaker Contracts
Source: https://vaultcrmhelp.veeva.com/doc/Content/CRM_topics/Events/Speakers/SpeakerContractGeneration
Demonstrates the various token formats supported in .docx speaker contract templates for Vault CRM. These tokens dynamically populate contract information based on event, speaker, contract, or user data.
```text
{{ObjectAPIName.FieldAPIName}}
{{currentDate}}
{{currentTime}}
{{timeZone}}
```
--------------------------------
### JSON: AR Scene Audio File Configuration
Source: https://vaultcrmhelp.veeva.com/doc/Content/CRM_topics/Multichannel/CLM/CreatingContent/DefineAR
Configures audio files to be played when specific actions are initiated in an AR scene. Requires specifying the audio type, ID, and the associated sound file name.
```json
"audios":[
{
"type":"audio",
"id":"audio.shot",
"file_name":"ArrowHit02.wav"
}
]
```
--------------------------------
### Populate Allowed Products Field by Call (Vault CRM)
Source: https://vaultcrmhelp.veeva.com/doc/Content/CRM_topics/Call_Reporting_2/Restrictions/AllowedProd
This code snippet demonstrates how to populate the 'allowed_products__v' field on 'call2__v' records to define allowed products by call. It uses a double semicolon delimiter for the product list. This configuration ensures that only specified products can be detailed or sampled on a call.
```CRM
Populate the **allowed_products__v** field on the appropriate call2__v records with a double semicolon delimited list of the products that are allowed to be detailed or sampled, to define allowed products by call (optional). The format of the products in the field must be as follows: Product1;;Product2;;Product3;;. For example, Cholecap;;Restolar;;Narbrax;;
```
--------------------------------
### Define Object Recognition Triggers in JSON
Source: https://vaultcrmhelp.veeva.com/doc/Content/CRM_topics/Multichannel/CLM/CreatingContent/DefineAR
Lists the names of objects used to trigger object recognition software when placing a model. This array contains configuration objects for each reference object.
```json
"reference_objects":[
{
"name":"eyeball_marker_rounded_small.arobject"
},
{
"name":"eyeball_marker_dark.arobject"
}
]
```
--------------------------------
### Approved Email Receipt Template Tokens for Call Samples
Source: https://vaultcrmhelp.veeva.com/doc/Content/CRM_topics/Multichannel/ApprovedEmail/SendAE/EmailReceiptsforSignatureTransactions
This snippet demonstrates how to use the `insertCallSample` token within an Approved Email Receipt template to display call sample details. It shows how to add custom table headers and filter transaction line items based on product type and other attributes. This is useful for organizing multiple sample tables within the email.
```html
{{insertCallSample[tableHeader=Samples Left Behind,filterProductType=Sample,Quantity_vod__c,Product_vod__r.Sample_U_M_vod__c,Product_vod__r.Name,Product_vod__r.Manufacturer_vod__c,Product_vod__r.Distributor_vod__c]}}
{{insertCallSample[tableHeader=Samples Ordered,filterProductType=BRC,Quantity_vod__c,Product_vod__r.Sample_U_M_vod__c,Product_vod__r.Name,Product_vod__r.Manufacturer_vod__c,Product_vod__r.Distributor_vod__c]}}
``` -------------------------------- ### Insert Call Sample Formatted Date/Time Token Source: https://vaultcrmhelp.veeva.com/doc/Content/CRM_topics/Multichannel/ApprovedEmail/CreatingContent/ConfigTokens Allows specifying date and time formats for call sample records when they are Date or Date/Time types. Refer to 'Formatting Tokens to Display Date and Time' for format details. Supported in 'Receipts'. ```email-templating {{insertCallSample[Column1,Column2(FORMAT)]}} ``` -------------------------------- ### Insert Call Sample Filtered Table Token Source: https://vaultcrmhelp.veeva.com/doc/Content/CRM_topics/Multichannel/ApprovedEmail/CreatingContent/ConfigTokens Filters call samples based on a specified product type before rendering them in a table. Different columns can be specified for each filtered table. Supported in 'Receipts'. ```email-templating {{insertCallSample[filterProductType=Sample,quantity__v,product__v.name__v,product__v.manufacturer__v]}} ``` ```email-templating {{insertCallSample[filterProductType=Educational Material,quantity__v,product__v.name__v]}} ``` -------------------------------- ### Disable Calls for a Single Account Type (Veeva Settings) Source: https://vaultcrmhelp.veeva.com/doc/Content/CRM_topics/Call_Reporting_2/Restrictions/RcType This example demonstrates how to disable all call report entry points for a specific account type by listing only the account object type in the `allowed_call_record_types__v` Veeva Setting. This is useful when calls are not supported for a particular account type. ```plaintext professional__v ``` -------------------------------- ### Populate Allowed Products Field by Territory (Vault CRM) Source: https://vaultcrmhelp.veeva.com/doc/Content/CRM_topics/Call_Reporting_2/Restrictions/AllowedProd This code snippet illustrates how to populate the 'allowed_products__v' field on 'tsf__v' records to define allowed products by territory. Similar to call-specific configuration, it uses a double semicolon delimiter for the product list. This ensures that users can only detail or sample specific products for accounts within a given territory. ```CRM Populate the **allowed_products__v** field on the appropriate tsf__v records with a double semicolon delimited list of the products that are allowed to be detailed or sampled, to define allowed products by territory (optional). The format of the products in the field must be as follows: Product1;;Product2;;Product3;;. For example, Cholecap;;Restolar;;Narbrax;; ``` -------------------------------- ### JSON: AR Scene Model Definition Source: https://vaultcrmhelp.veeva.com/doc/Content/CRM_topics/Multichannel/CLM/CreatingContent/DefineAR Defines a model within an AR scene, specifying its ID, name, path, assets, and file extension. The file extension must be either '.dae' or '.obj'. This structure is used to list multiple models. ```json "models":[ { "id":"LogosCodesignVeeva", "name":"LogosCodesignVeeva", "path":"Models", "assets":"Logos", "file_extension":"dae" } ] ``` -------------------------------- ### Custom Text Content Token Picklist Source: https://vaultcrmhelp.veeva.com/doc/Content/CRM_topics/Multichannel/ApprovedEmail/CreatingContent/ConfigTokens Allows picklist values to be populated by Content Tokens from Account, User, or User_Detail__v objects. Special characters like { and } are replaced with #. HTML tags are not supported. ```email-templating {{customText[##accTitle## ##accFname## ##accLname##, ##accCredentials##|##accTitle## ##accLname##|##accFname##]}} ``` -------------------------------- ### Configure Allowed Call Record Types (Veeva Settings) Source: https://vaultcrmhelp.veeva.com/doc/Content/CRM_topics/Call_Reporting_2/Restrictions/RcType This example shows how to configure the `allowed_call_record_types__v` Veeva Setting to restrict call reporting for specific account and call object types. It uses a double semicolon delimited list format. This setting is crucial for enforcing call restrictions at the administrative level. ```plaintext hospital__v,meeting_brief__v,event__v;; ``` -------------------------------- ### Sorting Contract Lines in Templates Source: https://vaultcrmhelp.veeva.com/doc/Content/CRM_topics/Events/Speakers/SpeakerContractGeneration Shows how to define the sort order for contract line records within a .docx template. Sorting can be based on multiple fields in ascending or descending order. ```text {{contract_line__v.service_name__v