Not shunning customization at all - just ensuring that we are doing 'customizing' the correct way. Over the 13 years I've worked with the platform, I've seen bad customizations that make the platform unusable, and become a major barrier for innovation. Our intent is to ensure that customizations are done with the necessary oversight to ensure they don't conflict with OOB capabilities and interactions between other modules in the platform, and to ensure that customizations aren't created in lieu of an OOB configurable capability - which is where training comes into the picture.

You can also call them business smart customization Check out these are the ServiceNow customer success center

You don't need to do anything special. (Create and) switch to the Update Set you want to track the Decision Table in. Make any changes and save. That's enough for it to be part of the current update set. If you are using the draft authoring feature and want the decision table to be available to be called from a flow, subflow or code snippet, you need to also publish the Decision Table. -LH

Make sure to check the logged in user working the playbook has the (ACL) permissions to read/upload attachments for the record. If you're (for example) using the Update Record activity in your playbook, check the UI Layout Tab and set "Attachments -> Attachment Source" to "Related Record" or "Parent Record" to determine which attachments to show. When testing the playbook, some UI features are not available when using the Playbook Preview, instead test it from the workspace it's being worked in. If you have further issues with this, please submit a case to support.servicenow.com/ or post your questions on the Community post for this academy: sn.works/workflowacademy/2404 -LH

Hi Miguel, one option to explore is to work with subflows. One to do two approvals, and one for all four. You can reuse the same decision table in each subflow to determine the approvers or decide to split your decision table into two. One to determine which subflow to run based on the amount (in case the amount changes, keep it in a decision table so you don't need to change the flow every time the value changes), and a second decision table for the approvers, in case they depend on other conditions (category, business service, priority, etc.) than just the amount. Check this article on decisions & dynamic flows: sn.works/CoE/FD/DynamicFlowDecision -LH

Thank you, Lisa! I'll explore that idea!

servicenow.zoom.us/meeting/register/tJIlcOysqTssGtGOlRPuzUaHdzBhPfsX-byw#/registration

Hi John, make sure to add an action to your custom activity and that the user has permissions (roles, ACL, etc.) to update the record. If you're using the flow data table and set the assigned to or assignment group, only users matching that condition would be able to update the record. -LH

Glad it was helpful! -LH

Not having much UI Builder experience, I don't know. You might want to try the community or perhaps reach out to Brad Tilton directly. Thx

Hi there! I would use a combination of tools here. First, you can use this pattern to get the Requested Item approved. www.servicenow.com/community/developer-forum/subflow-to-create-approvals-from-results-of-mrvs/m-p/2627308 Next, you can use a for each to create the catalog tasks with the 'wait for completion' box unchecked, then further down the flow do a do the following until with a look up records to check if all catalog tasks have been completed. Add a little timer to that loop (something like 5 minutes or half an hour, depending on the use case) so it won't check back-to-back.