hello and welcome my name is lisa howenstein i'm an outbound product manager for workflow automation in the now platform i've been working with the nav platform for almost six years and i've just had my three year anniversary at servicenow like a couple of months ago this this text is a little older but this is how long i've been here um i'm joined by my amazing colleagues live on camera with me are andrew barnes and brian vimshlega please give us a quick shout out in a small introduction andrew brian sure hey i'm brian bim schlager i am uh one of the product managers here at servicenow and one of the products that i am pm for is flow designer so i've been here uh just over two years i've been working on flow designer since i've joined so very excited to join today and hopefully be able to answer any of your questions that come up oh andrew thank you thank you for uh letting me join you today lisa i'm andrew barnes i am a product success manager for creator workflows here at servicenow and one of the things my team does is supports uh you know all of our wonderful platform products and flow designer being one of them and i have been working on and around servicenow for a little over eight years and i've been here ad service now for three and a half and flow designer is one of my favorite products here at servicenow and so i'm excited to talk about it with you today yes me too so this is our 18th academy session already and we're coming up on our academy anniversary actually the first session that we did was last year on june 30th so we're uh almost one time around the sun with our academy which makes me quite proud because it's still going and we still have an amazing topic to talk about and today's topic is very exciting it's flow designer and i know a lot of people are maybe hesitant or haven't gotten around to work with flow designer yet so today is all about migrating towards flow designer and our other workflow product and we want to make sure that you know how to migrate um and which technology to migrate flow design so back in april we already had one session that was going through flow designer best and good practices and we hinted on some guidance on how to approach migrating from the old technology stack to the new one this time around we want to dedicate some more time on actual migration use case and as always this session is will be recorded edit it and then post it to youtube sometime next week and i'll also share the presentation on the community post and with that we'll get into the agenda so we'll kick this off with a little in repetition from the last session for those who haven't seen last the last academy i will give you a brief overview of the flow designer history so far and some arguments on why we think it's time and really has been time for a while to consider switching and start switching and adopt flow designer and the other no newer workflow tools over the leg and to guide you on your migration journey we want to supply you with what we think is the best approach start this process and some highlight and a highlight tour covering most but probably not all of the use cases that are already possible flow designer pad and decisions day and how they make your life easier my wonderful friend andrew already posted yes please put any questions that you have in the q a section so we can keep track of the answers answer them um either live or at the end of this so how did we get here well that's a very good question and i have a couple of slides detailing that the flow designer history is a lot longer than i expected when i started researching this topic for the last session that we did we actually started releasing flow designer back in kingston as mostly an alternative to async business and in london we went beyond orchestration and we added complex and dynamic integrations reusable components but and also uh catalog filament which i think is probably the most prominent uh use case that we usually have for flows and workflows is a lot of request fulfillment part uh with madrid we brought forebra foreground or background execution to make it a real workflow alternative and to make ourselves ipos in new york we expanded integration hub to deliver enterprise enterprise-grade integrations but we also added the run from api option and more workflow more flow configuration up orlando then brought some action steps to easily parse and use complex data that is xml and json um to and we added dynamic flows and dynamic outputs and finally what one of the very handy features that we have in flow designer that is transform function um in paris we added loads of things so this list just gets longer and longer with each release it's ridiculous paris added run with roles content x filtering decision table action duplicate action or subflow which is very handy if you want we use the same gun before but don't want to configure all of it again we added flow data definitions specifically for the integration and the use of flows to support and power process automation designer activity and then with quebec we brought wonderful ui redesign our amazing designers made a really great job to make flow look even better and be more accessible out of flow variables which one of the features that have been asked for for ages like forever people wanted their stretchpad variables we now have them in flow design and then there's also a ui to set feature act so imagine you have um citizen developers in your hr department and you want to give them the power of flow designer but you definitely definitely don't want them to be able to change things in your active directory or any other system that they shouldn't have access to so you can determine that those people per role only have access to say the workday spoke which so content filtering is very powerful the next to last release rome brought action and flow error handling again feature that has been asked for for a long time faster performance and the option to set the logging levels to your own needs and more transform function we're almost in the present with the san diego release so san diego released in march this year brought us more options to build a new way the this is the very first please that we have the option for flow diagramming and it allows you to see the path of your flow that flow can follow and the connection between the elements and developers being able to save scope flows as reusable templates is extra powerful because it will improve accessibility for your low and no code developer and the third big feature in san diego is adding the try and catch error logic into your flow which allows for a flow to be more robust and to continue running even when an error and some more some smaller enhancements include managing feature access slow error handler transform functions more transform functions we just need more transform [Laughter] and then some some updates and edits to the run start date time data pills and how the dates are stored and giving you access to having the run uh time also in utc and local so lisa yes you know i thought maybe we might give brian an opportunity to like share a little bit about which of the things in san diego he thought was the most impactful since that was that was his uh his baby yeah well thank you uh i would say diagramming was definitely the the most fulfilling um we've had a tremendously positive customer response from diagramming so far i know we've talked with a few of the folks that are on the call that have been early adopters and we know there's a long way to to go but even just the initial reactions of saying hey this diagram view makes it so much easier to share what i'm working on with a business stakeholder uh that that seems to have achieved a really big outcome and we know there's more support coming uh you know things like support for service catalog and stages and annotations things like that that really help you decorate your flow and make it more valuable it's all coming but san diego was um diagramming in san diego was a favorite for for me personally and for our engineering team well thanks for sharing i think so too so flow designer objections uh have you started using flow designer let me share the results we have the majority have already used flow designer which makes me very very happy um at least some use cases so we're at over 80 percent that's amazing but i think we can find we can get to more people using it for most cases or all of them so i would love to for those numbers to go up and i hope this session uh will help you go that path and then second of all what have been your biggest objections we have some for performance some for usability most for features i mean that's going to improve with the time and then enablement that's also what we're here for and for the people who say other objections let me see what are your objections in chat all right ellen yes there are more use cases than just flows that's correct and some of those we're going to be talking about today it's true it's not just workflows absolutely right and and we are actually going to touch on several of those yeah just a moment that's what we're here for which is a nice setup there yeah then uh rohan says flows get queued that's the biggest problem i've seen so that would be in the flow in the order of executing engines um do you have uh a word for that ryan uh yes i mean there are ways to uh like run your your flows faster or you know assign higher priority like like a lot of things in flow designer there are a lot of buttons and switches and ways that you can can modify um but if you're if you're running a super high volume of flows eventually queuing is is going to be a thing that you have to be concerned about but you know if some some of the things that we're exploring um in the future uh you know not committed to anything yet but some of the things that we're exploring is uh being able to attach priority to certain flows like similar how in previous releases or recent releases you can say hey i want reporting to be different on this flow than that flow we're exploring ways to assign priority differently based on certain flows as well that's awesome thank you uh so for uh some of this is if you compare flows or regular flows with business rules uh the ones that get queued would be similar to async business rules so async business rules would be queued just the same way that the flows will be today um similarly as as was mentioned here if you configure your flow to run in the foreground or synchronous then it would be just like an after business rule and would run faster than the async version the the one thing i want to uh expand on a little bit on the wording there lisa is this isn't about how fast the flow runs itself the execution time but how soon the execution is invoked so that's yes the speed of the flow is going to be the same yes it's when in your engine ordering is is it going to get invoked so how near to when the trigger was invoked going into the arguments uh some of those the people who were in here in the session last last time may already know this slide but i'll still go through it real quick um the main benefits of using flow designer over legacy technology is well first of all it is our current technology and we're actively developing new features uh we are not removing workflow anytime soon it will not be retired as of now we have no plans you will get plenty ample notice but i mean execution plans are still around we rarely ever shut something off completely um but it has entered a maintenance state so the important part here is we're no longer actively developing new features and functions for either workflow or orchestration and all innovation is being poured into flow designer and integration so i think that's the key thing yes eric ui ui 11 is still there so cms is still there execution plans are still there the only thing that i think is not there is list v3 but other than that i don't think we we hardly shut down anything but still that doesn't doesn't um i don't want to encourage you to keep your old things i i really want to encourage you to give flow designer the chance that it deserves because it has in general a best a better performance than our workflows it is faster it is more reliable having low code uh logic makes your uh your processes your apps more robust and thus more upgrade safe because it's really hard to put in typos into non-scripting logic and with that you will also incur a lot less tech time the second argument is really usability and reusability so creating subflows and flow actions to allows you to reuse them in other contexts and create contained units of logic that are easier to understand and maintain the same of course goes for flow templates then looking at the flow designer layout especially with flow diagramming now it makes it a lot easier to understand what a given flow does than it would be with long scripts if you have a script that is i don't know 100 200 400 lines long it takes you a while to understand what's happening especially if it calls other script includes and maybe the the functions you call aren't named in a speaking manner so you don't necessarily know what's happening and you have to click through and figure out what's happening in your script i think that's a lot better in flows and fl with flow act then the third part is something that i've touched upon touched upon earlier um low code accessibility so uh looking we have easier access and we want to also promote the delegated development we've talked about feature access and content content filtering to make sure that the low code developers the citizen developers the process owners you want to involve only have access to those features that they they want to they need to use and then lastly and most importantly flow designer and integration hub have reached and exceeded the functionality if not before then at the latest with the quebec release there are very very minor very few things that aren't possible in flow designer yet and as far as i know all of them on purpose so it's not an oversight that we don't allow these things if you want to know more we had some more info in the previous session and i will link to that in the other i will link to the previous session in the show notes and in the video and i will also post it in chat for those who haven't seen it yet and then next if you use the new and modern tech stack it opens the door to use even more new tool one of them is one of my really favorite un most under appreciated small thing but it makes your life so much easier and that is decision tables decision tables allow you to remove complex if-then-else logic from your flows or case switch things make decisions in an easy-to-use interface and you can also grant delegated development to say process owners so decoupling your decisions from your logic allows you to have those process owners decide if the threshold for the extra approval is a thousand dollars or two thousand dollars as a developer you most likely don't care but they do and if you have the decisions in decision tables and not in your flow logic it makes it a lot easier and you don't have to go through the whole publishing process for the flow every time a number changes second consider using process automation designer if you already build flows with smaller targeted and reusable subflows and flow actions it makes it a lot easier to switch to process automation designer when your processes become more complex you can use the subflows and flow actions to power the individual process automation designer activities and at the end of the day you may need dedicated smaller projects to handle migration for specific groups but i want to encourage you to look at what you already have and create those reusable components and then the third part is automation engine so automation engine brings you the power of three products now to allow you to automate integrations and document processing you likely know integration hub already which is there to have integrations provided by servicenow to third-party apis and you can also create your own custom integrations the second will be rpa so robotic process automation which allows you to integrate with systems that do not have an api andrew and daniel have done an awesome lab and knowledge about it so if you're interested about that i'll link that in the resources of this presentation as well so yes robots rule the world daniel and then lastly the newest addition to automation engine is called document intelligence which allows you to extract data from scanned documents or printed or whatever documents pdfs that you upload to the system and it actually gets the fields and the the value in those fields and you can use them in your process very exciting i think that's all i wanted to do about it to tell you about this well i think that's a nice setup uh to talking about well let's get started let's do it so let's give you some guidelines on how to actually begin your migration journey if you haven't already started it if you've already started it hopefully we can add in some tips and findings and if you have some please share them with us so if you're here live put them in the chat and if you're watching this later put it in the comments in the youtube and we'll come back and read them and incorporate them so if you are starting a migration project you might have seen something like this before which is you know a big project plan with multiple phases in the first phase here that we're outlining is you know determine all of the different places that we could migrate from and then to flow designer um so i'm going to leak a little spoiler here we're not going to suggest this plan so don't get nervous but if you were going to approach it from this angle you could identify all of the different workflows the business rules the script includes uh the scheduled jobs those inbound emails all of the different things that flow designer can actually achieve in a more low code manner and document them all and then you know then you move into that second phase uh if you somehow completed the first one uh and then start to to actually like make a plan and assign these tasks out and have a two-year plan to do this big migration this isn't actually how we suggest doing this uh one because it's too resource uh intensive and freezes active productive development delivering more value directly to your organization so let's shelve this and look at what our proposed plan is so if you could step me forward lisa yes all right so our migration recommendation um the actual the first step even before you get to these is learn flow designer so get someone on your team who's experienced with flow designer understands it so appoint a champion in your organization to go and learn flow designer get comfortable with it and can be that central resource for your team to go through this migration process but once you've you know done that and decided that you would like to start taking advantage of flow designer which as lisa pointed out unlocks some of those other components so it's not just useful to do in and of itself it's it is an unlocking mechanism for other opportunities here's how we've structured an approach which is establish a plan and a process for what you're going to target and that is you know that governance piece this isn't you know big heavy-handed governance this is team governance for your team to govern how you're going to approach this process which is one really good rule that we found is new requirements as they're coming in if flow designer can solve the problem then that is an easy sort of guideline for your team to now start using flow designer for new development to meet new needs as those requirements are coming in so you know this is this is an easy way to get started to making sure that your team understands the power of these uh before we start overhauling other existing things then as you are getting familiar and you're getting requests to change uh existing uh you know workflows and processes um and those need to be overhauled well that is a good opportunity then to move it from where it is be that asynchronous business rule or workflow to flow design you touch it you move it if you touch it you move it exactly so if i'm going in and and making a significant change to a an old workflow that's a great opportunity to see if i can you know break that up into parts and i'm actually gonna skip a little bit to the incremental part there is is if i'm enhancing a workflow and pulling it into my process i don't have to convert it all at once i can actually convert the parts that i'm working on into flows and then invoke the workflow from that call of workflow action or the other way around or the or the other way around so i can you know have that established workflow and call my flow from there so absolutely so that's you know for your work and then looking at you know service downs uh provided functionality is another good time you know so in this adapter baseline section here is when you can look at moving from the old workflows of change to adopting the new change flows for example and there's other opportunities like that um as servicenow has converted its workflows and we're gonna we're gonna touch on that in just a moment as well in in more particulars um we have been shipping more things with flows that replace those legacy workflows and you know as part of this strategy that's a good time to consider these and and bring those in and then being prescriptive about it right so setting aside a time so once you're comfortable you've got this in your your whole team is able to build flows you understand them then you can start setting goals and time to you know do conversions as you're working on things and and getting and unlocking that new power in flow designer and and it's not just those one thing i want to add to some of those tools is as we move to more low code methods we unlock the ability to do things like being able to collaborate with others like our business developers or citizen developers and allow them to contribute to the flows that are running their processes so part of this conversion can tie into other organizational goals by doing things like empowering those distributed and citizen developers to come collaborate on their workflows now that we've made them into flow designer and made it accessible to them and as part of that you know that expert that i said to designate is a good thing to do whenever you have a process like that establish something like office hours a you can do a community of practice as well to share questions and answers around uh you know moving to flow designer and centralizing those things into something like office hours helps you know keep some of that interrupt away from that that expert and you know centralizes it uh to a given time and allows other folks to hear and collaborate on those uh so you get some uh scale at that time the last thing in the incremental before we move on is you can you can reference we talked about referencing calling the workflows uh and calling flows from workflows the other thing you can do is you know you can invoke script includes from inside custom actions in your flows until they have been moved into direct low code alternatives like a spoke in integration hub so we we think and we've worked with customers to do conversions just like this and this is uh you know a successful strategy for migration for in particular all of these things we've set in the flow context but this actually works for more than just flow designer i've done very similar strategies with customers around automated test framework adoption for example the process is very similar process so um before we move to the next side lisa do we have any thoughts or comments from you on uh on this one i think uh maybe one more thing adding to the adopting the baseline um one thing there is not just moving from the previous version that we shipped with our earlier releases but it's also a moment to analyze possible custom implementations so if you and your uh if your instance has been around longer maybe you haven't ever used out of the box uh processes for these things maybe you have your custom implementation for change flows or of csm processes and when you do this migration this is an awesome chance to check out what we are delivering by now and i know that for example change is making it's also making heavy use of decision tables in their change policies so this is a great chance to replace custom implementations with out of the box again making your uh your upgrade lives easier making your testing lives easier and so that is one more point i had for this one excellent point lisa and and really really good call out there that i i forgot to mention um so for example uh you know in a in a past life i'll give you a little anecdote um in a previous system it didn't have an email engine and so my team had to craft an email engine in the system and then you know once the that provider actually built it in eventually we you know made the decision to convert to the out-of-the-box one because then we didn't have to maintain that anymore and so a very similar thing here is you may have built functionality but now servicenow has made a baseline and this is a good time to make those evaluations and do that conversion let's do the the common injections um so the first one here is you know why should you use these low code tools i think we covered this to some extent um you wanted to you would allow uh unlocking of folks like citizen developers to contribute um but professional developers actually work faster in low code tools as well um and it's more upgrade safe and you can do things like make custom actions when you need uh so that that one seems pretty straightforward nobody takes away the scripting from you it's just it's supposed to be in the place where it's supposed to be and that is custom actions yeah and so you've got a large code base how do you even start um so like the the process we just outlined is is a good way to target that which is you know do this incrementally take it on piecemeal as you need to adjust things and you know moving the new requirements into the new way is a good very first start so looking at the atf test suites for workflows and business rules we've covered atf quite a few times here on the platform academy in the earlier sessions i think our first one which is our anniversary one coming up covers some of this is which is you want to test for outcomes instead of individual steps and so atf's that are designed that way will actually continue to work for you after this migration yes next slide and the fun thing is mark has asked the perfect question for this one and he asked within uh areas in servicenow you still have workflow two examples is knowledge bases or field service management is this also on the roadmap to have flow everywhere this is perfect thank you for sending that out mark thank you [Laughter] um so you know servicenow is adopting a similar strategy to the one that we're uh letting you know which is they're doing it incrementally as those products get overhauled their workflows they're moving them to flow designer uh so their path is the same as our path um so this is uh you know just an easy setup there thank you mark um so if you've tried flow designer in the past um you know it is a ever evolving product uh thank you brian and brian's team delivering new features and functionality release of release so uh give it a try check out some of our resources that we'll have to show you what is in you know san diego release and even the previous releases to get you up to speed on what flow designer can do for you today and the last one on can't handle errors in flow designer well hey i just mentioned that you should check out the san diego release uh and one of the cool things in san diego was the uh flow action air handler and tri-flow logic um so those those have been enabled in rome in san diego for you and that should solve that objection and also uh plugging this right here already the next academy session in two weeks will be about uh improving performance and debugging flows and going through error handling and tri-flow logic so it's a topic it's coming awesome yes thank you lisa sure so we've mentioned this a little bit which is you know this is an opportunity to for change um so you get a chance to not just convert from one process to another but while you're doing that you can do things like optimize that process you can do things uh like simplifying more complex scenarios now that you might have more access to the powerful actions in flow designer that can simplify how you built those uh processes and and deliver value faster and with less complication uh and in that more upgrade safe way so there's lots of opportunities when you're doing an overhaul to not just use the new tool directly but you get to unlock the things that that new tool is providing you in those powerful actions and in the things like the subflows that you build that are reusable and can centralize those processes for you and unlocks other opportunities like we said like being able to use process automation designer so when you build those subflows and flows that you can make them available to now fit into a process that you can leverage in process automation designer uh so that's super exciting um that uh that those feed into each other and the other ones that we mentioned on the other side like automation engine and document intelligence and rpa all of these things start to come together yeah when you unlock their power by leveraging flow designer awesome thank you so much andrew that was that was really interesting i think it's so helpful to have a strategy and a path forward and in order to get your opinion on this we'll now start the next poll and while we do that i will continue with the next slides and go through the key takeaways for this thing before i hit upon individual use cases um i think i i hope that our main points are got very clear use the low code workflow products um it accelerates your experienced developers and allows you to involve more low coders and citizen developers it'll also increase your development capacity at the end of the day because if you include everyone everyone can contribute to your to your processes become more efficient and and more automated reusability we've touched upon this a couple of times is a big big keyword reuse subflows reuse process activity definitions reuse decision tables in different processes where applicable it reduces tech depth we want to create up upgrades save workflows and by workflows in that case i mean flows and uh decisions and processes and everything that flows adopting baseline and accelerating the development develop velocity and of course making your upgrades faster and then incremental migration i think that one has been uh discussed enough replace what you touch and now uh just to give you some more info we have a couple of minutes left and i hope i get through most of those use case but if i do not we are currently working on a small video series um and this is the first place uh we're announcing this so we're working together with our awesome content creation teams to bring you specific and targeted videos for each of those use cases so you will be able to find those on youtube we'll post them on the community on all of the channels that you've found this webinar on so we want to make sure that you know exactly how do you get from point a how do i get from my service catalog fulfillment workflow to doing this in flow designer how do i do uh inbound email flows as opposed to inbound email actions so we're very excited to uh work together with our colleagues and andrew and i are are planning this thoroughly and we hope we cover all of the use cases but in case that we forget some we would love all of your uh um questions and ideas for use cases that you would love to see covered in a in a small video in a small blog post to help you navigate those migration use case and we yes absolutely more ideas more input more more content is always good in general we want to divvy up the use cases that we could come up with in some different categories first there's workflows the i mean flow designer replaces workflow editor but not only that it can also replace email inbound and as well as outbound email and not just email but notifications in general remind me to change the slide andrew because for the video series andrew pointed out it should be all kinds of notifications right it's not just emails it's also sending sms or messages to teams or slack or through any of the other channels that we offer and that's really one of the bigger use cases what i've failed to mention on the workflow part is the biggest i think the biggest part and that the poll will probably show that too uh the biggest part is service catalog fulfillment and yes thank you the poll absolutely confirms it's 80 percent um of people who want to see service catalog fulfillment topics so our assumption was there i'm very glad so it's nice to get a little validation right i think so too and then the third bucket would be scripting custom scripting so replacing scheduled jobs with scheduled flows replacing after async business rules with flows replacing script includes with reusable flow action or also called spokes as we said before if you want to take the iterative approach and you don't want to create everything at the same time you can create custom actions and just call the script includes and then lastly of course replacing complex if then else and case switch statements with decisions and the fourth big bucket is integrations of course it's integrations either through integration hub or having scripted rest api and also replacing using data stream actions as data sources that can be done for example in the new integration hub import tool which allows you to do a low code mapping like just like you have in flow designer dragging and dropping and mapping the data pills applying transforms in the interface to you to the data that comes in through a data stream action so that is a really cool feature if you haven't seen that yet make sure to check it out especially everything around integrations i want to call out there's a learn integrations on the servicenow platform youtube series on the dev program team by chuck tomasi and he did a very great job going through all of those points using the the rest api trigger data streams and import integration hub import tool so make sure to check that one out all right some fun things and examples i i can get through some of those i think i hope so you remember workflow it can look like this it can look a lot more complex but you can replace catalog fulfillment flows you can see the stages you can add stages in flow designer and those will be just uh represented just as much in the in your portal in your employee center or wherever you need those stages um they're currently not supported on uh flow diagramming but that they will be in the future release one big new feature in san diego that i really really love i bet every one of you has at some point uh started to or scripted how to execute order guide items in a sequence so that they don't all run at the same time but you cannot i don't know deliver the laptop if the person doesn't have an id account yet or you don't you can't do much with your outlook inbox if you don't have a password yet so with process automation designer creating an order guide sequence makes uh the sequencing of uh request fulfillment so much easier you can add new lanes you can tell the lanes to run in parallel or after another or when the previous one starts you can have the same for the different items and you can decide and move them around and drag and drop it's super awesome so definitely check this out sla workflows i think those were some of the first that got adopted for flow designer um and have been replaced also out of the box so check those out they do everything you're used to from workflow you can wait for a duration of time for slas and uh do whatever you need to do for your slas to notify people right okay this is one of my favorite slides so workflows could get so complex and so hard to read it hurts my soul have you seen these i mean i i rejected the the peer reviews when they looked like this how would you ever figure out where to go from which and what happens in this flow it's a lot better it was why i rejected because i said i can't actually understand what this is doing try again [Laughter] thank you try again next so our try again version is process automation designer and i think it makes processes to be so much more readable when you have this kanban board style interface and again you can decide to have the different phases run one after the other in parallel you can have conditional lanes uh with the latest release you can run the different um activities after another immediately whatever you want and also new in san diego is optional activities so if you want to learn how to do that you can check out micro utercon lab which is also on now learning on process automation designer and playbooks those two labs teach you how to make use of ad hoc activities that can be added at runtime which can be so so powerful because your processes you can sketch them out but they rarely meet the reality and sometimes you just need to add something at runtime we've talked about inbound email processing so replacing custom script again with uh with easy to understand flow actions outbound emails the same we can combine flow designer and decision builder to decide which notification is supposed to be sent so this is a really handy use case if you want to just have one flow that runs for notifications but depending on the stage or the priority or whatever other criteria you want different notifications to be sent out to different people schedule jobs is another one that is rather obvious or not i don't know they run on a regular cadence and you can do the same with flow designer we've talked about async and um after business rules um so the only business rules that we currently cannot replace are the before business rules before query for example um so those should stay in business rules for now creating spokes instead of script includes or reusing scripting script includes in spoke actions mentioned a couple of times that's one of the bigger use cases when you migrate incrementally and then if you give it a speaking name it'll be so much easier to use in your flows going forward so decisions i've talked about this replacing scripts or switch statements with decision tables is so useful because the new decision builder is so nice to use especially since in san diego we've added the option to have multiple outputs not just one and to have outputs that are variables and not just reference tables that makes it so much more useful and so much better so i hope you give decision tables a whirl because they make your life so much easier the rest of the slides that are coming are integrations i've already pointed you to the the youtube series and the only thing i want to start now is the last um poll just real quick i want to get your feedback how you like this session before everybody takes off and please please give us feedback yes give us feedback make these sessions better hopefully if you go back and look at the very first one which is anniversaries coming up you'll see that we've actually taken your feedback uh and adjusted the program since then and hopefully it's providing continually improved value to you yeah i love how active the chat was today there was so many great uh questions and and input we love that as i said i will post uh the the uh presentation too you will get access to all of the good links all of the info that i put in the information resources make sure to check them out there's training there's videos there's knowledge courses check this out i think flow designer is absolutely ready for the spotlight that's about all i have to say for that thank you andrew thank you brian thank you lisa for having us thank you brian for sharing as well thank you everybody for joining us today have a wonderful wonderful day