Student Guide

Vlocity Platform Essentials

Doc Version: PE V2.0

 CONFIDENTIAL

Legal Notice
USE OF OUR EDUCATIONAL SERVICES, COURSES, AND TRAINING MATERIALS (COLLECTIVELY REFERED TO AS
“EDUCATIONAL SERVICES”) IS CONDITIONED UPON THE ACCEPTANCE OF THESE TERMS BY YOU (ALSO
REFERRED TO AS “PARTICIPANT”). BY DOWNLOADING, INSTALLING, OR OTHERWISE ACCESSING OR USING
THE EDUCATIONAL SERVICES, YOU AGREE THAT YOU HAVE READ, UNDERSTOOD, AND AGREE TO BE BOUND
BY THESE TERMS OF SERVICE. IF YOU DO NOT WISH TO BE BOUND BY THESE TERMS OF SERVICE, PLEASE
DISCONTINUE USE OF THE EDUCATIONAL SERVICES IMMEDIATELY.
For your review, the terms of service are available at the following URL:
https://vlocity.com/cms/resources/vlocity-university-terms-of-service-2016.pdf

Restrictions on Your Use

You are granted a nonexclusive, nontransferable, revocable, limited license to access and use our Educational Services in
accordance with the Terms of Service (https://vlocity.com/cms/resources/vlocity-university-terms-of-service-2016.pdf). Only
the authorized registrant may participate as a licensee and user of our Educational Services. As a condition of your use of
our Educational Services, you warrant to us that you will not use our Educational Services for any purpose that is prohibited
by the Terms of Service.

Our Proprietary Information

The material, content, and Educational Services provided by us or accessible from this Site and any other website owned,
operated, licensed, or otherwise controlled by us (the “Content”) is our proprietary information or the proprietary information
of the party that provided or licensed the Content to us, whereby we or such providing party retain(s) all right, title, and
interest in the Content.

Accordingly, the Content may not be copied, decompiled, reverse engineered, disassembled, transferred, distributed,
republished, resold, sublicensed, uploaded, posted, used to create derivative works, or transmitted in any way without our
prior written consent or the prior written consent of the Content owner, except that you may print out a copy of the Content
solely for your personal use, including as part of the applicable training or educational program.

Representations; Warranties; Disclaimer

YOUR USE OF OUR EDUCATIONAL SERVICES IS AT YOUR OWN RISK. THE EDUCATIONAL SERVICES ARE
PROVIDED “AS IS” AND WITHOUT WARRANTIES OF ANY KIND, EITHER EXPRESSED OR IMPLIED. WE DISCLAIM
ALL WARRANTIES, INCLUDING ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
PURPOSE, TITLE, OR NON-INFRINGEMENT. WE DO NOT WARRANT THAT THE FUNCTIONS OR CONTENT
ASSOCIATED WITH OUR EDUCATIONAL SERVICES WILL BE UNINTERRUPTED OR ERROR-FREE, THAT DEFECTS
WILL BE CORRECTED, OR THAT OUR SITE AND EDUCATIONAL SERVICES ARE FREE OF VIRUSES OR OTHER
HARMFUL COMPONENTS. WE DO NOT WARRANT OR MAKE ANY REPRESENTATION REGARDING USE, OR THE
RESULT OF USE, OF THE EDUCATIONAL SERVICES IN TERMS OF ACCURACY, RELIABILITY, OR OTHERWISE.
THE EDUCATIONAL SERVICES MAY INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS, AND
WE MAY MAKE CHANGES OR IMPROVEMENTS AT ANY TIME.

Vlocity has made every effort to provide you with a proposal and information that is accurate as of the date of
this document response and within our knowledge. Because our procedures and policies change from time to time, we
cannot guarantee that the information within this document will be identical at the time you enter into a contract
with us. If you choose to use us as your service provider, we will enter into contracts that cover many of the
topics in which you've expressed interest, and those contracts will be the definitive agreements that describe all
aspects of our relationship.

Last Revision: 10/31/18 10:26:10 AM

© 2018 Vlocity, Inc.

Student Guide - Page 2 of 10 Legal Notice

CONFIDENTIAL

Data Flow Diagrams

Data Flow Diagrams Student Guide Page 3 of 10

 CONFIDENTIAL

Student Guide - Page 4 of 10 Data Flow Diagrams

CONFIDENTIAL

Data Flow Diagrams Student Guide Page 5 of 10

 CONFIDENTIAL

Work Patterns for Challenges

Before You Seek Help, Ask Yourself if You Have:

• Followed your naming conventions

• Followed your build plan
• Closely analyzed the key takeaways
• Followed the data trail
• Reviewed the demo video
• Reviewed and followed best practices
• Followed the troubleshooting checklist

Don't Get Discouraged

Have you have followed the challenge work behaviors AND checked through your work for more than 10
minutes but still can't find the problem?
• Reached cognitive overload? Can't remember where you are in the process? Take a break and come
back with a new perspective.
• Sometimes you make a mistake and can't see it yourself.
• If you are in Instructor Led Training, ask a classmate to look at your work and they may find it
quickly.
• Working on your own? View the SAMPLE object in your org and compare it to the one you built.
• Still stuck? Try starting over from scratch. Often you made changes that you forgot about and a clean
slate will help you find them.

Student Guide - Page 6 of 10 Work Patterns for Challenges

CONFIDENTIAL

Vlocity Naming Conventions

Application Convention Examples

DataRaptor Names Requirements: PRFXVerbObjDetail
TRNGTypeAheadCase
• Must be unique within the org.
VPLGetAcctCases
• No spaces
Best Practices
• Use CamelCase – Prefix, Verb, Object and Detail
• Use an action verb and descriptive nouns
• Use abbreviations

DataRaptor JSON Requirements AccountName

Paths CallerName
• Unique in the DataRaptor
OwnerName
• Use ASCII characters AcctBillingStreet
• No spaces (some exceptions) AccountId
CallerId
Best Practices
• Use CamelCase
• Short, descriptive names
• Abbreviate
• For Ids, Specify the object
• If there is more than one extract from an object
type, assign a label to each object
• For Quick Match, use SF field names

OmniScript & Requirements ReadCaseDetails

Integration GetWeatherFcast
• Unique in the script
Procedure Elements
• Use ASCII characters SetErrorProduct
CalcServicePrice
• No spaces (no exceptions)
Best Practices
• See DataRaptor JSON Paths above
• For Actions – VerbObjectDetails with standard
verbs
o DataRaptor: Read, Update, Create, Xform
o HTTP: Get, Post
o Set Values/Errors: Set
o Calculation: Calc
o Email: Send
o PDF: PDFGen
o Remote: Invoke
o DocuSign: DocuSend, DocuSign

Vlocity Naming Conventions Student Guide Page 7 of 10

 CONFIDENTIAL

Vlocity Naming Conventions

Application Convention Examples

Layout Names Requirements: myapp-home-product
myapp-home-kitchen-sink
• Must be unique in the Org
trng-account-console
• Use ASCII characters
• No spaces
• Layout names cannot be changed
Best Practices
• Use lowercase
• Separate by dash (-) for feature or sub feature

Cards Requirements: VPL Product Details

• Combination of Name and Author must be unique in TRNG Account Cases
the Org
• Only one version of a card can be active at a time
• Two cards with the same name cannot be active at
the same time (even though they have different
authors – they are considered versions)
• Card names cannot be changed
Best Practices
• Use descriptive names
• Use Title Case with words separated by spaces

Merge Field Syntax

Application Context Variable Merge Field Syntax Array Notation
Cards Framework params.id {{records.AccountZip}} {{obj[1].ContactName}}
OmniScript & Integration ContextId %Step:Block:Element% %Parent|2:Child%
Procedure

Important Links
Resource Link
Salesforce login.salesforce.com
Vlocity University vlocity-university.litmos.com
Vlocity Success Community vlocitysupport.force.com
ClassMarker https://www.classmarker.com/
Support Center Documentation Corrections docs@vlocity.com
Training Content Corrections vu@vlocity.com

Student Guide - Page 8 of 10 Vlocity Naming Conventions

CONFIDENTIAL

General Troubleshooting Guide

• Activate everything!
• Salesforce hanging up? Reload the Chrome page.
• Use OmniScript Debug Console to trace your data flow.
• Check the spelling of component names.
• Check that abbreviations in variable and component names are always abbreviated and not spelled out in
full. For example, ReadAcctData instead of ReadAccountData.
• Boolean values are case sensitive; check that true and false are all lower case. Do not use quotation
marks when using a Boolean value.
• When troubleshooting with preview mode, remember to Clear Data in OmniScript Designer and View
Data in Card Designer.
• If you are having problems with populating data; check that the variables in your OmniScript or Layout
match those in the associated DataRaptor.

• When working in the Card Designer, if you see a caution icon; hover over it for troubleshooting
guidance.
• In Card Designer preview, if you do not see the cards you expect: check if you are in Design Time or Run
Time, and check if the card is added to a Zone.

Work Patterns for Work

• Vlocity First. Use out-of-the-box Vlocity as much as possible. Use custom Apex as a last resort.
• Look in the Vlocity Process Library for similar processes that you can start with.
• Review the Success Community for documentation and training on any functionality in your project that is
new to you.
• Plan your data flows.
• Plan your naming conventions and follow your team’s guidelines.
• Use best practices from this course and from your team.
• Start small. Build your flows with a few fields first, then add the rest after you have tested the process.
• Use Integration Procedures instead of Apex for REST and SOAP.

General Troubleshooting Guide Student Guide Page 9 of 10

 CONFIDENTIAL

Notes

Student Guide - Page 10 of 10 Notes