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 how can business stakeholders manage decisions some business stakeholders are quite comfortable with service now development and are regularly working in subpro environments building flows processes playbooks or decisions but this video is meant to cover those business users who either have more limited access um and familiar with service now or who are not working in service now at all we'll talk about the two different avenues that admins can use to Grant access to manage business rules and decision rules via decision tables the first is giving users access to manage rules in service now and the second is to manage rules via Excel admins can apply roles and permissions to limit user access to decision tables the first role they can use is the decision author role this role gives you users full control over the rows and decision tables users can add new rows delete rows specify conditions and set result values however users can't modify the decision table structure which includes the inputs and the columns in this decision table this protects against the possibility of a business user changing the structure of a table without understanding where that table is used like a flow or a script that is expecting a specific format and structure for even more limited access admins can grant users the decision result editor role this role is intended for users who are not changing any of the logic in their decision table but they are changing the result values with this role users can change values in the result columns but they can't modify the decision table structure and they can't add or delete rows or modify condition cells the third approach for managing decision Tables by business users within service now is to give these users delegated development access delegated development access gives users full access to decision tables for a specific scope so this would limit them to a specific application but would require that the users have knowledge of how to create the structure of a decision table as well as the content of it in the decision rows the other approach to managing decision Rules by business stakeholders is to manage rules in Excel business users can work on decisions in Excel and import them back into service now once a decision table has inputs in columns a developer can export that decision table to excel business users can then fill out rules in the Excel template with validations and pre-populated drop-down options as you can see here the possible values for results if there's a record a reference result are available within that Excel template the Excel template includes also includes dropdowns for operators and any choice values and has rules in place to ensure that business users follow the validations that are applied within the the service now interface completed Excel templates can then be imported back into service now the import will identify errors and provide resolution instructions in case there are any challenges with that import and the developer can partner with the business user to rectify any errors and allow for reupload thank you for your time I I hope this answered the question of how business stakeholders can use decision tables and that it encourages better partnership between your business stakeholders and developers when managing application logic thank you