Announcing the Global SNUG Board of Directors. Learn more here
10-24-2022 02:40 AM - edited 04-16-2024 03:52 AM
Workflow Automation CoE > Decision Tables > FAQ
With the Washington DC Release, Decision Builder is now integrated into Workflow Studio. Access Decision Builder alongside other powerful tools such as Flow Designer and Playbooks to seamlessly integrate decision tables with workflows.
The short answer is no, Decision Tables are a platform product, included with any ServiceNow subscription.
Since the San Diego release, Decision Tables allow you to use a range of different result types, like String, Integer, Choice, and more (see Options in Docs).
Prior to the San Diego release, Decision Tables only supported the reference result type. Therefore, in order to use it, you’d have to either already have a table that houses options for your results (e.g., Assignment Group, Priority), or you needed to create a custom table to house possible result answers, which may count as (bundled) custom tables.
Decision Tables are available for all levels of developers, including no- and low-coders. Experienced low- and pro-code developers can benefit from their understanding of the ServiceNow table architecture, and thus make use of reference tables. Low- and no-code developers can either use simple inputs, conditions, and outputs or even not interact with the decision on the Now Platform at all and instead edit and maintain the decision in Excel instead.
[Update for Utah Release]
We’ve released a native Default result option to Decision Builder in the Utah release.
For instances prior to Utah, you can use one of these workarounds:
Hi Lisa,
Its very possible I dreamt this scenario 😀, but I thought the decision_result_editor role was intended for process managers so they could update the result of a condition as needed in production.
Our example is for Code of Ethics Approvals. The developer built the conditions and initial results, but we thought we could allow the COE folks to edit the approvers (results) as responsibilities change within their group.
If this was not the intent of the decision_result_editor role and the results should not be edited in production please let me know. I will be sad though as we were excited about allowing these changes without all the paperwork and processes of a production change.
Thank you so much!
Mariah Thomas / KeyBank
@Mariah Lea Can you please let me know which release your instance is on and check the Application Manager for updates to the Decision Builder and Decision Table Builder store apps.
If you're on a Vancouver instance, those should be v5.0.0 and v5.0.2, on a Washington DC instance (e.g. test on a PDI) those should be v6.1.0.
@Lisa Holenstein - Hi Lisa, we are on Vancouver and I confirmed we are up to date on Decision Builder and Decision Table Builder.
@Mariah Lea Thank you for checking! Would you please be so kind and submit a case to support so our teams can investigate?
Thank you,
Lisa
@Lisa Holenstein - We have had a case open since October (CS6944796). It wasn't until recently that I thought maybe I was misunderstanding the intent when it came to process managers having the ability to update results in production. There are pretty detailed notes in the case from my tests late last week. Thank you so much! Mariah