All right, hello. Thank you for joining FTC3 in the wild. I'm Eugene Sorensen, Chief Parked Officer for Cosaic. And it's great to be back here in London after almost a three-year absence. So, and this is? I'm Rogue Friends, Product Director at Symphony. Thank you. So what we want to do, a quick agenda, just run through quick intro on FTC3. If you guys aren't available, then we're going to get a live demo of FTC3 actually in production environment. And then we'll circle up with a couple other use cases and some of the things of the challenges that we encountered in this project. So let's, next slide. There we go. All right, so I thought just for a quick moment we would read through the charter as a product guy. I think it's always good to make sure you know what your vision is. Where are you headed? So the financial desktop connectivity and collaboration consortium is to develop specific protocols and taxonomies to advance the ability of desktop applications in financial workflows to interoperate in a plug and play fashion without prior bilateral agreements, right? And I think that plug and play piece is really key. That's where we need to get to so that it becomes really fast and easy to build the best of breed desktop that all of our clients need. And next slide. All right, so what is FTC3? So core components of it, context data. Those are your nouns, the things that describe it, right? All that metadata that you think about when we think about a position, a person, right? That's what we need to transmit from one app to the other, right? The intents are the actions, your verbs, right? I want to launch a chart. I want to launch a chat. I need to send a message. Those are the intents, right? The application directory, right? We're all out here building apps and multiple apps. So where do I find them? How are they defined? They need to have a standardized method of describing them and finding them so that it's easy to use. And ideally, we're going to have multiple app directories, but we'll come to that point later. All of these things are tied together by an API, the desktop agent API. And if we'll click. So there are several desktop agents out there available today. Of course, at Cosaic, we have FinSomble, which we're quite proud of. Glue42, OpenFin, also commercially available solutions that you can use as your desktop agent to facilitate this interoperability. The FDC3 desktop agent is a plug-in, a browser plug-in. And we just had last quarter released the FDC3 electron, which is an open source version of a desktop agent.  And next slide. So I've broken down who's using FDC3 into four categories. The first was the group on the last page of desktop agents. Then we have the financial service companies who have actively been invested. We highlighted some of these before. Then there's the app teams. These are the firms that are building apps, the best-to-breed apps that you want to plug in to your smart desktop. And this is where FDC3 really allows it to be that plug-and-play experience. And next slide. And then supporting this transition, the agents of change. So if you want to implement an FDC3 project, you want to transform part of the digital transformation, transform your app stack, then adaptive reform as Normans and so on, Scott Logic, have all been active participants. And we thank them all for what they do. We work closely with all of these firms to help our clients implement their desktops and build out their applications to leverage FDC3. Now with that, I'll pass it over to Rob to talk through a use case of why we're all here, to see it. Let's see this thing actually work. Let's see it in action, exactly. All right. Quick share hands. How many people here have been or are a trader? None. How many people? Oh, was that half? No, none. Anyone been a salesperson at a bank? One. All right. So I'm in a relatively safe space here then. That's good. So this example that we're going to go through, this is something we did a symphony event a couple of months back. The workflow is meant to be a buy-side trader. I played the role of the buy-side trader in FX. Very busy person. I make lots of money. I don't have time for any idiots. And I want my desktop to be really smart and fast. That's the basic concept.  You'll probably recognize those traits in how they behave. Time is money. And I want to make lots of money. So what we've got here, so we talked about the desktop agent. So what we've got, we've got four applications and a desktop agent. And they're all going to interact together. And I'll just talk you through the workflow and you can kind of see what you can do with FDT3. So what we've got on the screen up there, we've got a blotter on the top left. So that's where my trades. That would be my firm's blotter. Over here, it's all a bit squished because normally I'm a really important trader. I'd have six screens in front of me. I wouldn't be doing this on one laptop because I'm really big screens. So I've got a blotter here. I've got my chat platform, Symphony. And we'll show you a few other things. So what Pierre here is running things so that I can be hands-free. So what we're going to do, imagine I just traded sterling dollar yesterday. So if I'm a good trader, I'd be looking at how I performed and how well I've done. So we're going to put in GBPUSD up there. Thank you. And I just want to see how some of these trades that I did yesterday performed. So first thing that's going to happen, if you just click on the chart IQ little widget there. So the blotter is my in-house application. Chart IQ is a third-party charting app. And we just clicked on the button. And magically, the chart IQ chart came up. Now, what happened behind the scenes we'll talk about in a second. But essentially, as a user, I love that because I clicked on it. The context got passed over. It loaded the security. It loaded the time frame. It showed me the orders I was interested in. And I didn't really have to do anything apart from clicker buttons. So as a user, love it. So what we're going to do is, if we click through this, there's little pink dots here. They're the executions that I did yesterday. So if we just look through that, Pierre, thank you. So you can see we can click around the chart. What this is telling me is there's some executions happened here.  So if I'm on the buy side, I'd be talking to my sell side about, well, what happened? Why is it that you didn't fill me at the right price where you were slightly off market? So that's one application that's kind of talking FTC3 between these two. The other thing we have up here is a tool called TradeFeeder, which is a transaction cost analysis tool. So it analyzes how trades perform versus the market. So Pierre has just clicked on the TF thing there. Again, it's done the same thing. FTC3 talked across past the context. And wow, that's a lot of stuff.  The red dot is the average performance, and it actually shows that yesterday that algo performed better than it did on average. So it's probably a good day. But because I'm a buy side trader and very high maintenance for my sell side, I want to just make sure what's going on. So one of the things I can do is start to query that with my sell side. So client support on the sales side of the bank. So Pierre, if you want to just share that, so what we're going to do now is we're going to share that chart using symphony to connect to the bank on the other end. So if you imagine there's somewhere, wherever they are, Barclays, Morgan Stanley, Citi, whoever it might be, I can now send. And again, we just did one click from here over to here. And we've initiated a chat and embedded the FTC3 context and a little picture of the chart. And we can say, feels came in quicker than expected or whatever it is that I'm asking about. And I can pass that context. Over to my sales coverage.  And they'd be able to pick up that information that I've passed across in this message. So it's all a bit crushed because we're on a laptop. But you can imagine that this would be on one of my screens. And I can pass that across. And then they can pull that context out. And again, seamlessly move not only on my desktop seamlessly, but also across to another user's desktop. And just to show you the other side of this. So it can also work the other way around. So here I've got a chat where someone's passed me an instrument that they want to know about. Same thing Pierre can do here. He can hover over that view instrument. And you see up the top left. So Symphony and that blaster just interacted past the FTC3 instrument context across. And now it's filtered on my trades for EuroUSD without me having to really do anything. So as an end user, very cool. And a huge amount of potential I think in FTC3 and Symphony working together. Yeah, right. I think the key thing here at all of these apps built with FTC3 APIs under the hood, right? TARDiQ, Kozak's second product. Actually, it's the first product. Finsambol is the second product. All written with those standards. So it makes it very easy to integrate and pass this together. And we're going to go through two pieces that show you a couple of tools that we've got that make it easy to build a smart desktop using FTC3. So the first piece that Pierre is going to bring up is something called the FTC3 workbench. So this is an open source project, as Gav was talking about this morning, that has been contributed. We worked heavily on it. Kozak contributed to the community. And because FTC3 is always about connectivity, you always have to have that communication, right? If you're talking on a telephone, somebody's got to respond. That's what the workbench is designed to do is to provide you that counterpoint application to work with. So the first thing that we're going to do is we're going to join a channel. So we know what line we're going to communicate across. So we join channel one. And it pops up with a little note there. And then we're going to go over to context. And we're going to go ahead and choose an instrument and enter in your, we've got, we've searched for yours. So we're going to search for Sterling again. So GVPUSD will be entered in. And then we're going to broadcast that to the, to the OMS. We'll blot her. There we are. You both have to be on the same channel. And then we broadcast the context. Now also, you note that it shows you the syntax here, right, for the code. There we go. And those little copy buttons allow you to just copy that text you need for FTC3. And put it into your app, right? And then the third piece is an intent. So we're going to go to the Intent tab. And in this case, we'll just launch a chart, View Chart. And we are going to raise intent. And it's going to pop up with Sterling loaded, right? So this is the kind of workflow that you get from FTC3. And it makes it very easy to do so. Now, I'm going to, we're going to go into something we call the Smart Desktop Designer at Cosaic. It's a product that we built that facilitates building out your desktop and makes it a GUI that allows a product manager, project manager, somebody to that effect, not a developer, could be a developer, but doesn't have to be a developer. Really, we're trying to save the developer time so they can focus on the hard problems to actually build out your desktop solution. So you can see the different tabs we have across the side. We're going to go to Manage Apps, right? And we're going to go ahead, so these are the apps that I've already got in my system. And we're going to add one. We're going to add something, a company called Era, who provides, they capture live streaming events and do the transcription of those events, right? And they're capturing more events than anybody else. So we've copied in the URL for that, and they have built their app using the FDC3 standard, right? And so then we've put it in, and we're going to add it. And then we can launch that app, right? And then we can go back to the workbench or somewhere else, the other chart, anything that's on the same channel, it doesn't matter. And we're going to type in Vox in this case, and it searches for that. How long did it take Era to stand up this app inside of Ensemble using the workbench and FDC3, because they had already written for that? And the Smart Desktop Designer? About four hours, right? So this is something, if you use this standard, it is plug and play. That is exactly the objective up front that we are after, right? Is we get more apps, right? We had some 20-some apps have registered. It said, yes, we're using FDC3. And we can get more apps doing this. This is when the rising tide will lift all boats. It will help our entire community. We were just chatting with our friends at Pictay, used the term, fix for the desktop. That's what FDC3 is. All right, so Rob, we? Yeah, I think we were going to talk a little bit. I think Chris wanted us to talk a little bit about some of the challenges we face when we did this. So when you start to use these things in the wild, obviously that's when you realize all the things you didn't think about. One of the things we found, I guess, on the start chat intent was that's great to start a chat, but what if it's not already exist in chat room? Kind of obvious, but it was something we had to add to it. The other thing I think you saw in the demo as we did that, chart share into symphony. We allowed people to put in some text, and we had a little picture and all those things. Again, the original, the first version, didn't really allow that. It was literally start a chat. So a natural thing as you start talking to users is I don't want to just start a chat with Pierre. I want to actually say something to him at the same time and probably share something with him. So all those kinds of things are getting worked out as we start to use this for real in the wild. And obviously that will feed into Chris and the next version of the standards. But the more people that do that, the more we'll find these things and we'll get a more refined standard that's good for everyone. So I think those are probably the key ones that we found during this. I'm sure there's a few you had on your list. Yeah, well, so if you bring back up the workbench for just one second. So one of the things that you see in the workbench is that if you go into the context, so you can define your own. At the bottom it says create context. And you can define your own context and build this thing. And that's what Symphony had to do because it wasn't there in the standard. So it's great that you can do that. But then it lives for this application in this implementation of the desktop. And so this is where we'll go back to the slides and talk about really sort of what are the things that, where do we need to take FDC3? And what is it that we need to build out to do? So let's go to the next slide. Right, so we need to expand. Really, there is a context and intense data working group. And that's the team that's really building out and defining the objects that we need to pass back and forth, the actions that we need to take. It's great to see so many people here at this event today in this room. This is the kind of community that we need to have in that group because we don't know what that list is. And as you can see in the workbench, there's what, a dozen, a dozen or so contacts, a dozen or so intense. We're all doing a lot more than that every day. And so this is what really has to be built out. So if we can get more people participating in that and defining that, raising their hands, saying, these are the actions that I need. These are the things that are part of my system and I need to share. So we need to end to that invoking more actions and a standardized message format. This is the point is we have too few and we need to really build that out as we go. Are many more added in 2.0? Oh, yes, OK. But many more to go. And then we need a standard way to deploy these applications. So that app D, as we call it, that's the key piece. And there should be multiple app Ds where I can see all of these different applications and all of the sub applications or all the different vendors. Each vendor would have an app D with all of their child apps within it. We showed ERA. They have a couple of different apps. Those need to be listed and discovered by the desktop agent without thinking. It just plugs in, looks up, says, oh, I've got these five app Ds. And it pulls in all of those. It allows the user to access any of those apps. And if we go to the next slide. So this first point was exactly why Symphony had to write their own context. Because it's not a transaction. There's no communication back and forth in the 1.2 standard. And so once you've sent it, it's send and forget. That doesn't do so well. When I'm talking on the phone, I expect somebody to reply to say yes. I expect Rob to say hello to me. Not just me to talk at him. That's why I'm talking to you. We need back-end processes start using FDC3. Right now, everything that we're doing is on the desktop, as I said, fixed for the desktop. But if the back-end starts using the FDC3 standards as well, then that will simplify the work on the front-end. It requires less translation, less work for devs to map from the data feeds and the data sources onto the desktop and into the apps. So that's a really, will be an important step forward for the solution. Yeah, I think that's one that we get a lot of when we talk to clients is a lot of conversations about as you get into more complex workflows, the back-end needs to interact with the human beings, not just passing instruments across. They want to do more, and they need more systems to talk to each other. So we're definitely seeing that as people get into the FDC3 kind of world, and they start talking about, right, it's great. I can do this across the desktop. I also want to be able to get information somewhere that maybe isn't the desktop, and I don't want to have to go through all that pain of formatting in APIs and wouldn't be great if everyone spoke the same language, not just the desktop. So yeah, I think that's definitely a trend we're going to see. Yep. Desktop agent bridging, right? So up front, I said that there are five desktop agents. Those are the public ones. There's a couple of firms that are actively building their own private desktop agents. Mazeltov, good to them, right? I don't recommend it. It's a lot of work. We've uncovered a lot of challenges. There's a lot of man years in our effort, not to mention our peers' efforts. But listen, if you want to do that, that's great. But the point is, let's say I am going to have one of those desktop agents, or I'm going to have multiple desktop agents. Why can't I use all five and have those apps communicate on the desktop? That's where we need to get to. So the desktop agents need to be able to talk to each other. So this is a big challenge for FDC3. And we'll need to enrich all of our apps to facilitate this. As I said, it's rising tide lifts all boats. There's a big enough pool out here that we can all play. We don't need to own the space. Of course, we love to own the space. But that's not a reality. And we need to make sure Gabb mentioned this in his opening this morning. We need to build out some conformance tools. So we need to know that when somebody raises their hand and says, yes, I built my app using FDC3, that what did they actually do? We need to know that when the desktop agents say this is an FDC3 desktop agent, we need to validate that it's passing the intents correctly, that it's sending the intents correctly to create an action that's passing the context data correctly. So it needs to pass this information. And the app's the same thing. This is going to require some work. Rob was talking about it this morning as well. So this is a major area to go forward with FDC3 as a community. We're all going to have to participate in this conversation to really drive the standard and get the most out of it. Because that's when it becomes plug and play. And you want to be able to look up that list on the FDC3 website, see all the apps that are there, and go, oh, that one's interesting. Good. Pull it down, get their app D, and plug it in, and it works. That's what it needs to do. So that's the vision. That's where we need to go. And I think that pretty well wraps us up. So we have some time for some questions and answers. Yeah, I think we have to be careful when we say pricing. I guess I'm not talking about equity pricing or liquid products. This is more in the structured products where it's almost like a conversation, but it's a machine to human. Or that's streaming prices. Yeah, not FDC3. I was going to say, it seems that we've got a solution for that. Maybe it's not perfect, but we don't want to get re-invited. Or retrieving content from your trade database, all of that stuff, or your news database. These things could all be done to think about the broad spectrum of types of data. More questions, yes? How we worked together to work this. So I think we probably over a couple of months, I guess we were talking about how this would work. Because it was the first time for Symphony to really integrate into FDC3. I think we've talked about it, but I think we're actually going down that path now. And we've got the integration with FinSomble and Glue42. And we're working with OpenFin as well. So all the big three desktop agents. And as Eugene said, there's not a standard way that you interact with all three, which is one of the things that would be nicer to stand away to do. So it's a conversation there, a conversation there, a conversation there, and then working with the developers to agree on how we actually get Symphony to talk to that agent. The FDC3 context, like we said, there were some changes we needed to make. There were additions, I should say, not changes. But really, it wasn't a huge amount of yannics here from our engineering team. It wasn't a huge amount of work. Was it yannic? It was reasonable? I was going to say it's actually very easy. We take the example of the things we want to move forward on, like being able to share rich text, maybe with some images, maybe with some tables, stuff like that. It's literally been the case of opening an issue on the GitHub repository, talking about it with Chels, discussing it to want to be bi-weekly or monthly meetings. But I've got to write the full request. That's it. It'll be done. It's really easy. And going forward, as Symphony deploys applications, they're going to be leveraging the FDC3 standard. So anybody who uses Symphony is going to be able to plug right into a desktop agent that's built for FDC3. Come back to you. You know, quite frankly, no, we have not had that conversation that I'm aware of. Maybe Chris knows. But it is surprising that they have not picked up and paid attention to this initiative. The old people in the Mickey's Keyboard A. The old people in the Mickey's Keyboard A. Yeah. But not that I'm aware of. We haven't had those conversations. No. No. Two more triggers. Did you have a comment? Yeah. So in Finsomble, you can wrap an app, a native app, and it puts it in an electron container. And it can live inside the Finsomble desktop and move and behave. And then there are solutions. David is here from I Push Pull, where to facilitate the data transfer from one app to another. So Excel can play in this environment. And we work quite closely with David and his team at I Push Pull to facilitate that. So Excel can play. And we have Allison in the back from Google who thinks they have a solution to compete with Excel. And we would love to get that fully operational into the smart desktop. So I don't know if my finance guy would agree yet, but we'll get there. You had a question? Yeah. Just the majority of the traders. Roomba talk. Any ambition to expect to? Any ambition to expand to Bloomberg? Sorry? I'd be chatting. Well, I can't speak for Bloomberg. I used to work there for 12 hours, Eugene. So my boss. Yeah. I don't know what their plans are. I mean, obviously their business model in the past has been the kind of walled garden model, which I think is not kind of the direction of the industry. I would expect that they're going to have to do something to interact with this kind of open API. They're doing some work, but I'm not sure how far they're going to go. I think that's probably a question for them to answer. Bloomberg has a solution called Terminal Connect. We interface with Terminal Connect so that we can have a bidirectional conversation with the Bloomberg application. There's a plug-in. You go into the SDD, and it says add Bloomberg, and you put in your code. Or this is coming out in a version in probably August. And you'll be able to use Bloomberg. IB Connect is what they're dreaming of. I think it's more than a dream. It's more they continue to sort of put their toe in the water and figure out. Happy to chat with you afterwards and introduce you to the right people at Bloomberg to give them a kickstart. Not that Rob and my friends here are going to be excited about that, but maybe would. Yeah, could be, right? So it's in play, I guess, is the right answer. Yeah, it's Bloomberg, right? It's like moving the London Wall. You do it one brick at a time. That's right, that's right. But they are recognizing that they do not own the space. I think really it comes back to, and I think we'll wrap on this point, is that was the era 15, 20, 25 years ago. You had to build everything, right? You had to build all of the apps. And Tom Sakunda, our boss, he would wrap on the product team, right? He wraps on everybody.  We're the second best at everything. The only reason we're so successful is because we have everything, right? And you know what? He was right. But we were competing. Whatever products we were building, there was whole companies competing against that single product, Bloomberg had everything. So you can't be the best at everything, right? What we see with FTC3 and we see in a smart desktop is that opportunity to build a best of breed solution, right? Let the traders, let the analysts, let the risk managers, let the ops people figure out what the best solutions are that they need, right? You guys are all building apps. Let's go sell them, right? And let's allow them to plug and play together and build that solution that pushes back against the industry leaders of Refinitiv and Bloomberg and anyone else who's old in that. Yes. I think that's actually a perfect segue to what's next is FTC3 2.0. So this was the warm-up back for Chris and Rika. And I will let them handle that question. But using the workbench gives you a tool to do that, looking at the standard and migrating your APIs. But if we have anything else? All right, we'll think. Yes? Yeah? Yeah. You're still going to run into all of those procurement and security hurdles to install an app. That's what we run into. We at Cosec, both of our apps are desktop apps. And so they don't talk to a back end. Or they communicate through a back end. But there's no back end that is open to the public. So we tend to go through pretty easily. But any app that does have a back end, you're still going to run into those same sorts of hurdles. It doesn't yet solve that problem. What it does is it simplifies your go-to-market time. Your time to value. Once you've got that app approved and installed on the desktop, and we'll deploy it, right? If Ensemble does, or any of the desktop agents can deploy the solution, it's part of what the technology is. And then it will plug and play. We've got the lady with the red light saying stop. All right. We're out of time. We'll follow up later. Yeah. All right. Thanks, everyone.


