Streamline sales operations automation in IT architecture documentation with airSlate SignNow

How to create outlook signature

e [Music] [Music] [Music] hello everyone and welcome to another Salesforce Ben LinkedIn live so my name is Zaya Dar and I'm the events content producer at Salesforce Ben and I'm really excited to be your host for today's event uh business process automation with Salesforce flow so while we wait for everyone to join um let us know where you're logging in from today we always love to see what a global audience we have attending so let's kick things off by addressing a common challenge faced by many organizations uh low adoption of IT projects so despite meticulous planning and Flawless execution by project teams adoption rates often fall short of expectations so the answer lies in the need for more business process Automation and there's a solution to this challenge it's in Salesforce flow so business process automation using Salesforce flow can can streamline workflows um reduce manual effort and pave the way for excellent user adoption so um I'm thrilled to introduce to youen who is here with us today to share his expertise and insights uh on how to leverage sales force flows for Effective business process automation um Ser would you like to introduce yourself yeah sure J I uh thank you uh thank you for having me on this live session uh again good morning and good afternoon everyone so this is my name is shasa I have over like 20 plus years of it experience of which 16 years is mostly in sales for sales cloud service cloud and other you know CRM related applications right in addition I'm author of like two books I I'm I wrote two books one is the business process analyst the other one is the business process automation using flows so that is the one we're going to discuss today thank you yeah yeah so just before we get started um just a few House Rules this is a webinar um all lines will be muted but don't worry we'll be having a Q&A at the end for you to ask um s any burning questions you may have so feel free to submit the questions and the comments uh throughout the webinar uh the webinar will also be recorded and will be available on our Salesforce B LinkedIn and YouTube channel just in case you need to drop off or would like to share it with your colleagues great well I'll hand it over to you s to take us through the presentation and I'll see you at the end for the Q&A yep sure thank you zna again uh good morning and good afternoon and thank you all for joining the call today so today I'm going to discuss the importance of the business process automation so more than the flows I want to emphasize why business process you know having a business process important then what things we need to automate and again we look at an example where you know we see that the flows how we build a flow on that one okay so I'm going to go through the slid make it a full screen okay the first and foremost important thing is Right anything whether you automate or you don't automate when you get a requirement from your business right you need to understand it right you may have a use case you may have a BD document but still if you have a visual form of it it will help everybody understand the flow right how how the requirement from end to end right initially you know we need to some kind of conceptual flow where you can take a pen and a paper or you can whiteboard it basically right from that during each stage of the project during solution design right during each phase right even during elicitation during solution design you refine that and create you know understand the current and future states of the business processes right here again these business processes should be like system agnostic right then we going to decide on right based on the flows we're going to decide on okay what steps make sense to automate this you're going to do with your stakeholders via workshops or conference room pilots and then for each one of them the whole the stakeholder team should agree the rational behind that when you do a automation right yes you can do pretty much anything automation but is it really adding business value right if you think if the team thinks that it doesn't add much value or it only benefits small of people you need to think through right is it really worth doing that or it's better to add some other functionality right rather than automate and then again you need to prioritize right when you have a project when you have a big road map you're doing some implementation you may have multiple releases right so the priority always is to enable the functionality for the users then the automation comes next right but again automation is important I'm not saying the downplaying that but functionality is more important right the right functionality then the right way automating the right time right will help in adoption again we do it in a phase manner to add real value and then again this business process flow whatever requirements you have in conjunction with the requirement the process flows need to be agreed the steps need to be you know prioritized and agreed upon by all the stakeholders okay so this is the first part the next one is you know what are the tools we have automation it's not just flows only you have other features too we'll get to that in a little bit but you know here since the topic is related to flows right so here flows it's a declara tool it's a fantastic tool again they say no code but I would say you know sales admins can do that but admin role is getting you know like much broader now right you cannot just do admin stuff you need to know little bit of coding you know you need to little little bit of testing right if you have all this it'll help us a lot so what I recommend is right if you know a little bit of coding epex coding that'll really help you understand the flows and then the second one is order of execution right probably most of you know this one if you're a developer of course you know that right because you do the Apex coding the classes methods and all you need to know this one but again for flows this is even more important now right when it's executed what's the order right you may have like Salesforce had a way how things are executed right like how the lead routing rules or the case escalations you know before save after save triggers and all so understanding order of execution for flows will be really important again flow types we have five you know all of you know probably because right now this is the only way to you know workflow automate in Salesforce right high level screen flows you got trigger schedule platform Ed aut launch with flows another great feature is right in the past we don't have this workflows you can do the aex sharing you can use Apex sharing in the past only the developers are able to use that using Apex coding but now you can share records via flows with clicks right declaratively basically you can add sharing you can remove sharing V flows to this is another great feature and again it's easy to use feature right it got a debug window where you know you can optimize and troubleshoot the flows you can run test repeatedly you can debug it repeatedly right you don't need to go to debug logs and do that or go to Apex debugger through Visual Studio and do all that this debugger window is Right available on the screen right on the flow Builder and you'll be able to you know use it very easily right another great feature is right you can identify fals sometimes you know your users get some weird messages some 404 504 510 nobody understands even the business analyst you know we cannot understand right but with flows when you do the fine-tuning troubleshooting optimizing you capture the errors and you can convert them into a friendly user friendly error messages right so this is the second part these are the tools and finally the orchestration I don't know how many of you had seen probably most of you already went through this one again this is a wonderful tool tool right again orchestration is nothing but it uses flow only right in top of the flows where you can package this right it basically amplies the impact of the flows you can have a you know end to endend complex business process building into this form again when I show a a when I describe a scenario I'm going to show through you know flow orchestration only right within flow orchestration right again it uses flows right each flow there stages steps and flows basically you can modularize a big module into orchestration where you know you you you run it by stage there is aition element right you at any point only one stage can run and within one stage you have multiple steps right it can be interactive or it can be you know backend steps and then you know each step is associated individual flow okay in addition to that there goto elements work guide right work guide is in nothing but you know where you know you can you know see that you know if some task is assigned to somebody right they can see the work guide on their screen the system sends an email a link and when they click on the link it opens up the page and of course you know the admin need to configure that they need to add it through the lightning web component onto the page okay and then orchestration run and orchestration work items you can monitor the orchestration say some Orchestra is there right you have interactive session and some you know like backend sessions are there say approval process there a multi approval process is there if it is waiting on approval by somebody and you know it's there for a long time you can go to the orchestration run through the app launcher and you'll be able to monitor it and where it is and all and you can also debug it from there right see you know if something happened you can you can verify that and work items also same thing you can access through app launcher if a work item is assigned to a specific person for approval or doing something on the work item and this person is not available on leave something happened right you can reassign it to somebody okay so these are the features we have so with that what I want to do is I want to explain you a a a scenario this is a real world scenario I simplified it a lot but uh what I want to do is I want to just explain you the use case right this is the use case b item whatever you call it a high level again I simplified it heavily and then you know show you how I created a process flow and then how we transformed that into a future State process flow and then you know how we implemented that using flow AR registration okay so this scenario partner registration I don't know like how many of you you know about the partner registration partners are nothing but they are the you know if I'm a company say for example you know let's take an example apple apple sends multiple products right they have laptops they have computers iPads you know they sell keyboards iPhones everything right so they can send directly to corporations they can do it to individuals too but in this case we're taking B2B right business to business so Apple Sals to corporations directly they have it and in addition to that right Apple will sell their products some of the products through different vendors too say for example Wireless vendors like whereon AT&T or you know T-Mobile they sell Apple iPhones right airpods so they are the partners for Apple they sell their product of course in collaboration with you know the the Apple team the account team but again there it's indirect selling same thing Apple computers and other you know peripheral computer related equipment maybe Best Buy or you know some other company may be selling that to some retailer will be selling that to right so these are the partners so when this partner say in this case if Verizon wants to right Verizon may already be there there may be existing partner say we have a new company coming up they're wireless provider they want to sell Apple products and then now they they request registration right that's what we are talking here the use case is a company request you know registration to the company to sell their product right to do that to collaboratively sell it you need to you know give them access to your system right you need to you know have uh access to the accounts you need to create a user ID for them and then you need to give them access to your leads opportunities again if they premium partner if they're big Partners proberbly the MDF deal registration these are all you know partner specific you know High LEL application the next level right so for that one they need to request a registration so the partner ask for registration that the goal is the functionality here is you know we need to create account for the partner add the contact and convert the contact into a partner user right so that they get access to your system and they collaboratively work with your team the internal account team and the with the partner team to sell the products okay so this is a conceptual flow before going anywhere right you know in some cases if it's a simple request right this is a little bit complex one probably you don't even need to draw you may directly do it in the system right but take for an example there is a little bit you know complicated requirement that you have it's always better to just put it on a paper right this diagram right the requirement need to be understood not by just the business stakeholder the person who is asking and just you who is doing right it need to be understood by everybody the testing team Your solution Architects right even the training team members even the end users right so if you draw a conceptual flow right you don't need to be fancy you can use there are multiple tools I sometimes use pen and paper you can just go to the Whiteboard and draw it there during the workshops or conference room Pilots right so the basic requirement is if you see here the partner request registration and the channel team receives the registration request right this is here so I put in each of the requests right the channel team reviews that and the sales operations creates accountant contact record and then sales operations since they cannot create a user record they request you know the IM team to create that one and then finally the the partner is activated notified so you capture that as steps in here right so I use Vis and capture that you know whatever way you want again this is a conceptual flow so that you get a right understanding right from the stakeholder whoever is requesting that and the smes right at this point you don't need to have a big team to understand everything because the first this this may be the first or second cut you're are doing once you understand you the requirement in conjunction with the requirement you understand that you can take some notes right how do they want to do that right do they want to do it manually or do they want to automate it what's their priority right again review there is some review step who is going to review do you really want to review it can can be manual too I'm not saying you need need to automate everything but at least you know capturing certain things will help you during the next phase of Designing right and again while we are discussing one of the users told me that oh the adoption is really bad because we are doing everything manually and too many touch points are there and you know a lot of things are lost in communication and I I took as a notes here saying that the ad options really PO is only 20 to 55% so this is one of the priorities I want to improve the adoption so then it makes a very good use case for automating stuff right again when do you do don't worry about that what system you use don't worry about that right just capture it from end to end so that you understand first of all then all your team members agree to this one team means all the stakeholders on the project once we have that right you have again right as as like any other projects you have planning phase you have a lot of sessions you talk to the business sometime they tradeoffs right and then finally eventually after maybe like couple of iterations right you come to this you know I would say more or less a final stage this is the future state that we're looking at so we took that all seven items from the conceptual flow I I named as 1 2 3 four 5 six seven so these are the steps we want to do this is the things we want to pretty much automate right I put in more like you know more than functional thing what we are automate but again do you really want to automate all the one through seven in one go right it again depends on the resources right again it's always the important thing is the functionality is important then comes automation okay so you can decide right based on you know once you have it I have the players here to what the partner user does they're going to submit the web form right with all the details with the account their company details the account what products they're interested in and all once they submit it it basically is going to send a notification with a ID so that in future if they want to refer back to the registration they can always refer back and the web form got a lot of information there company information their contact information the product information and all right once we have that you know somebody's going to review this one let me Zoom it a little bit I cannot zoom it okay so then they're going to verify and then it the channel team right request the sales op operations right again here we didn't capture that there is a step approval step it's not a direct approval but they collaborate with the account manager make sure that the account manager is okay doing indirect sales too right then it goes to the sales operations and they're going to make sure that the partner account is properly created a contact is created they send it to a different team the IM am team identity access management team they're going to Prov the users and send a communication right if there is any issue then again you know email goes back it goes to the channel team right so we have the personas here too right so this is called a swimlane diagram again I I usually use Visos so we have the conceptual flow from conceptual to this one yes of course it takes a couple of iterations but once you have this one right if tomorrow a new business team member comes or a new end user comes if you share with this with them they can clearly understand the partner registration process how it flows through who does what and what are the steps right so once we have this one right everybody agreed of course everyone need to agree that and and another good thing with this one is right if if a step right when you walk this through all the stakeholders right including your testing team members your your training team members so that way it'll help when they train right if if if somebody feels that certain fields are redundant are useless not needed this is the time right you can remove those things or some people can say they have some pain points right you can take care of them right you can you know Focus your resources on that and sometimes you may find some opportunities to to improve this one so you can find gaps you can find Opportunities again it's a good document that you know visually people can you know digest it okay so once we have agree document right then basically right of course you know you need to create you know I I I implemented this as part of record orchestration right as I told you orchestration again uses steps right the first step is basically when account is created so what happens is the partner user through company portal or disal experience disal Cloud they're going to submit the form and then it it creates an account and creates a custom objects where it places all their data their account company data account data I mean contact data right the products they're interested and why they're interested whatever format you have they capture that so this one goes to step one right it says that capture partner info so the channel team can open this one and basically review this and make sure that okay everything ties through that everything is fine right they agree to that and they're going to fill in certain attributes if needed on the account object right and then they you know it is not here but again there is another process another functionality going on where they need to do you know due diligence right they need to do the kyc that to do the legal need to approve compliance regulatory if other things are they they take care they talk to the account owner and get the approval and and add certain attributes right based on certain attributes here this de element even though it says account on approval it's not really approval right I named it this way it's basically based on the attributes on the account object or any other object behind the scenes it's going to determine whether this person can progress to the next level or we should cancel it if you cancel it of course I ended it but you send a notification saying that by you cancel to to the customer the pro partner right but in here the reason why we have this is right say for example apple is there we have another small company they want to do business with apple they are a virus provider they want to sell Apple products yeah they can submit all that everything is fine the channel team can put add some attributes based on the attributes the account owner the account owner you know the manage the Rel no matter whether they sell Apple Sals or it's sold through you know T-Mobile or Verizon or any company Best Buy that person manages the relationship if something happens right he's he's going to lose the sales the company is going to lose the sales so this person need to agree right yeah this person is okay you know partnering through Verizon Best Buy and others but I have a small company I want to sell the products this person may say Okay certain based on the attributes I captured here I do not want to do business with this person so they can can it right and if this person agrees based on the attributes agreed it goes to the next level right so the next level is creating a partner account and contact so so what they're going to do is again this is automatically created they don't need to earlier they used do manually but now through flows we are creating a a partner account so you create account the account is created you convert into a partner account then they create a contact it's automatically created because you have the data from the web form and that contact is convered to partner contact right partner management bees a little bit different way right you need to have a contact to create a partner user right and again there's an interaction step the reason why we have interaction step is right what kind of you know entitlements are you going to give this partner right if this partner is a premium partner then do you want to give him MDF marketing development funds do you want to give deal registration capability right all those things they're going to talk with the channel manager at this time the channel manager is the is the link with the partner you know manager they talk to them they manage the partner relationship okay and then once it's agreed okay marketing Development Fund means basically you're giving some funds to do common marketing efforts and all right so they're going to put all these things in this interactive step and then it goes to creating partner user it goes to the IM IM team right in case if it's a small company maybe the admin can create right in big companies you need the due to segregation of Duties it goes to the the another team where they're going to create it and again they're going to notify the account owner and notify the partner user right again I I highly simplified it but again if you use single sign on right if if you give some accreditation you link it to your LMS because this Partners need to be trained again if they're case management right if you know their complaints on cases the partner also should know right the product complaints and all again that's that's again we have like multiple you know functionalities enabled but this is a simple functionality that I want to just cover in here okay so we we we took the you know conceptual flow we have a bu requirement or a use case we convert it into conceptual flow it's a simple diagram you can wrw it with pen and paper and then from there we created in couple of iterations the future stated flow right what is future today right will become a current state tomorrow for the next release right it's a living document you keep updating it right and then we created we automated it based on you know like using uh process orchestration um Salesforce orchestration right again and what I want to you know just you know emphasize here is right one you know you should start drawing process flows right even if you have you know anything like a little bit complex too right get get used to that put it on a pen and a paper just just draw that that way you understand and rest of the team understands in even in future if you had to refer back and then you need to explain you have a document a visual document right again these business process flows need to be kept current right and you need to be you know make updates each release if you are touching anything related to that functionality you need to update it keep it current relevant and effective okay flows probably everybody's using that that's the only way you do the workflow automation right so yeah learning epic coding will help you a lot because a lot of the concepts once you get deeper into the close understanding how things work behind the scenes will really add lot of value will add a lot of clarity to you okay again automation don't always flow sad right just because a tool is there don't start just using it sometimes you know you can do in a simpler ways to right yeah through page layout lightning web components right and then you have you know even record types you can write validation rules and then you can do via you know other you know uh third party apps to so think through based on the complexity and if you can do it a better way just do it right and again right don't automate something if only if it benefits only one or two people right if it if it really need to add value okay and then flows and flow orchestration are getting started I think this is the only way in Salesforce you can do the workflow automations right so it it it's a very powerful tool again you know it's it's changing so rapidly right what I say today may be irrelevant tomorrow so this is like our process flows right we need to keep relevant right if you follow the you know sales for really cycle and you know you have lot of lot of resources on flows lot of great people like fantastic you know trainings are there even trial head trial head is absolutely phenomenal right you have like so much in there you can you can learn a lot right so again flows are the future and I'm pretty sure all of you are going to use it and if you are admin just just focus on you know learning some level of coding also that'll help you a lot and again for everyone right process flows you have a requirement you need to have a process flow right I'm not talking about Salesforce flow flow right even with you know just draw it with the pen and paper that that that will really save you a lot at the end okay with that you know uh this session concludes and uh thank you all for joining this call I hope you got something out of this one and I'll let J you know just facilitate the Q&A session and uh we can you know great well thank you so much for that really um interesting presentation Ser hopefully everyone attending now feels much better equipped to sort of um harness the power of sales force flows for their own business processes so um without further Ado it's now time for our Q&A so if you have any questions for sereni please feel free to submit them in the comments below and we'll try to get round to as many as possible okay so let's see let's just remove that okay how devops friendly are flows and Flow orchestrations uh this is a good question honestly I I don't have an answer right I I don't know to say something and uh probably what I'll do is let me do some research or talk to my friends and I'm going to post that answer on this you know the YouTube you know I'll post a response later in one or two days yeah thank you um okay so I hear people say flow is the future for Salesforce automation we need only flows to automate or do we have other ways to automate business processes yeah not exactly though I mean flows yes that's the only what you know you have it that's the latest one you have it but again it's not always flows though if you have certain complex automations that need to be performed sometimes you need to take the help of a technical team the developer maybe the Apex triggers may be better way right certain things you can automate using lightning web components too right some automations like M you know dependent pick list kind of thing you can do why that one too right there are other ways to right before you jump into the flows think through right and find one or two ways and find the best way to do that but majority maybe you know flows but you have other ways also to accomplish this one okay great um so what tools did you use to document business processes what's your recommendation uh the tools usually what I use is I use visual most of the time again you have lucid chart you have like lot of others tools even you can use a pen and a paper to to do this right so it's not what tool you use but you know that whether you do it or not so just just start doing it I use video sometimes you know I used to use Lucid charts but again you know it depends on a company right whatever you know they pick they may have a standard so just go with that one okay nice um so how does one make sure that the implemented solution aligns with business requirements what state steps did you take to ensure this uh that one uh what you need to do is Right anytime you have a requirement right the basically it follows a process right it's a business analysis I'm not saying a business analyst will do just business analysis it's done by you know the admin anybody who's implementing something for the business need to do that analysis right so if you have a project you need to make sure again as I told right you need to have a concept you need to understand the requirement right once you illustrate the requirement right probably after multiple meetings you are able to understand it from the business user but there's no guarantee that others will understand the same way you understood it right so you translate that into visual diagram right once you have a visual diagram right again to enable this pH from conceptual flow requirement conceptual Flow To You know the the future sa flow right you need to you know meet with the right stakeholders via the workshops or you know conference room pilots and you know together in those meetings right of course you have lot of debates agreements disagreements and all these things right you need to go through that and at the end of the day everybody need to agree to the process that yes this is the requirement I gave and this is the process I want to be followed right if you can do that yeah certainly you know that that's going to you know you know reduce a lot of pain at the end okay Fab um would you migrate old workflows to flows uh I yeah you we have to right I don't think you can uh going forward you can create workflows now again as it is within Salesforce they give a migrate you know you can Mig migr it one what it does is each workflow it creates a flow but that's not the right approach though if you don't have resources maybe you can do that right the reason being is right say for example you have 10 workflows on opportunity record right now if you convert automatically what Salesforce provided it may create 10 flows for you and that's not the right way then the order of execution will be off and you know and unintended you know scenarios may happen on the back end right so what you need to do is you need to analyze create one single flow right or you can create if you have like 50 you know workflows on opportunity object you create multiple you can have a flow subflow right you can call a flow from a flow to right if you can consolidate the whole thing right and fine tune it that way you can right reduce it and have one single flow or one or two flows H that that will help you but again if you don't have time if you had to do that yeah certainly you can do but at some point yeah you had to consolidate that for them to behave the right way okay very nice um so could you briefly explain when to use flow orchestrator yep sure so flows right if you have any small thing right a business user asks you okay when when somebody you know creates when an account is converted from you know stage a to Stage B like say you you started with a regular account a prospect to customer it changed right then you need to send a notification to the kyc team to do the you know kyc stuff that kind of thing Small Things yeah you can use flows even little bit complex things too right when something is created you want to create some related objects or you want to have a roll of summary you can use flows right independently they can be debugged it's fine but if you have a complex logic kind of thing where say for example a person does something then it goes to a manager for approval then it goes to another person to add certain things in there right so now here you can create interactive steps some backend steps right sending emails updating Fields you can do via inter backend flows but some interactive steps creates a work item notifies the person to do something on their screen and the work item will be placed on the screen right the admin will place that on the page layout wherever they want so the person who assigned the task can complete it then it goes to the next person so basically you can streamline the whole process a complex process you can streamline and you can monitor that so when when you have a complex functionality to implement which which touch just many people then you go with the orchestration if not yeah just go with the flows okay go with the flow um so how do you find balance between business requirements and Technical feasibility uh moreover how how do you approach this balance while keeping end users needs in Focus uh yeah that's a good question this is a very difficult thing to do though in any project right so the business ask for certain things right again right what I do is I have a conceptual flow and before I come to the final flow it's not that I'm going to as a business analyst admin talk to the users right I'm going to pull in the uh solution architect right and I'm going to pull in the technical architect we have have the SMS in there right technical lead even the testing lead is there right so when we assess yeah conceptual flow it doesn't tell you anything about technology but when you come to the end stage when we say that okay these are the things we want to automate this is the functionality we going to add we have the solution architect technical architect and the technical lead too including the business analyst that's where we debate we keep fight we do tradeoffs and all and they say that no no this piece looks simple but it's really really complex to implement right do you really want it if you want this one then you need to trade off this this this right now this is the priority then you you going to bucket it you're going to put that okay this it takes this much effort right and if something is a priority you know maybe they need to prioritize that or if they want this one they need to let go that ABC right so it's again a balance it's not an easy one and again that's where the workshops are the conference room Pilots with the right stakeholders come into to play and again you have this visual flows you have the right team members right you have the prioritize list then that that's where you know we are going to see that sometimes certain things may not be technically feasible at all then you know yes you cannot do it in Salesforce but it doesn't mean you cannot use it using third party tools right then you go explore it find out from the third party talk to your architect and see there's any other tool that can be done right again it's a it's a balance resource are limited business wants a lot right again there that's where we need to strike a balance that's where you have the project managers and again the business analysts right and we take the support of the solution architect and The Architects and you know just strike a balance to deliver you know maximum benefit to the business yeah okay okay fantastic um can there be multiple flows with dependency with each other yes yes you can do that uh I mean you you can write I think within flows you can sequence them though if you go to the flow Builder I think from there I don't exactly remember but yeah you can create flows later on if you sequence them you say that fire this than this than this you can sequence it it's available there yeah okay nice um so can organizations identify which business processes are suitable candidates for automation using Salesforce flows um Which business process flows are yeah again it as I told you right as we discussed before right what what is you know valid in Salesforce again you need to look through though because again you don't want automated things sometimes some things may be really really complex right the business needs it but it is done only by one or two team members in the team right something like you know some incentive payment need to be done for you know sales people and it's done by two three people in the back end but the way they do it is very very complex it's it's not easy to grasp and then they want to automate that kind of thing right again it's the example I'm saying right if it's done by very few people let them do it man you don't need to automate 100% you can give them some tools to little bit ease their job but if it's done to three people it's better to do it manually rather than automating it so that kind of business processes where it it doesn't you know impact more people doesn't really add value to multiple people then maybe you know you you need to put it on the back burner yeah okay um can you share any real world examples of successful implementations of business process automation using Salesforce flows uh I think you know lot of organizations I talked to a lot of people on LinkedIn to there's a lot of discussion going on I mean we don't have an option though right because workflows are you know they removed it no more you cannot use workflows anymore anything you do you had to use flows only right and flows I mean Salesforce oh my God they ramped up so much so much even the recent spring release I see they added a lot of new stuff in there right so I think that's the only automation tool we have so you know we had to use it I think if you're using Salesforce okay um is there a reason to use Flow orchestration versus sequencing multiple flows yep it's a good question very good right sequencing is right say for example you have an opportunity object you have created say flows in the last two years some 4050 flows are created multiple projects are going on different teams created it and everybody's busy nobody you know really look to optimize it but now you have time you want to optimize it you sit with the team and sequence it right you give an order one to 10 right which one need to fire before after and all these things it's good right orchestration is not like that it's not just sequencing what orchestration does is right see I'm there if J is there she is submitting something and she wants approval I she wants me to do something on that right and then she creates a work item for for me the system notifies me I go into the system I go to the specific page layout through the link I can go I don't need to really navigate and then I can add my you know whatever I need to do I'll do that then you need to go to another team say it need to go to a backend team where they need to approve invoice then it goes to that team they can do that stuff so basically what we are doing is multi people doing a task multiple tasks we are packaging it and managing it right you can manage it end to end process that's where it use it's not sequencing it's more like managing the whole process business process okay okay nice um so what are some key factors organizations should consider when designing and optimizing their Salesforce flow um optimizing key conations okay first thing is right as as I told before I think somebody asked a question right just don't create you know for each requirement don't create new flow right so whenever you create flows right try I mean people recommend if if you look at you know lot of white papers are there people say that create one flow per object right that way have better control but again that I don't think that is feasible for complex implementation it's pretty difficult though you mean to have sub flows you may have have multiple flows that that way you can stack the flows right you can rank them and say that which one need to fight before which one need fire after right so that that's the approach I would take right yeah try to do if the small company go one flow per you know object if not try to restrict and keep them to minimum so that you have more control okay thank you um so how does Salesforce flows integrate with other Salesforce features and third party applications uh Salesforce flows see Within Salesforce right it it's native to Salesforce so whatever you are able to do with earlier workflows or process Builder you can do pretty much everything in here and more okay even with flows now you can delete records you can do a lot of you can schedule them right you you you do a lot of stuff in there right and again integrating from outside parties right platform event triggers that kind of thing you can integrate now with flows you can do that platform events and moft is there with mues soft you can integrate with our other applications too with taking the help of moft you can do that one right and again lot of third party apps are coming too right again Force are relatively new right it's it's they're adding lot of new features and again we're going to see a lot of you know stuff in there where flows can integrate with other third party applications too okay Fab uh what is the limitations of using Salesforce flow uh limit itations like any objects right there may be certain considerations that you need to take I don't remember on top moment what the considerations are but pretty much you know you can do pretty much anything with you know like flows though it won't stop you the only thing is Right some limitations like you you can you cannot like you know within a loop you cannot update certain things right you need to package and loop it again hits the governor limits right certain things yes you you you can you need to consider like like even Apex coding right there are some considerations but pretty much you know you know you you can pretty much you know other than the other limitations or the considerations the Salesforce provide you I think it's pretty it can do way more than what you have in the past workflow and process Builders okay cool um so what are some best practices for maintaining and updating Salesforce flows to adapt to changing business needs and technological advancement uh the best practices right one is you know every you have the maintenance release go through the release right even Salesforce Ben I think they are the first people who publish that one each release they go through and lot of fantastic people there who put in examples they give demos to it's not just putting something in there right just listen to that you know just subscribe to this you know the the Ben and other Salesforce Ben and others and just follow through and if you think it adds value to you maybe just revisit it and replace it sometimes you know what you custom buil there may be already provided by Salesforce through the release right so if you keep current with the releases and update your system right not just learning doing it right and again at the same time update your process flows too because when you're doing something in in you know available out of the box right then you just update everything then that way you know you you can be on par with what's happening in flow okay cool um so what's the best approach two flows per object before and after or a lot of simpler and smaller flows with entry criteria uh I think it's two flows per object is a better option right rather than creating too many but again as I told you right if your is a very large corporation like say Coca-Cola or something like that they have so many users right so then maybe you know you create multiple flows but again you can call a flow within flow another flow right or you create the flows and then you can sequence it which one to fire Ben kind of thing right again the minimum number is good yeah before save one after save one that that's a very good idea right if you take a midsize company that's that's really good but again keep it to me minimum right don't don't don't create too many if it's a big company if you have 150 flows nobody knows what's happening with the flows it's very difficult to manage okay okay um Can flows replace Apex triggers nope it can never replace certain features through Apex yeah you can call that anonymously right you can do certain things but Apex is too powerful right you need developers and any time when you have a very very complex integration I think at least my feeling I don't know others right it's a big companies you have a lot of development team technical team let them do it they may do it way way better than you know what you can do with clicks no code right that's why I'm emphasizing even admins learning you know technical stuff is very useful yes it can never I don't think it can replace you know that okay um so can you provide insights into the potential Roi organizations can expect to achieve from implementing business process automation with Salesforce flows oh it depends though yes you you you get a lot of benefit right the thing is once lot of you know in any implementation it's not just CRM Salesforce anything right if you look at that a lot of task can be you know automated in the back end right by doing that the good thing is right one you keep the data clean right data that that's the most important thing right and sometimes people had to update the data at 10 different places right by automating you're reducing that one is right if I update it in place if I'm tired right I'm a fat finger it and I can mess up the data right then everything is out of sync so by doing this automating this one is right you are saving time right you can schedule certain things to you don't need to do now right when the resource are available night time you can schedule it it can run on own then generate email success error report kind of thing right one is you you save time the quality data is fantastic and with the AI coming into picture data is even more important right you need very clean nice data right so Aro is like yeah if you don't have any automation from zero of course I don't believe that right any company will have lot of automation already right any workflows right email triggers anything you do it's automation only right you have it but yeah the a is I don't think I can really quantify though I mean it it's kind of you know it's almost like if you look at that I would say like 60 to 70% of you know things what we work on we try to automate okay thank you um can flow orchestrator replace approval processes no though it doesn't really approval process different right say for example you have a quote approval process and all within that you can use approval process within flows too right you don't it doesn't need to replace but this is like this is more like it creates a work item work item is right when I did it demo the orchestration I said that account manager approval de step it is not approval really it's what it does it take some attributes calculates right it's like getting you know like you know our rating right when I apply for credit card based on my rating they give so much money right kind of so much money I can use it on the credit card right it calculates based on that right so this one it creates a work item somebody had to do something say they need to give some rating or they need to put some comments kind of thing right so approval process is still there you can use approval process by flows but it doesn't the both are totally different though okay okay great cool well those appear to be all the questions we've got um and we're coming up to the hour so um thank thank you so much to everyone for attending we hope you feel um empowered to implement business process automation with Salesforce flow uh in your organizations um feel free to connect with Ser uh on LinkedIn if you have any further questions um I'd like to give a massive thank you to you Ser for sharing your expertise and insights with us today and before we round up um any final words yeah thank you Jan and thank you for giving this opportunity and thank you everyone for taking time from your busy schedule and uh attending this session I hope you got something out of the session thank you brilliant well thank you again to everyone for attending and we hope to see you again for our next webinar soon take care thank you