1. What Is Vlocity?
Ans: Vlocity is building industry-specific CRM solutions for cloud and mobile use on top of Salesforce.
These solutions are designed for specific industries such as communications, media and entertainment, insurance and financial services, health, energy and utilities, and government and nonprofits.
2. What are the basic fundamentals of Omni Script?
Ans: OmniScript addresses the basics, like guiding customer service through client onboarding and helping insurance representatives with plan upgrades. It also enables self-service troubleshooting.
Vlocity OmniScript teaches customers how to streamline operations, enhancing service quality by making it faster, more personalized, and more responsive.
3. What is Omnistudio? And How it works.
Ans: Omnistudio is like a toolkit for crafting custom apps on Salesforce, without needing hardcore coding skills. It lets you design and tweak applications for specific industries like communications, insurance, and finance—using a visual, drag-and-drop setup. You can pick your industry, play with the design, integrate it with Salesforce, run some tests, and boom, deploy it for actual use. It’s all about making tailored apps without the coding headache. Also, you can override the Lwc component.
4. How To Improve OmniScript Performance?
Ans: There are several ways to improve the performance of OmniScript.
On the client side, you can reduce the number of conditional views, merge fields, and formulas where possible.
You can also speed up the application of responses by trimming the response JSON.
On the server side, you can reduce the number of elements in the script (a single OmniScript should not exceed 200 elements), run logic on the server where possible (including conditional logic in Integration Procedures and formulas in DataRaptors), and remove unnecessary data by trimming the DataRaptor extract output.
You can also test performance by enabling time tracking. If time tracking is not used in production, you should disable the feature before deploying to production.
5. What’s the Purpose of Remote Action?
Ans: Remote Action, an apex annotation, flags a method for JavaScript remoting. It’s handy for calling apex classes from OmniScript. When troubleshooting OmniScript, the callOut Remote Action kicks in, reaching out to an external system to verify the warranty status for the asset.
6. What attributes need to be specified for the Delete Action?
Ans: Here are the Delete Action features:
ID’s Path (optional)
No ID required
Message: Entity was removed
Delete unsuccessful message
Invalid ID message
Confirmation required
Label for Removal
Message in the Confirmation Dialog
7. What’s packed in OmniScript Designer highlights?
Ans: OmniScript Designer highlights pack a punch with features like the Header, Navigation Panel, Canvas, Build Panel, Properties Panel, Setup Panel, Preview, and Debug. It’s a toolkit that covers all the bases for a seamless design experience.
8. What’s the scoop on crafting a Script Structure?
Ans: Build the script’s logic by structuring a sequence of activities and measures. These actions, whether blocks, inputs, or displays, impact the entire script, handling tasks like receiving, submitting, assessing, and transforming data. And hey, don’t forget, you can also throw in some OmniStudio features and action-specific buttons for that extra functionality. It’s all about creating a well-organized and efficient script.
9. What’s the deal with linking OmniScript and Salesforce?
Ans: Integrating Salesforce knowledge into your OmniScript makes it possible for users to browse and view Salesforce expertise short articles in OmniScript. It additionally supports inquiring lightning knowledge.
10. How do you kick off knowledge base articles outside of OmniScript?
Ans: Access knowledge base articles beyond OmniScript by using the Vlocity OmniScript knowledge base component on a community or lightning page. This component showcases knowledge base articles alongside an OmniScript or as a standalone element. When you open knowledge base articles from an OmniScript, specific details are passed to the component to search and display the articles.
11. How do you seed data into an OmniScript?
Ans: To fill OmniScript areas with data or incorporate hidden nodes, use the seed data JSON feature in the OmniScript setup. It’s perfect for fixed values during the first OmniScript loads. If you’re setting values with formulas or data entered later on, explore other options post-initial loads.
12. What’s the deal with Stateful OmniScripts?
Ans: Stateful OmniScripts are essentially LWC OmniScripts that store the state of an OmniScript in the URL. You can achieve this by default setting the c_step parameter to the name of an active step.
13. Tell me about Navigate Action Properties.
Ans: Navigate Action comes with a bunch of properties, including Button Variant, Icon name, Page Reference type, Replace existing page in browser history, Component name, Target Parameters, Article URL, Article Type, Page Name, Tab Name, Object API Name, Object Action, Filter name, and Record Action.
14. What’s the scoop on Remote Action properties?
Ans: Remote action properties include things like Remote Class, Remote Method, Remote Options, Extra Payload, Invoke Mode, Send Only Extra Payload, Show Toast on Completion, and Use Continuation. Now, what’s up with Set Errors Properties? Well, it does things like merging fields from the previous step, assigning literal values, concentrating values, providing the output/result of formulas and functions, and setting values to expressions that link the options.
15. How do I launch the OS?
Ans: The operating system can be launched from various places—record webpage, LWC, lightning, community, or even an external system. To get the OS URL, just hit “how to launch” on the OS webpage’s right side, open the popup, and voila, you can copy the URL to launch the OS from anywhere.
16. When should Integration Procedures be used in Vlocity?
Ans: Consider using Integration Procedures in Vlocity if:
Data transformation requires more than just formulas; additional conditions dictate filtering or calculations.
Interaction with both read and write sObjects is necessary, requiring a minimum of two DataRaptors.
The involved sObjects lack a specific detailed relationship.
JSON node mappings are complex and involve multiple steps.
Actions like calling a REST API, sending emails, merging lists, handling errors, etc., are needed.
17. Tell me about Integration Procedures.
Ans: Integration Procedures are like server-side wizards—they execute multiple actions in one go, merging outputs from various APIs and orchestrating multi-step calculations. Plus, they’re versatile, serving as a data source for OmniScripts, FlexCards, APIs, or Apex.
18. Can you explain Integration Procedures?
Ans: Integration Procedures are server-side processes that efficiently perform multiple actions in one server call, combining output from various APIs and managing complex calculations. They can serve as data sources for OmniScripts, FlexCards, APIs, or Apex.
19. Why choose to navigate to a community login or logout?
Ans: To guide users through authentication in an OmniScript, navigate to a community login or logout. You can preview the OmniScript by activating it and placing it in a community.
20. How do I navigate to a Record Page?
Ans: In the “Page Reference type” section, hit “Set to Record,” then add a “Record Id” field for merge fields support. Finally, click on the action property to pick the action you want to invoke.
21. When do we use Integration Procedures in Vlocity?
Ans: Use Integration Procedures in Vlocity when you need:
- More than just formulas for data transformation; additional conditions for filtering or calculations are required.
- Interaction with both read and write sObjects, involving at least two DataRaptors.
- SObjects lack a specific detailed relationship.
- Complex JSON node mappings with multiple steps are involved.
- Actions such as calling a REST API, sending emails, merging lists, handling errors, etc., are necessary.
