hi my name is Julia Peis and I'm a principal product manager with the workflow automation team and today we're going to talk about decision tables one of the questions we commonly encounter is why should I use decision tables historically and probably currently in your instances if you're not yet using decision tables business logic has been hardcoded into applications through code workflows and flows this approach brings with it a number of challenges firstly when there's a change in business logic there's a need to know where all of that logic is used so developers need to know if there's a number of flows or scripts using the logic they need to be able to find them to be able to make changes they then need to change all impacted flows and scripts to carry through that change in business logic If You author complex logic you can't reference it elsewhere so if you have a flow with a complex set of IFL statements it's difficult to take that logic and use elsewhere in your workflows you would need to reauthor it additionally logic requires mid skill and above developers to decode and maintain the interfaces for authoring logic using the old way um require developers who can go into scripts and at the minimum level of skill can go into flows and really understand what's going on with the if else logic in a flow or case switch statements in scripts to be able to decode the logic that's powering the application decision tables offer a new way to approach business logic in service now applications to address those challenges with decision tables developers can capture application logic in reusable decision tables that can be built and maintained in partnership with the business decision tables can then be used anywhere the specific logic is needed to power a workflow the benefits of using decision tables include a purpose-built interface for capturing application logic reusable logic across applications that could be stored in a single place streamline code that changes less frequently if you looked at the flow that was using the decision table in the previous slide you see that the slow the flow had been significantly streamlined and reduced because the hard-coded IFL statements were no longer needed lastly the benefits of decision tables include better tools to collaborate with business stakeholders on Logic for more information about this last benefit look for the video answering the question of how business users can be involved in the logic authoring process with decision tables decision tables can be used for a wide range of use cases across the platform and can be used anywhere that you are are going to be able to execute logic from a flow or a script but some more specific use cases to consider include conditionally driven routing record routing prioritization escalation and support levels approval thresholds and assignments Dynamic routing to different subflows for Integrations and approvals or other use cases defining eligibility rules capturing complex logic like pricing adjustments tax codes application scoring Etc as well as customer segmentation and targeted Outreach thank you for your time I hope this answered the question why should I use decision tables and that you to will be able to benefit from decoupling logic from code in your applications