 Hello everyone. I am Sanjay Gupta. I welcome you on Sanjay Gupta Tech School. So as we told you in overview session like from this week, we'll be starting regular sessions for Omni Studio. So this is day one session for Salesforce Omni Studio Bootcamp. And I have Abhishek with me who will be majorly delivering the content and we'll try to cover the content in such a way so that we will do some discussions as well so that it will clear all your doubts within the sessions itself. So welcome Abhishek on the platform and I see huge response of the audience in the day zero session. I think it is crossing 3000 views now. So like people are really appreciating this bootcamp and I know this is the latest technology and demanding as well. So people will be benefited with the efforts we are putting in. So with this note like I just want you to introduce yourself with the in front of the community so that if someone who is watching this bootcamp session for the first time so they know like who you are and what all certifications you have done. So over to you. Thank you Sanjay for giving this opportunity. So hi everyone myself Abhishek and I am a Salesforce and velocity developer and I have in total five plus years of experience in Salesforce domain. And I'm a trailer double star ranger as well and I have done some certifications on Salesforce. So I am a only studio developer certified and I have done CPQ specialist service cloud PD-1 and admin as well. So yeah that's all about great. So it is it is very good like if you are learning a technology or tool with a certified consultant. So it is very great because along with certification Abhishek have done work on various projects as well. So I appreciate your efforts Abhishek. So moving on to the next slide if you have any kind of doubt because I'm sure you will be having lots of doubt. And if you want to do practice together so that if you ask question and anyone on your behalf or our behalf like if they know the answer if you want that kind of platform. So you can join this telegram group and here more than 3000 folks are connected who are freshers or like intermediate professionals. So they are learning Salesforce day by day. So join this group and in the next slide like if you want timely notifications just join Sanjay Gupta Tech School on YouTube, LinkedIn, Instagram or telegram whichever is you are using frequently. And all the links are available in the video description so you can go through and please provide review or feedback about the bootcamp so that we get motivated. So that that is available on next slide Abhishek if you go. Yeah. So here some upcoming bootcamp information is also available. So next month I'm planning to have two new bootcamps that will be based on DevOps and AI. Right. So I'm planning those kinds of bootcamps so that you can learn those new skills as well. Okay. So just note like I just want Abhishek to start kickstart the session and I will be like jumping in between so that I can turn the session in discussion mode. So over to you Abhishek. Yeah. So let's go to the next slide. So before starting any of the explanation or introduction about Omni Studio first we will see how to set up or which which which will support Omni Studio tools. Right. So we have a link in this slide. So what you have to do you just have to I mean this link will be provided into the session tracker right Sanjay. So this all access link is available in the session tracker as well. So if you go to the description of this screen that you're watching. So in that stream you will find the first link that is session tracker link and in that session tracker link this session tracker link. You will find this link which will let you have the developer edition all that has Omni Studio pre installed. So if you read the paragraph at bottom left corner. So use these use this space to sign up for a developer edition or that has Omni Studio pre installed. Correct. And I will I will share the link in the chat as well. Okay. Yeah go ahead Abhishek I will be sharing the link. Yeah. So once you sign up on this page and you will you will get the org access where you can do all the hands on exercises. Of Omni Studio tools like majorly they they have four tools omniscripts flex cards data raptors and integration procedures. So whatever whatever introduction practical knowledge we're going to see in our live session. You can do all hands on exercises whenever once you will get the once you will get access to this all. Okay. Let's go back. So let's move on to the next slide. So as we have already seen introduction of Omni Studio in a previous session only. But in a brief I'm going to explain all the things again so that whoever has joined on today's session so that they will get a brief idea. And then we're going to see the introduction of each each and every component of Omni Studio so that we will get idea what exactly and how exactly Omni Studio works. Right. Right. So first of all customer expectations by Omni Studio is it can be accessible anytime anywhere to the company. So what what do I mean by anytime and anywhere. This Omni Studio tools whatever you are building whatever you are developing can be accessed on any any machine which can be a laptop mobile or anything and it can be accessed anytime as well. And and so there are so many industries introduced by Omni Studio or velocity as we as we have seen in the last session. We lost prior to Omni Studio this Omni Studio tools was called as velocity platform essentials. So velocity as a company has given us so many pre-built solutions for different different industries like insurance cloud telecommunication public sector energy and utilities. So this they these pre-built solutions can be accessed at twenty four seven and it any anytime and anywhere. Right. Yeah. Now let's go to the next slide. So yeah. So what Salesforce provides. So as we all know Salesforce provides so many cloud solutions like sales cloud service cloud marketing cloud and commerce cloud but Salesforce prior to Omni Studio or prior to velocity Salesforce haven't given us the industry industry solutions. Right. Like it can be one of the one of the industry can be like financial services health insurance services public sector services. So all those all those industries was untouched by the Salesforce. So velocity came came with an idea. So what they did is they created some pre-built libraries pre-built managed package so that it can be installed on your Salesforce or and whenever whenever a customer or an account wants to build some functionality. Right. Wants to build some build this functionality around these industries so that they don't have to build the build all the functionality from the scratch. So they have given us pre-built solutions for these type of industries and if customer wants to do some customization make some changes. So those all are easy to easy to make on those pre-built functionalities or pre-built libraries. Right. Yeah I think in next slide it is more clearly available. Yeah. Yeah. So industry cloud solution here has like Salesforce cloud specific industry model processes. So what do what do I mean what do I mean by specific industry model. So for example let's say we there is a customer who wants to build their software or functionality by using the velocity solutions on the insurance cloud or the health insurance cloud. Right. So velocity has given us a data model which will support all the all the functionalities that includes in the health insurance health insurance cloud. So for example whenever you are whenever you are going to buy a policy right insurance policy. So what type of things you will face you will be you will be given a code first of all by let's say you want to buy a health insurance for your whole family. So first of all you will be given a code then when you will be agree like this is the premium I'm going to give monthly basis or the annual basis. After that there will be a contract will given to you. So let's say if you have purchased the policy for one year. Right. So they will give you contract. So all these terms like right code contract products policy those all are the objects that have been created by a velocity and that have been given you by the velocity as a prebuilt solution. So that any insurance company can come to any consulting company will say use the industry specific solution given by velocity for insurance cloud and put and build a software for me. And if there if here in there there are some changes or some customization those can be incorporated very easily in on those prebuilt solution and we can we can build it. We can build a software for that customer. Right. Yeah. And I think for each industry that data model implementation is already available in the arc whenever client purchase some licenses. Right. Correct. So whenever once you will be creating your account on that only studio developer addition or you will just you will just get the access to the only studio tools. Now let's say if you want to work on the health insurance cloud. Right. So there will be a separate managed package that will be installed in your or not then you will be able to utilize that prebuilt solutions given by velocity. Yeah. Exactly. So you need to install particular packages for which industry you want to implement the solution. And you might be thinking like what happens if customer purchase licenses from Salesforce. So whenever you purchase licenses from Salesforce so Salesforce provides that already installed in that particular or that you want to request from Salesforce. Right. Yeah. So for example if you are creating your account and developer addition or so you have sales cloud service cloud pre installed. So similarly whenever you purchase some licenses for particular industry cloud. So those those are pre installed in that particular or. Right. On to the next slide. So how how only studio is different from Salesforce components. Right. So let's say whenever whenever you are working in with the Salesforce components. Right. Like apex classes SQL queries DML operations lightning web components or components. Right. All are the Salesforce Salesforce core components by which you will be building a solution or building a functionality for any of the customer. Right. So again at the same time only studio is also giving some core components like data actors flex card integration procedures and only scripts. So how these components are different when we are comparing these components with the Salesforce components. Right. So so the major difference between those two components are all the Salesforce components requires knowledge around how to how to write code. So you must be having some some language knowledge, some concepts knowledge so that you can write the logic in the apex code LWC lightning web components so that you can write the SQL queries. You must have knowledge around the database management as well. Right. But when you are working with the only studio these all tools are point and click tools. You don't need to write any any sort of code. If you want to create a if you want to create a web page, you don't need to write a single line of code when you if you want to create a web page or a UI page for a customer. And at the same time if you want to do it with the Salesforce components, you must be having knowledge about lightning web components. You must be having knowledge about apex classes, SQL queries, all these things. So the main benefit of using only studio is these all tools are drag and drop and point and click tools. And other other advantages, it increases the user productivity. Right. How it increases the user productivity. So let's say if you're building some some solution on the Salesforce components and you're writing some code writing some logic. So it will take a bit more time as compared to when you are when you are building some logic with the point and click tools. Right. So it will automatically will increase the user productivity in terms of building a solution. It will take lesser time to build some solution or build some functionality. Right. And as we all know, all the sale in Salesforce, we can connect our Salesforce or with some external system. Those things can be done in the only studio components as well. What do I mean mean with connecting with external system we can integrate our Salesforce system and fed some data from some external system. Save some data tools to the external system. All those things which are incorporated in Salesforce integration can be built into the only studio tools as well. So to the next slide. Yeah, so folks who have been who are joining this session for the second time must be must have seen this slide before. And for folks who have joined for the first time, this is this is the architecture that only studio follows. Right. So before talking about this picture, I'm going to tell you what are the main components when you are when you are building some functionality in Salesforce. So first first component will be your digital experience. So what is digital experience? Whatever thing which you are seeing on your web browser, those all comes under the digital experience, or we can say you are experience. Right. And now on the second layer, which is service management service management includes all the custom logic that you are writing all the data that have been that is saved in your database. Now you want to fetch it or whatever information you are getting from the user from UI. Now you want to save it to the database. So all these things comes under the service management. Right. You work with Java you work with any any language these two things will be similar to all of the technologies right this digital experience and service management. You will be you will require a UI experience and you will require a service management so that you can build some logic, save some data, fetch some data from database. Last in the in the only studio is developer experience. So when we are working with Salesforce components, right, we are working in sandboxes. So we are not directly building our logic into the production org, right production environment. Whenever a customer comes, they will buy production purchase like a license from Salesforce, and then from that production or or environment we will be creating multiple sandboxes, according to the requirement right. So, let's say you have created a apex class in your sandbox org or sandbox environment. Now you want to deploy it to the deploy it to the production environment. So, what are the things that we can use for the deployments in sales for Salesforce components like change sets, like workbench, we can deploy with the help of via school, we can deploy with the help of and migration tool. Similarly, only studio also provides some deployment tools by that we can deploy our only studio components like integration procedure data raptors to the another environment or production environment. And those tools can be there are two tools. First is IDX build tool and second is IDX workbench. So by the help of these two tools, we can we can deploy our changes to the another environment. So these are the three major layers that only studio gives us in order to build some functionalities. Right, so I think in today's session we are going to deep dive and in overview session also we discussed about these layers but today actually along with these layers we'll be discussing more about these individual components like what is flex card. What is omniscript, what is IP what is data raptor. So this these individual components you need to know so that you can you can understand for what purpose we actually need to implement these components. Okay, so I think we can proceed further. Yeah. So, first of all, we're going to deep dive deep dive into the digital experience or the UI experience. So, when we are working with Omnis Studio in digital or UI experience, Omnis Studio is giving us to two components or two tools. First is Omnis Studio flex card. And second is Omnis Studio Omniscripts. And what's the main difference between these two components, because these two, these two components or tools are comes under into the digital experience only. There is a difference between them. Whenever you want to show some show some data right, like, let's say you want to show a data account records table. So we can simply use the Omnis Studio flex cards. Right. And whenever you want to create some guided path. So let's say you are onboarding a customer into your Salesforce org. Now you in first step, you want to get the account information. In second step, you want to get all the contacts information. And in the third step, you want to create the opportunity for them. Right. So whenever you want to guide it, but so that a business can complete that, then we're going to use the Omnis script. Right. So this is the main difference between them. Right. And if we want to compare Omnis script. So I think Omnis script is somewhere similar to our screen flow that we implement in flow builder. Right. Right. Yeah. So I think those who are watching this live or if someone is watching the recording. So you might have heard or you might have worked on screen flows that those are available with flow builder. So you can relate Omnis script with that because in screen flow also we create some screens. And on one screen, we do some operation on another screen. We do some another operation and all the screens are connected. So that is a guided flow. Right. So similar flow, similar path you can create with the help of Omnis script in Omnis studio. Right. So this I told you so that you can relate how Omnis script will look like and in upcoming sessions like we will be implementing everything practically so that you can visualize how things are working individually and we'll tell you like how these flex card Omnis script can be connected together so that you will be learning. Yeah. Let's move on to the next slide. I think there is one more point Abhishek last point like LWC. So what is this? Can you just relate it as well? Sure. Sure. So whenever you are creating a flex card or Omnis script, right? So how Salesforce is managing. So basically Omnis studio has given us some tools by using the drag and drop functionality. We can create a UI or the digital experience, right? But Salesforce as a core platform supports only our components or the lightning web components if you are creating some UI. Correct. So Omnis studio has played or build this tool in a such a manner whenever you are creating a flex card or Omnis script at the back end it will be created as a LWC component. Right. So when you are creating the flex card or Omnis script with the drag and drop functionalities you are doing nothing but creating a LWC component. So now you don't need to write the code from the very scratch. You can just use the Omnis studio components which are drag and drop tools and at the back end LWC will get created automatically. So this is how Omnis studio has built their tool. Correct. Yeah. So I think it will help them to understand like LWC is somewhere in the back end. So if you know LWC so it will be good to work with Omnis studio. Yeah. And this will make more sense when we will be doing all the practical implementation. Yeah. Exactly. One more question like if someone doesn't know lightning web components so will they face any challenge? Not at all. So I mean whatever code has been created by Omnis studio at the back end we don't care. We are just working on the UI. So it doesn't matter. Yeah. That's why it is very simple to use because you don't need to think about coding if you are not good with coding still you can work very well with Omnis studio. Yeah. I mean that's the problem that Omnis studio have been resolved for the developers right? Yeah. Who don't want to code then you just come and create some LWC components with the drag and drop tools. So there is one question from winner. This is very good question. He's asking can we check that LWC code which will create by Omnis studio. I think yes. Yeah. Definitely. Yeah. We can check that and we can study that code as well like how it is implemented. Yeah. Okay. So I think we can proceed further. Okay. So now let's see the I mean as we have already discussed but let's check it check it out what flex card is again. So it summarizes the basic information at a glance. So let's say you have a customer support support system and let's say a customer is calling you and your agent who is attending that call wants to get the information very quickly right? So we will ask your name. You will ask your phone number. So for that type of functionality we can use the flex card. So on the UI we will just pass the phone number or name whatever information we require and we can fetch the data from database and show it into the flex card. So this is one of the example which can be given for the flex card. Okay. So you mean to say like there will be a component and it will receive two inputs phone number or name of the customer and on the same UI it will fetch some selected information and that information will be available on the UI. Exactly. So I mean if I summarize it we will be having two let's say text inputs where we will be getting name and phone number and there will be a button. And after click of that button within milliseconds only not seconds milliseconds all the data can be fetched from the backend and show it to the user and not let's say there are a lot of information for that customer right. So what we can do is when we are clicking that button we can just show four to five fields on the UI. Now let's say if customer agent wants to see more information we can create one more button which will show more information on to the same UI. So on the first click they will just see basic information which can be identified but if the customer agent is not satisfied then they can click another button and get some more information. So that's the functionality flex card supports. Great. So I think more idea when we will be demonstrating so it will be here then. So guys in this session we are just having a discussion like what particular tool is what we can do. So be with us because in upcoming session if you have gone through the session tracker so tomorrow we will be having one session on data raptor right. So from tomorrow onwards all the sessions will be based on practical implementation right because only studio is all practical implementation because it is a tool. So in this session only we are talking theoretically but from tomorrow onwards all the sessions will be having 80-90% practical implementations. Okay. So I think we can move on to the next slide. Yeah. So next component that comes under the digital experience is Omniscripts. So Omniscripts gives us the guided path. Let's say if you want to execute a business process step by step then we can use the Omniscripts and as Sanjay mentioned Omniscript can be compared with the Salesforce screen flow. So let's say on the first screen I want to let's say I want to create one account right and I am just I have just got information like what's the name of the account. I mean and let's say there are some conditions right. So let's say for that account forecasting is forecasting is let's say it's $10,000 right for that account. So on the next step we can show some elements or show some data according to the condition. So for example let's say if the forecasting is more than $10,000 then we will allow user to create an opportunity. If it is less than $10,000 then we will not allow the customer to create the opportunity. So these sort of conditional UI also we can create into the Omniscript. Yeah. So I think it is similar to in flow we have decision element. So based on decision element we can decide like which path we need to show to the end user. So I think it will be similar to that. And I think those who knows flow they are feeling excitement like how quickly they will be able to understand the concept because if you know the flow builder functionality you will easily catch Omnis Studio functionality right. So I hope like if you have attended Salesforce bootcamp flow session. So with that knowledge you will be able to understand all the sessions of this bootcamp as well. Okay. So maybe we can jump on to the next layer and which is very much on your hand and backbone. Correct. So before jumping on to the next layer which is service layer I just want to mention one more thing. As we discussed all the flex card and omniscript are created as created as a LWC at the back end right. So one more benefit of creating flex card and omniscript. We can add these omniscript and flex card anywhere into the Salesforce. It can be your record page. It can be your home page. It can be your community page or anywhere. It can be even even it is possible to integrate or embed your omniscript into our custom LWC. So let's say you have created a LWC which is which which you have developed from the scratch right. Now what you want to do is you want to create a omniscript and that omniscript can be embedded into your custom LWC which you have created. And it's vice versa. If you if you if you have created a LWC and if you have created an omniscript that custom LWC can also be embedded can be embedded into your omniscript. So these these sort of flexibility omnisodio tools. Omnisodio has given us. So this is also one of the most important thing. Yeah, I think and this is great and similar thing we can do in flows as well. So those who are familiar with flows. So they can just relate whatever you are explaining. Yeah. Okay. Now let's move on to the next layer. Okay. There are some more explanation of omniscripts like as we discussed. We already covered I think all the things that can skip and we can jump on to the next. Yeah. So next layer in the service management layer. So so one part is completed. You have created the UI right now if you want to show some data which is saved into your database or if you want to save some data into into your database. So let's say you are getting some customer information. Now you want to create a record for the scene. So those sort of for those sort of things. When we talk about Salesforce we use apex and SQLs and DMS in Omnisodio. We use integration procedures and data raptors. So if if we want to compare the SQL queries and DML operations with the Omnisodio components, those can be compared with the Omnisodio data raptors. And if you want to compare your apex class where you where you are building some sort of logic or some sort of conditional statements, those can be compared with the integration procedures. So if you want to set some data, if you want to save some data, you can you can use the data raptors and if you want to build some logic. So for example, let's say in your apex class, you are writing five five SQL queries. So what you will be doing is you will be creating integration procedure and integration procedure from where you will be calling five data raptors. So it can be really it can be related with this this this example. Yeah, in your IP slash apex class, you are writing five SQL queries slash five data raptors. So this can be one of the example. Yeah, and I think the best part of data raptor and IP is like in one apex class if we are writing five SQL. So those SQLs will be utilized in same apex class only, right, we cannot reuse them in another apex class. Right. But in case of data raptor, if you have five data raptors, you can use them in one IP. And along with that, if you want to use all data raptors or any one or two in another IP, I think we can use there as well. Right. Exactly. Yeah, so data raptor and IP, both are independent components and they are reusable components. So this is the advantage of this tool. So whenever you create any data raptor or IP, so both are reusable. Right. So you just need to design or implement it in such a way so that you can reuse as much as you can so that your implementation time should be reduced. Right. And if we compare it, so data raptor is similar to SOQL and DML in simple way and integration procedure is similar to Apex and in flow. Also, we have these things. So in flow, we have data elements like create record update record. We have delete record. Right. So get record. So all these are related to data raptor retrieve update and transform not transform but retrieve update. And load. Right. So and in in flow, we have decision element. We have loop element. So these are somewhere related to like IP. So IP has more features as compared to flow. That's why it is more popular in industry clouds. So this way I think if if you go for an interview, so these kind of questions will be asked, like why Omni studio? Why not flow builder? Why Omni studio? Why not Apex? And it's it's it's related feature. So this way you need to know how you can compare everything with with the help of example and you can justify your answer. Okay. So I think we can move to the next slide now. Correct. So the first component of service management layer is data raptor. Right. So there are four types of data raptor that Omni studio provides. Named that data raptor turbo extract data raptor extract data raptor load and data raptor transform. So so data raptor turbo extract and data raptor data raptor extract would vote the data data raptor are same kind of data raptors. We will call call them DRs. So DR turbo extract. We will be using when we want to fetch some data from only the single object. Right. Single object and it's direct pairing. So why and DR extract we use when we want to fetch the data which is in which is in hierarchy. So let's say we have three objects like A, B and C. Right. If we and C is the grand child and is the grand parent. So if we want to fetch the data of a with the help of C object, then we will be using the data raptor extract. Right. Yeah. So to add here like objects which are having relationships. Right. Correct. Yeah. Right. So we can fetch the data from from the direct parent only. So we can just go to the one level only. But in the data raptor extract we can go to the multiple level or if you want to fetch the data from from the object which are which are not into the relation also that also we can do in the data raptor extract. But why they have created in such a way because data raptor turbo extract will give you the data a bit faster as compared to data raptor extract. And the reason is because when DR DR turbo extract we are just fetching from the data from only single object. And in data raptor extract we are fetching the data from multiple objects. Which can be which can be which can be or which can be a single you know related object or or separate objects as well. Now we will see the data raptor load. So what data raptor load does is yeah so what data raptor load does is so when we talk about the Salesforce conference slide. First is your SQL and second is your DML right. So if you want to insert some data or save some data or update some data into your database then we will be using the data raptor load as the name suggests load some data into the database right. On to the last one data raptor transform right so the the main thing about the only studio tools is they supports multiple type of data formats like Jason XML and etc. So if you want to transform your data right like from XML to Jason Jason to XML or Jason to Jason also. So those sort of things we can do into the data raptor. One more functionality of data raptor transform is if you so let's say if you if you are fetching account records and you are getting 100 or let's say 500 records of accounts. Now you want to trim it trim the data down by the 100 records then then we can take the help of data raptor transform. Okay so due to some reason my video got stuck so apologies for that. So I think you very well explained all the things there is one question what is transforming. So I think it is new concept and it was not available in flow and it is not available in apex as well right. So it is available in almost today. So I think whenever we'll be doing some demonstrations you will be able to understand it more clearly right. So right now like extract you can relate as SOQL and load you can relate as DNL right. Okay so next is IP. Yeah so as we already discussed IP is nothing but it is your apex class which has some similar similar functionalities like calling calling calling or writing SOQL queries. Writing a DML operations writing some logic or business logic or conditioners logic like if else for loop try catch block all these sort of things that you can do in your apex class we can do it do it into the IP. And one more benefit that Sanjay told before like if you have written five SOQL queries in your apex class and if you want to use the same SOQL queries into your another apex class you have to write those SOQL queries again into the another apex class. But in the context of OVNI studio IP let's say you have created five data raptors so those five data raptors can be used into N number of integration procedures. You don't have to create a data raptor for each and every icon. You can use your data raptor at multiple IPs at multiple OVNI scripts. So that is one more advantage of OVNI studio tools. Yeah and I think it is faster as well so that example is on next slide if you go to next slide I think yeah so with this example I think you will be able to understand the power of OVNI studio. So basically if you have any minor tasks for four hours that you are building with apex so with IP you can implement it in one hour. And if you have any major tasks that that will take six weeks so that that actually you can cover in one day maybe or in two days with the help of integration procedure. Right so your efforts will be reduced and in OVNI studio we don't need to write test classes but in apex we need to write test classes as well. Right so that's that's where also you will save lots of time. Yeah. Okay so with this we can move on to the next layer. So the last layer is developer experience layer which is which is nothing but if you want to deploy your OVNI studio components from one environment to the another environment. So OVNI studio has given us two tools first is IDX build tool and IDX workbench. So IDX build tool and IDX workbench what you can do is you can fetch your components in your source org or source environment. And with the help of these tools you can deploy that source code into your target environment. So this is self-explanatory so we I mean this can this can be this is all for this test and experience. Yeah so I think we have one one one slides for each IDX build tool and IDX workbench. So basically build tool is command line automation tool which packages and migrates OVNI studio data packs in a source control friendly format. Right and it preserves dependencies validates the data and verifies the success of migration. So it is basically based on command line and if we talk about IDX workbench so that is basically if you go to the next slide. So it is basically a desktop application that enables developers to migrate data packs and Salesforce metadata from one org to another or from an org to a Git repo. Right yeah and it also includes a test console where users can run test procedures and view Gantt charts of their step by step performance. So these are two tools available for deployment purpose right so we'll be doing demonstrations in upcoming sessions. So I think this is all we prepared for today. So I hope now you you must have deep dive right so in overview session we just talked about the layer now we discussed them in detail. And tomorrow we'll be picking data raptor. So in tomorrow's session you will get to know how you can create data raptors. So from day to onwards all the sessions will be having practical implementation so that you can understand and you can have grip on this tool. So just just share a review or feedback about the bootcamp how you are feeling and what what what are your reviews like you are liking or what what we can improve. I'm sure like from tomorrow onwards when we'll be doing some demonstration so you will like them. And we request you to create your account in the org which is having Omni Studio installed and like if you have the org so whatever demonstrations we will be doing so you can practice them. Along with that we'll try to create a practice exercise sheet also so that day wise whatever we are covering in the session. So we will be having those requirements placed in a document so that going forward whenever in future you want to practice so you can use that document handy. Right. So this is all about today's session. Let me see if we have any question that is not answered. I tried to have all the questions. So there is one question velocity and Omni Studio are same or different. So I think velocity developed this tool and now it is known as Omni Studio. So this we already covered. So you can just watch overview session where Abhishek explained it in detail. Then when I was asking there is a separate org for different insurance also like health and vehicle. Similarly for insurance cloud there is an org and in that insurance cloud you can have insurance for health or vehicle. Right. They are part of that insurance cloud. For health industry we have separate cloud that is known as health cloud. So one question how much ease in troubleshooting steps with regards to Omni Studio. So Abhishek I think it depends on practice totally. Right. Yeah. The more you practice the it will it will get easier to troubleshoot your problem. Yeah. So Manjunath I think this this is answer for your question. So initially whatever demonstrations we will be doing. So just practice those and like if you get a chance to work on a project. So I think you will improve a lot and Rajiv there are two certifications for Omni Studio. One is Omni Studio developer and one is Omni Studio consultant. So Vijay there are lots of jobs for Omni Studio like once you will be having enough knowledge. So read reframe your CV as per that and then try you will get a lot of opportunities for Omni Studio. Right. So if you are not seeing it means you are not searching in proper way. So lots of jobs are there. So how to use real time Omni Studio so that we'll be demonstrating from tomorrow onwards. So Suresh if you know Apex and SOQL that would be good. If you doesn't know we'll try to tell you in such a way so that you can understand. But if you know so you will be quickly like understanding all the concepts that we are going to explain. Yeah. Okay. So I think with this note we can end the session because we don't have much questions now. I think we are we already answered all the questions. So guys tomorrow like tomorrow is Friday but due to some reasons on Wednesday we were not able to have the session. So we just want to have this sequence going forward like two sessions every week. So we'll try to have one more session tomorrow so that you can start implementing something on Omni Studio tool. Right. Okay. So there is one more question. There is no requirement for code. So non-technical person can also. Yeah. Yes. When I'm non-technical person this is low code platform so non-technical folk can work. So Manjunath I think for development you can go through the bootcamp there everything I already explained related to Apex and all. Yes. After this I can plan for CPQ. So it will take some time. Yes. Omni Studio is part of Salesforce developer jobs. But if you have Omni Studio skill set so your chances will be high. Getting a job. So Omni Studio is a developer tool. So that's why you will see a Salesforce developer jobs having a skill set of Omni Studio. Right. And they can come as velocity developer as well. So Salesforce developer or velocity developer. So velocity developer is specific to Omni Studio and Salesforce developer can be LWC or Apex along with Omni Studio. So exclusive jobs for Omni Studio will be called as velocity developer. So with that keyword you need to try and search the jobs. Okay. So thank you Abhishek for sharing the insight and I am sure like from next session onwards people will be getting more knowledge practically. So I am excited. I think you are also excited and I can see the excitement throughout the community because I can see more than 250 folks joined. And right now also we have more than 40 folks live and I'm sure like this bootcamp will break all the view counts because very, very less platforms are having this content. And thank you Abhishek for doing this for the community. And I will like I'm sure we will be doing in different way like I did other bootcamp. So we'll be going on slow pace keeping that in mind like people are beginner for this tool. So we'll explain everything in detail. We'll try to answer each and every question so that this bootcamp will be a unique kind of bootcamp for the community. Okay. Yeah. Yeah. So thank you so much Abhishek. Yeah. Thank you Sunday. Okay. So I think that's a wrap. So see you guys tomorrow in the next session. Bye everyone.