 Hello everyone. So we are back with one more session and we already have covered all the concepts related to Salesforce Omni Studio. So people are waiting like how we can deploy components if we have implemented them with the help of Omni Studio application, right? So this is day 16 and I have Abhishek with me. Welcome Abhishek on the platform once again. So today Abhishek will be demonstrating you like how you can deploy your components from one app to another with the help of Omni Studio development experience layer. Okay, but before starting of the session, Abhishek, can you please introduce yourself to the audience? Sure, Sanjay. So hi everyone. I hope you all are doing well. So myself Abhishek and I'm working as a Salesforce and Velocity developer in Salesforce community since five plus years now. And I met a trailer double star and I have done some certifications on Salesforce like Omni Studio developer, PD-1, CPQ specialist, admin and service cloud. And I have done multiple projects around Salesforce and Velocity both. And specifically on Velocity, I have worked upon industries like health insurance, telecommunication and industry, CPQ. So yeah, that's all about me. Okay, so thank you Abhishek. So with this, let's proceed forward. So if you want to join Salesforce community where lots of freshers and professionals are connected, and you want to ask questions, you want to discuss doubts, or you want to get updated with Salesforce related jobs. So you can just scan this QR code and become part of this telegram group. And next, if you want to follow Sanjay Gupta Tech School for more learning content, so you can follow on YouTube, LinkedIn, Instagram and telegram. Right. So recently we started our paid sessions as well where like limited students are learning, they are practicing things. So if you are interested, you can join those as well. And for that, you need to visit study Salesforce.com. So there you will find all the information. And if you want to write some reviews, so please share those on LinkedIn or YouTube comment section. So wherever you feel. And with this note, I hand over to Abhishek so that he can share insight how we can do deployments in Omni Studio. Over to you Abhishek. Yeah, thank you Sanjay. So on the deployment side, so basically, I'll just give you a recap so far what we have done in Omni Studio. So in Omni Studio, we have completed all the components, components which can be used. Like, first of all, we started with the data raptors, then we switched to integration procedure, then we switched to this script, then we completed the flex cards. So, and all of them can be used combinedly to create or build a solution around any sort of functionality, where if you want to fetch, you know, if you want to do some sort of DML or SOQL queries, then we will be using data raptors. And if you want to write down some sort of logic behind whatever data you are fetching or committing to data, then we can use integration procedures. And let's say if you want to create some sort of guided flow, then we will be using Omni scripts. And let's say if you want to show some sort of data on the UI, the way we are doing into the LWC, then we can create the flex cards. So whenever we are working with Salesforce components, right, whether it's a custom field, whether it's a custom object or a PIX class or LWC component, VF page, anything like that. So whenever we are working in Salesforce domain, we usually what we do is we always build our functionality into the sandbox environment, right? We never build our functionality into the production, production environment. Even from our production, we create two, three sandboxes like sandboxes like state environment, UAT environment, QA environment and DAV environment, right? So let's say for building a functionality, you have created 10 components or let's say 15 components. Now you want to move those components from one environment to another environment. So if you are going into each and every environment and creating those components manually, then it will be a very difficult task or it's a very time taking task, right? So what Salesforce has given us, like tools like VS Code, Workbench, Chainsets, GearSets, all these deployment tools, Salesforce has given us so that we can automate or we can reduce the time when we are deploying our components from one environment to another environment. So similar thing, Velocity also have done or OmniStudio also have done. We have some sort of methodologies by which we can deploy our components from one environment to another environment, okay? So in today's session, what we're going to see, we're going to use two methodologies. One is import-export method, which is already given by Velocity into the Salesforce org only or the environment tool. And there is another tool, which is a desktop application, which is called as IDX Workbench, Velocity IDX Workbench. By that also we can deploy our components from one environment to another environment, okay? Let's just move into the Salesforce environment and see the first methodologies of import and export. And guys, this is the third layer of OmniStudio, which is developer experience. So far in previous 15 sessions, Abhishek gave you all the insights and demonstrations related to two layers, which were having OmniScript, FlexCard, IP and DataReptor, right? So with this session, you will be having enough knowledge if you go through all the 16 sessions, right? Yeah. And Jerry on the cake, we will be doing one more session that will be project session, right? So we will be covering end-to-end project so that you can learn how all these different components work together in a real-time scenario, okay? Correct. Yeah. Go ahead Abhishek. So for the first methodologies, let's say I want to deploy one, I have created one DataReptor into my sandbox environment and I want to deploy this DataReptor to some another environment. So there is a button called, I mean like whenever you will be opening your DataReptor, there is a button called export in it, right? And as soon as you will click on it, it will start exporting your data pack, which is created for your DataReptor. And so I mean like this is the example of DataReptor. For example, let's say if I go to OmniScript, okay? So previously we created, let's say for example this account data OmniScript and there also we have one option called as export. Let it get opened. OmniScripts are always time-taking when we are opening it. Yeah. So we'll do it into the next round. First we'll just deploy the DataReptor. So as soon as I click on this export, it will give me an export data pack screen where I can click next and so it will show how many components you have selected for export. And again, if you click next, then it will say me that you want to download the data pack or not. So I'm just clicking the checkbox and when as soon as I click on done, the data pack will get downloaded. Okay. So as you can see, my data pack has been downloaded, right? Now, if I move into my another environment, right? And if I again go to the DataReptors, correct? There is another button called which is import. Okay. So I think Abhishek, it will be on the like ListView page, right? Export button when we open particular DataReptor. Correct. Right. So I mean, like, yeah, export will be on the particular DataReptor. And if you want to import it, you can go to the ListView, then from there you can export. Sorry, import. So or I think if you select multiple DataReptors on the ListView, right? From there also, there is a button called this, this one export. So you can export from ListView as well. So that option is also there. So okay, now if I want to import the DataReptor, there is a file already, already has been downloaded into your system. And if you go to that file, yeah, this one, okay. And if you click upload, right? Just click next, it will, it will tell you how many components you have selected for deployment. Again, click next, then again, then it will start importing your DataReptor. Okay. And as soon as I click on done, then I can see that DataReptor here. Just, just imagine if you want to, if, if this method, the methodologies is not there for the deployment, let's say you are extract, extracting 10 objects into your DataReptor, you have 50 data mappings into your DataReptor, and it will be a very time-taking task. And on the other hand, with the help of this deployment methodology, you just, you are just downloading your data back and uploading your data back into the another one. So this is, this simple as that. And now if again, if I want to open that Omnescript, we don't have anything in this Omnescript, let me open anything else, nothing in that as well. As you can see in this Omnescript, let me just activate it so that we have one button called as export here. But the only difference when you are exporting the Omnescript, or if when you are exporting the DataReptor, in the Omnescript, let's say if you are using 10 DataReptors, right now, we are just using one DataReptor. So as soon as you will click on export, it will pick up the dependency of your DataReptor as well. So let's say if you want to deploy an Omnescript, and if you want to deploy a whatever components, child components we are using into that Omnescript, that can be LexCard, that can be IP, that can be DataReptor. That also it will pick automatically whatever child components you are using. And when you click next, again, the functionality will be the same as we have for the DataReptor. So DataPack will get downloaded, right? And if I go to the target org, and if I open Omnescript, similar way we can upload the Omnes, that only that single DataPack which has been downloaded, downloaded it. And from that DataPack, your Omnescript and your DataReptor both will get imported. So if I click on upload, click next, it will show me there is one Omnescript and there is one DataReptor. And if I click next, my Omnescript and DataReptor both will get imported. And it will ask me also, you want to activate your Omnescript now or later? So let's say I'll select the later option, then my Omnescript will get imported, but it will, I can activate it later on. Any confusion in that methodology, Sanjay, if you can think of? No, I think it is straightforward, we just need to export first and then import. The thing that we need to remember, like if dependencies are there, so that is also taken care by the Omnescript application. So those who are like willing to practice this, you need to set up two orgs, right? One will be your source org and one will be your target org. And accordingly, you will be able to practice this. So Abhishek already covered DataReptor and Omnescript, right? So is it same for Flexcard and IP as well? The same process? Correct. Same process. Okay. Yeah, I think that it is the easiest one. Like if we want to export and import like few components, then I think it will be beneficial. Exactly. Right. Okay. I think you gonna cover one more way to deploy, right? Yeah. So there is one more methodology which Velocity has provided us, which is called as IDX Workbench. So what you do for this IDX Workbench, first you have to navigate to this URL. And from there, you need to click on this IDX Workbench beta. And according to your system, whether it is Mac, Windows, Linux, you can download the desktop application. So I think Sanjay, you can give the URL into the chat. I already pasted the link guys. So if you want to download this tool, so you can find the link in the chat. Right? So I have already downloaded this desktop IDX Workbench into my system. And this is how it looks like. So as soon as you will download your IDX Workbench into a system, these four columns will be blank. Depository, source, target and project. Okay. So I mean, right now for just demo purpose, I have set up all the things, but I will also tell you how you can do that. But so as soon as you have downloaded it, you have to click on this pencil icon. This will be always there. Okay. And it will open up one dialog box or the model in which first into the repository, let's say you, when you are working on a project, you have a repository created on your Git and you have created a folder onto your local system and you have created a clone of your Git repository. So you can, you can select that folder over here. Okay. So right now I don't have any sort of Git repository. So what I did is I just created one folder onto my desktop called as SGTS and selected that folder. But if you have created any sort of repository on Git and you have cloned it, then you can select that folder over here and into the source org. So right now I have already connected with the source org, but let's say I want to connect with another source org, then I will be clicking on this new environment and this will again open another model or dialog box where you can give it a name, whatever name you want to give, and you can select whether it is a prod org or it is a sandbox. And as soon as you will select it and click on the login using OAuth, then it will redirect to redirect. It will redirect you to the browser and then you can provide your user ID password and I mean the same way we do for the VS code. You can just provide your user ID and password and your org will get authenticated with this IDX workbench. Okay. Similar way for the target org also. I mean right now I have connected with one, but if you want to do it, you can just go give it a name, select whether it is a sandbox or production and authenticate with your IDX workbench. Okay. Now what is this project? Okay. So let's say I am working on a project where we are working on a, where we are working on a five omniscripts, 10 data reactors and let's say 10 integration procedures. Okay. And let's say in the first print we have done some modifications. In the second sprint, we have done again some modification on those components. So what, what I will do as part of deployment, I will create a new project over here. I will give it a name. Let's say my team name is SGTS deployment. Okay. And from here, I will select whatever component I want to deploy. Okay. So as I have told you, let's say I will, I will be deploying one omniscript. So you will be able to find your omniscript component over here. Select this. If you want to, this IDX workbench not only it's, it's supported for velocity components, it is supported for your Salesforce components as well. Let's say if you want to deploy some custom object, you can. If you want to deploy some lightning, lightning web components, that also you can. But right now, I don't want to do it. So I'll just simply click on this fetch data. Maybe we need to select some types. Yeah, I think we have selected one. Let me try again. No, this say, okay, velocity type and Salesforce type both are separate. Yeah, both are separate. I'm not sure. I will select my current project that I created it. I'm sure why. What I'll do, let me just reopen this. Just give me a second. I think now it is okay. I think it was some refresh issue. Correct. I click on cancel again. And let's see. So let's say I want to, I will be creating another project again as GTS. Then from here, I will select omniscript. That's data back. Yeah. So why I am creating a project? Because let's say in my, in my sprint, I will be always working on those five omniscript, those 10 integration procedure, and those 10 data efforts, right? So whenever we are, and my deployment cycle is like every Friday, I do the deployments in my project. So if I, if I'm not creating any project, then I have to always select those 10 omniscript, 10 data efforts, 10 IPs. And if I have created one project, so let's say I'm selecting only this omniscript. And let's say this one as well. Okay. And if I click, as soon as I click on save, there is a project created for me. So whenever I do the next deployment, I have, I don't have to select the components which I want to deploy. Those components will be always saved into this project. Okay. This is the, this is the main use of this, this project creation. So in the repository, you will be having your folder in the source, you will be selecting our target or sorry, source org in the target, your target will be there and in the project, you can define what components you want to deploy. And if you want to reuse your project as well into your next deployment or next, you know, recurring deployments. And if you, if let's say your components are always same in your deployments, then you don't have to create another project each time you do the deployments. Okay. And as soon as you click on save, it will start fetching your components from your source org. One question here like Abhishek, if we want to reuse the project, so can we add and remove components? Yeah, that also we can do. Okay. I mean, whenever you will be clicking on this edit icon and in, okay, I'll show you that as well. Okay. It reminded me gear set like in gear set also like we used to create these packages and then we can just clone and we can add, remove some components from there. So it actually improves the like process of deployment because every time we don't need to select a component from the scratch. Good. So like answer to your question, if you want to add or remove component, you can click on this pencil icon again. And from here, you can again see all the components, right? Okay. Correct. If you want to remove anything and if you want to add anything. Okay. So, so I mean, for me, in this first Omniscript, we had this data vector so that came by automatically and this AB English Omniscript, we didn't have anything. So nothing key. So let's say if you want to deploy only the Omniscript, you can select from over here. I mean, let's say you have from, I mean, by the fetch, you have fetch, let's say 10 components and you want to deploy only five. So you can select separately or if you want to deploy all, you can select this checkbox. Okay. And after selecting all the checkboxes, go to this actions button. And if you want to, let's say what I'm going to do is I'm just going to select this only first OS Omniscript. So as we remember, in this first Omniscript, we are using this data vector. Correct. And if I click on this button, then only Omniscript will get deployed. And if I click on this migrate with dependency, then this Omniscript and this data vector will get deployed even if you haven't selected this data. Okay. So right now I'm going to select all components and I'm going to click on this, let's say migrate only. And if I move to my target or go to Omniscript, so we don't have this AB English Omniscript right now. So as soon as my deployment is done, that Omniscript should be visible over here. So let's just wait for like... So meantime, there is one question from Saida. So question is, in this IDX workbench, LWC component also deployed directly. Will it be the same process or? Yeah, same process. Okay. I mean, whether it is a velocity component or Salesforce component, the process will be the same. Right. Some error is coming. I'm not sure why. Let's see. And I think if it fails, so it will throw an error message as well. I can see it is already doing. Yeah. I mean, I can, I write and there is some errors, but not sure why. Maybe there is some mismatch in package. So everything got failed. The reason is some records were not processed. I think I selected the wrong org. The org which I selected, that was the previous version of Omnis Studio. Okay. So this is another finding. Like if we are migrating any component from source to target, so both should be on same version level, right? Correct. Yes. So just give me two more minutes. I have updated the target and let's try now. I mean, it's comparatively, I mean, this tool is comparatively easy to use, but it's a bit time taking tool. I mean, patching data packs and all those things take some time. Yeah. I think now everything deployed, right? No. I mean, we have to again click on this migrate, then it will get deployed. Okay. Okay. Yeah. Let's just wait for the deployment there. Yeah. I think this is the last step. So anything else other than this we have for this session? No, I think that's all. Okay. So I hope everybody, those who attended this session understood like how we can deploy. And here you can see the Omnis scripts are available. Correct. Yeah. Okay. Yeah. Okay, guys. So I hope you all understood two different methods like how we can deploy a component from one up to another. So we will be having one more session on Omniscript soon, sorry, Omnis Studio soon, maybe next week. So we will be preparing a real time scenario and basis on that scenario. We'll try to implement all the tools, all the like components which Omnis Studio provides us, right? So starting from a data actor IP, Omniscript, Flexcard, and then we'll do some deployment stuff as well, right? So just wait for that session. I think that will be the last session for this bootcamp. And we'll try to wrap it by next week. Okay. And then as we already promised, like we are already working on few more things. So soon I will be sharing those details with you. So maybe in November or December, we'll be starting some use case oriented bootcamps where we both will be coming and we'll be guiding you some real time scenarios. Maybe it is related to Omnis Studio or LWC or integration, right? So till now, beginner and intermediate resources we have targeted. Now our target is to reach out to the experienced folks who have like four to six years of experience, right? Because somewhere like in companies when we work on the project, so we just focus on few things. So our aim is to reach everybody so that you can upgrade your learnings. And as I already told you, like soon I will be starting AI related bootcamp as well, because Salesforce is like moving to AI and they already launched their AI associate certification. So that bootcamp is also planned. So I know like I'm just keeping on rescheduling the date, but we are just preparing the quality content. So be with us and soon it will be in front of you. Okay. And other than that, I have planned for Kappado as well. So lots of things will be coming up in your way soon. Okay. So thank you Abhishek for sparing time on this weekend. I know it is a bit challenging. So I appreciate your efforts. And thank you for always be alongside with me. Okay. So yeah. So really excited to work on a few new bootcamps with you so that we can share our knowledge with the audience. Yeah. Sure. Okay. Thank you so much guys. See you soon. Bye everyone.