Hello everyone, I am Sanjay Gupta and I have Abhishek with me. So we are back with one more session on Omni Studio. So I know like from past few days we were not having any session on Omni Studio. So today we will be covering Flexcard. So Abhishek will explain what Flexcard is and will be implementing a end to end demo around Flexcard so that you can understand. So this way like all the concepts related to Omni Studio will be completed then we will be having two more things like how to deploy components and then end to end project. So this way like next week Omni Studio bootcamp will be like ending so that if you are following all the sessions so you can prepare for certification as well. So with this note like I hand over to Abhishek so that he can introduce himself and then we can proceed for the session. Yeah, thank you Sanjay. So hi everyone, myself Abhishek and I am working as a Salesforce and Velocity developer since five plus years now in Salesforce and Salesforce community and I have done some certifications around Salesforce like Omni Studio, Periwan Admin, Service Cloud and CPQ specialist and I have done several projects around Salesforce as well as Velocity Industries like Industry, CPQ, Health Insurance and Telecommunication. So that's all about it. Okay, thank you Abhishek. So moving forward if you want to become part of a community where lots of professionals are connected and they are learning and sharing job postings as well wherever jobs are available. You can become part of this group so that you will be updated about everything that is happening around Salesforce and if you want to receive timely notification for all the sessions so you can follow Sanjay Gupta Tech School. So on the next slide you will see all the social handles. So you can follow Sanjay Gupta Tech School on YouTube, LinkedIn, Instagram and Telegram and session tracker link is available in the description so you can follow all the sessions related to this bootcamp and other bootcamp from that tracker and please provide the feedback so that like it motivates us to do more things for you. So like recently me and Abhishek were discussing about some different bootcamps, those will be like based on scenario implementation. So we are just preparing for that and probably next week or so I will be sharing more information about that because it will improve your knowledge like after watching this bootcamp and the admin and development bootcamp. Now you will be having all the concepts related to Salesforce but if you want to deep dive and want to learn more with respect to scenarios so that particular scenario based bootcamp will be helping you. Okay, so with this note over to you Abhishek. Sure. So in previous sessions I mean till now we have completed all the OpenStudio components like data actor, integration procedure and OpenScript. So the only last component which is remaining in OpenStudio is Flexcard. So if I give you a recap I mean what components that we have gone through till now and what was the use. So for data reference we were doing all the things which we can do with the help of SQL and DMLs and with the help of integration procedure whatever we can do with the IPEX like writing down some sort of business logic or creating some sort of you know logic around data whatever you are receiving or you want to push it to the database. So whatever you can do into the IPEX class you can do with the help of integration procedure and if you want to create some sort of guided flow like we have flow builder in our Salesforce, core Salesforce and then you can use the OpenScripts so like flows we can take some inputs from user we can push it to database we can fetch some data from database that's all things we can do with the help of OpenScripts and last thing that we can that is that's we're going to go through in today's session is Flexcard. So Flexcard is just for you know showing some information to the user so let's say you want to create a list view right for showing all the account records right. So if you want to do with the Salesforce components then what you will be doing is you will be creating a whether a Aura component or the LWC. We are not preferably using the Aura components we are preferably using the LWCs now. So that kind of thing if you want to create some sort of card let's say in a card you want to show account name underneath that you want to show all the context related to it and on some sort of button click you want to you want to launch a guided flow so basically let's say in the LWC what you are doing in your parent LWC you are receiving all the account information and in that in the child LWC whatever account you want to edit you can create a guided flow for editing that account right so that's sort of same functionality you can do with the help of Flexcards as well like if you want to show a list of account records into your Flexcard and on the click of any sort of button if you want to edit some but some sort of account then what you can do is you can launch an omniscript with the help of Flexcard on that edit button. So let's jump into the you know trial or so to see how Flexcard actually works and at last we will be also seeing some two scenarios in today's session. First is we will be showing the account records in the data table so if someone is having the knowledge around LWC they must be aware of what is data table. So basically if you want to fetch some some sort of records from the database and if you want to show it into a tabular format then there is a there is a predefined LWC element which is called as data table that we can use into the Flexcard and in the second segment we will be fetching one private part of contact and we will be showing it to the showing it into the Flexcard. So for the first scenario we will be using a data adapter and for the second scenario we will be using some sort of other data tool to provide the data to this Flexcard. So let's jump into the org now and go to Flexcard. So first of all we're going to see the first scenario which is fetching the account records and showing it into the data table. So again I mean like what you can do is you can go to the Omnis Studio then in the Omnis Studio you can go to the Omnis Studio Flexcards then you can click on the new button then there we have then there we have two things first is name and second is title. So let's say if I give the name is like account list view okay and this author is this author that we can take it as like let's say SGTS and this author it doesn't matter I mean whatever you can give it into it but I mean it just shows which for which organization you are working for and for which for which organization you or for which client you are creating this Flexcard okay. So you can provide the name that title then theme will be lightning there is one more theme which is Newport which is similar to Omniscript that we have discussed. So previously Velocity or Omnis Studio launched with the theme of Newport only then after that they launched the lightning theme and if you it is this child card this is the same thing as we saw in the into the Omnis Omniscript that if you do not check this one and this Flexcard cannot be called from any other Flexcard this will be a parallel Flexcard right. If you want to make it a child Flexcard then you have to turn this flag on and you can provide the description and if I go next so in the next step they will they will ask you what data source you want to use to provide the data to this Flexcard. So basically if you want to use let's say SQL query, SOSL query, Apex class, Apex rest action, data rector rest IP, streaming API custom SDK. So in the Omniscript we in the Omniscript we were just using the data rectors or IPs right to fetch the data from databases but if you want to fetch the data into the Flexcard and provide it to provide it to it then you can use multiple things like SQL query as well SOSL query as well. So basically you can simply write it down the query that whatever you want to use it and you can show the data into this Flexcard. So for now I'm not sure what data source I'm going to use it so I'm going to go with the none as well so there is an option as well if you're not sure which data source you will be using you can go with the none as well and you can simply click on save okay and if I go back to our PPT so our first example is show account records and data table right. I have already created we have already created one data rector where we are providing a user input which is active whether it is yes or no whether it is yes or no and we are receiving the output of accounts right account active account name first name and all these things. So I'm going to use this data rector extract so as soon as your Flexcard have been created there will be a highlight panel where you will be seeing the author, versions, status, clone from if you have cloned any Flexcard from any other Flexcard then it will be coming there. A style Flexcard lies in the last modified theme and description and at the top you will be seeing buttons like preview, new version, clone, activate and help if you want to go to the developer guide then you can click on help. If you want to preview it then you can click on the preview if you want to create a new version or you want to create a clone of it then you can do it and similar to Omniscript if before using this Flexcard to anywhere you have to activate it and into the bottom part on the left side this is the panel where you will be using all your components slow so like if I go to the build then I have so many things in here like Omniscript if you want to show some chart, data, table, field, icon, menu, state and if I expand the input column then I have all the elements like checkbox, currency, date so if I drag and drop this one then there will be a checkbox element will be created here right so whatever elements you will be using from the build panel all elements will be coming in there okay so this is for your display thing and this is for your input thing so basically if you want to display some data then you can drag and drop some elements from here to there and if you want to take some sort of input from user then you can use these elements so and in the properties panel so basically there is a thing called in Flexcard which is called as state so if I go here again and if I drag and drop one more state right let's name it as like anything right so let's say you are calling this Flexcard from your Omniscript okay and you want to you want to show some sort of data into this Flexcard according to some sort of condition so there is a thing called state in the in the Flexcard so right now there are two state state first is active and second was as just as jts and if you click on this condition then you can add some sort of conditions like if that thing is true then show this state so that sort of thing also you can do it do it into the Flexcard so I mean I hope I'm able to make sense on this subject yes yes yeah right now I'm going to delete this state because we are not having this example in the style panel let's say if you want to set the height minimum height maximum height what background color background size whatever CSS you are known of all CSS you can apply it into the Flexcard so that is the biggest advantage of using Flexcard rather than LWCs because you don't have to write some sort of custom CSS if you want to apply a border type to this state you can directly select it top right bottom left and what what how much pixel let's say 10 pixel if you want the border radius or not what color you want what text color you want so that's sort of all things you can do okay and let's say if you're not able to provide some sort of CSS from the configurations at the bottom you can add your inline CSS as well so here also you can write it down any sort of let's say color anything like that so Flexcard is giving you that capability like if you if you're not able to do it any sort of thing with the configurations then you can just go and write the inline CSS to it okay it is I think related to all custom thing custom container class custom class inline CSS so therefore for design perspective it is right so that is there and in the setup part again I will go to the down as well till the down first so in the data source you will be able to see all the things that you all the options that you were able to see at the time of creation of flexcard so right now what we want is we want to call it data refter right or fetching the data so as soon as you will select the data refter name will appear and if I paste the my data after me it will come here right and if I go to the data refter again it is expecting an input into the user input variable right so in the input map what we can do is in the key like we can pass the user input and in the value let's say I'm going to pass as yes and if you want to test this data data refter from the flexcard only then you can just simply click on this saving patch and if you go to the JSON you will be able to see the data whatever is being written from there right now what so if you have worked with the worked on the data table into the lwc it always expects an area of list area of object so basically if I pass this whole data to the data table then data table won't be able to show show account records to me on the UI because it is having an object first right and then it is sorry it is having list first array first list first then it is having an object and then into the accounts it is having the list of objects correct so basically we want this data rather than so we want to trim it down right so what we're going to do is into the result JSON path first of all we're going to pick the zeroth index right and then what we're going to pick it pick is account account node account node so now if I click on save in fetch then now it is giving me all the list list of objects we will go we will see this again I'm going to remove it and I'm going to click on save in fetch so we have this list first which is on the zeroth index we have the object and in that object first object name is called as accounts so that's what we did on the zeroth index give me the account node and as soon as I do this my data is getting trimmed down right now what we're going to now what we're going to do is I'm going to go to build tab and in the display I'm going to drag and drop the where is that data table okay let me search data table and I'm going to drag and drop over here so I mean whenever we are using the data table into the into the lwc there are two things that we use to provide first is the column names and second is the data the the variable in which your data is stored so in the column name I mean I have added the data after first then I have added a data table so flex card is smart enough to understand or to create the mappings by itself only so we are receiving active name and id field into the into our output result right so the reason I mean because I have added the data after first then I have added the data table that is where flex card was able to recognize what is the mapping what will be the mappings for this data table otherwise if I if I if I'm dragging and dropping the data table first and if I'm doing the data setup part later then I have we have to create this mapping manually so wait one second so what I'm going to do is say it has a key none save and I'm going to go to build drag and drop this data table see there is no mapping created automatically and if I go to the setup again and if I put the data after I say this I'm going to say zero painting counts and if I click save and patch and if I click okay and now if I go to this data table now I have to create the mappings by myself so all the suggestions will be there but I have to create the mappings yeah so it would it would be always good like if we have the data like source first and then the component so it will save lots of time correct and all the configurations that we can pass through the data table into the LWC are configurable into the flex card like is sortable is searchable type like number okay active is text again name is text and id is also text and if it is editable user selectable so all these configurations we can do it and so this is the columns columns type that we have provided and whatever is being received by the setup part of flex card is going to get saved into the records records node automatically into the flex card so now if I go to preview one question Abhishek here so this records is like a predefined name or we can change it yeah it's a predefined name okay so whatever is being received into the flex card from source it's going to get saved into the records type only always node always okay so now if I click on the preview as we can see it is saying generating card LWC if you saw the screener right so similar to omniscript whenever we are activating our whenever we are activating our you know omniscript or flex card in the back end it is creating an creating LWC only so I mean like whomsoever is following the omniscript session they will be able to understand what I'm trying to say here so now what is happening this data rector sorry this flex card is giving us the data right like one two three four five six records but if you see this this data table is getting repeated for six times so one two three four five and six right and why is that because there is a thing called in setup which is repeat options and this thing is checked so basically we are receiving six records output record output records from the data rector and we have this checkbox set repeat records that means it will repeat the data table six times so now if I go to preview right so it is basis on number of records like if we were having 10 records so data table would have displayed 10 times correct yes and if you uncheck that record then only the data rector will be coming only one time and I will also tell you why this flex card have been configured in this way like how I mean the number of records we are getting from the data the data source by by that number that data that flex card is going to get repeated I will tell you the reason as well so as now this is coming with one only right now what we are going to do is I'm going to go to flex card again and I'm going to create one more so let's say contact record so this is our second you know second one so this will be for contact yeah okay the second scenario that we have into our ppt show contact records so now if I go again here and so directly I'm going to go to setup and now what we're going to select as a data source is sql query so I'm going to just simply write down the select id from contact okay and let's say name as well last name I'm going to get the last name and if I do this so if I select the sql queries I have the options as well order by fetch time of green flash delay and all these things and if I click save in patch as you can see I'm having all the contacts id and last name right and if I go to build and I would I just want to this you know show the data and in the label let's say I want to show the last name okay okay we will call it as last name and here we're going to select the last name and now if I go to preview right I will tell you the difference why we have to check that checkbox and uncheck that checkbox repeat options so this time it will be helpful yeah this time because in data table like in one table all the data will be there but here like different records will be in different card form correct so that is why flex card have been configured in such a way where if you are receiving 10 records then flex card will get repeated for 10 times because in data table we are showing all the data into the one so that is why we will disable that checkbox so see now this flex card itself getting repeated for how I mean like whatever number of records we are getting from that sql right and if I go to setup and if I do this part right then it will just show me the one data that's all let's just wait for yeah yeah and it's not even showing any sort of value as well because it's not I mean flex card is not able to identify from which node or from which index I should pick the data right I mean now if I go back to our this one what I'm going to do is I'm going to activate this flex card now this data table okay and when you are activating your flex card in the background it is basically creating a lwc component just give a couple of minute whatsoever is worked upon lwc right there is a meta xml file right where you have to define which on which target you want to use this lwc right record edit record page community page so if you go to publish options right you will be able to see all these things with the configuration so first of all you will see that is exposed then in the targets you will be able to see app page home page record page community page community report so these are the five options that we have when we are creating the lwc right so that also you can configure with the help of flex card so that is also helpful so if I click on save and now if I go to my home page I should be able to use this flex card into my home page okay so this way like I think omniscript also we can use the same way so I mean like omniscript doesn't give you the these options yeah these options that will be always exposed okay the reason is because you if you want to use your flow sales first flow you can use it anywhere right either on to your home page or community page that is why omniscript doesn't give you this option but flex card will always give you that option okay so if we implement omniscript and flex card so I think it is similar to screen flow once it's implemented so in the back end like we'll be using ip or data rector and in on ui like these omniscripts and flex card we can place so that we can see what data we are having and we can receive some inputs as well basis on that in the background we can do the process correct correct so I mean whenever whenever we are doing the real real implementation right so what we usually do is we are receiving some sort of records if if I want to you know do some sort of modifications on the existing existing functionality then first I'll be creating the flex card where I'll be showing the existing records right then on that record I will be showing some sort of edit button or something and on that edit button I will be launching that omniscript which will be working as a user guided okay so flex card is just for showing the data and omniscript like both input out of thing from flex card we generally don't receive input right correct I mean for small smaller things like if you want to get some name and show some data that that sort of user input you can get into the flex card but if you want to do some sort of complex functionality then you have to use the and another thing is you can never create a guided flow with the help of flex card right so flex card is like similar to lightning card just a ui and where we can put some data correct and another another thing I mean which cannot be covered into the sessions because we we have I mean that will be too vast for our omniscript sessions but with the help of with the help of flex card so again I mean if someone have worked upon the LWC there is a part which is called as event handling right application events component events pubs up and all these things right so that sort of things also you can do with the configurations on the flex card you don't have to a single write down a single line of code and you can do event handling of the LWC with the help of flex cards okay this is I think it is taking time yeah yeah I don't know why but maybe we can do a refresh yeah sure meanwhile I can show you that thing where where are those event handling options into the flex card you go here if I go to setup see this one this event is now if you click this is activated so and if I go to setup if you click on this add new here you will be seeing the type pubs up custom event record change you can define the name in the action you can also do what you want to do you want to call an omniscript you can do it you can call you can if you want to call some data on that event that also you can do so that that sort of things also available into the flex cards yeah so like it is same as we do in LWC but here through configuration we will be able to do yeah I mean like if someone someone doesn't have knowledge around the event handling they can actually do some sort of implementation yeah I think those who are like not good in programming still they want to pursue their career in Salesforce so I think with the configuration plus omnis studio they can survive as a developer in industry exactly and yeah I mean they will be able to I mean once they they will be able to complete the you know umni studio stuff then they will be able to understand the coding stuff as well because umni studio is nothing it's just that all the things that Salesforce has created they have created a UI for it that's it right I think now components are available in the custom yeah section so I have drag and drop there and here we can see right yeah I think it is similar to LWC component now correct great so I think whatever 15 sessions we have done so far so if we if anybody watch all the sessions so they will be able to create some sort of POCs so requirements will be same like whatever you are building through flows or LWC so guys try to implement that with the help of omnis studio tools right so in that case you will be able to understand and lots of options are available so in in our sessions I know like we cannot cover all the features those are provided by omnis studio but anyhow whenever you will be implementing those you can explore and maybe like in upcoming boot camps as I already told you we will be having some scenario-based implementation so we are targeting three things LWC integration and omnis studio so we'll see like which will be coming up first so till the time you can watch all the sessions practice and learn the concepts actually because nowadays in job market there are two types of developers needed one is salesforce developer and one is velocity developer so if you already have salesforce development knowledge so it is good for you if you have omnis studio knowledge then like you can say like you have both the you can work on both the types of clouds one is like functional clouds which are sale service marketing commerce and other than that if you have omnis studio knowledge so you can work on industry specific clouds as well right Abhishek? Yes Sanjay I mean like I mean if you want to become a velocity developer I will I would still call it velocity because omnis studio is just a you know a beginner guide to your journey to your velocity so if you still want to become a velocity developer just go with the omnis studio certification and all the tutorials and all the implementation practicals you can do then after that if you pick up any any one industries industry in velocity it can be health communication media energy telecommunication anything and become an expert for that that will give you an n number of opportunities into the salesforce domain right exactly okay so guys with this note like this flex card like brief implementation Abhishek gave you now you can try whatever LWC you have implemented so you can explore those things in omnis omnis script and flex card and at back end you can use IP and data adapters so we will be having two more sessions one one for deployment related things which will be like quick implementation and maybe will be of less duration and then we'll be having one session on end-to-end project implementation so where we'll be having a complete scenario and we'll try to focus on all the components of omnis studio like data adapter IP omnis script and flex card and with that implementation you will be getting knowledge like how to gather all the components you can club and implement a solution in omnis studio yeah okay so thank you Abhishek for this session and I like today's Saturday and still you were able to manage your time so I appreciate that and maybe next week also we'll be doing sessions on weekends or maybe on weekends we'll discuss and accordingly we'll be planning the sessions okay thank you bye everyone