Flow Designer: Script Editor Dot Walking and Data Pill Evaluation Failures in the Make a Decision Step Issue <!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } This article details a Flow Designer issue in the Make a Decision step, causing script editor dot walking and data pill evaluation failures. It explains the issue's root cause, manual remediation steps, and the fix's scope. Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } All Releases Resolution<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Field Details Error / Symptom Script dot walking to Make a Decision output returns undefined or empty at runtime. Cause Stale flow data omits result_elements from the stored output path. Autocomplete reflects the stale data and suggests an incorrect path. Workaround Manually include result_elements in the script path. For single results: fd_data._1__make_a_decision.answer.result_elements.<column>. For multi-results under For-Each: fd_data._2__for_each.item.result_elements.<column>. Currency field Currency fields accessed via Data Pill Picker in branch-enabled flows always return $0.00. Use a manually corrected script path instead. Auto-Remediation Not available. Manual correction or flow rebuild is required for all affected flows. Permanent Fix Apply the corrected script fix to your instance. Recreate affected flows after the fix is applied. Troubleshooting Scenarios and Instructions Scenario 1: Script dot walking returns undefined or empty for Make a Decision outputs. Step 1: Confirm the affected flow Open the affected flow in Flow Designer. Locate the Make a Decision step and the Log or Script step that follows it. Open the script editor and dot walk to the Make a Decision output using answer. Confirm that result_elements does not appear in the autocomplete suggestions and that the column field is prompted directly. Step 2: Correct the script path manually Do not use the autocomplete suggestion. Manually include result_elements in the script path. For First Decision that matches (single result), use the following pattern: fd_data._1__make_a_decision.answer.result_elements.<output_column_name> For Run all decisions that match (multiple results, inside a For-Each block), use the following pattern: fd_data._2__for_each.item.result_elements.<output_column_name> Note: Replace <output_column_name> with the actual column name from your decision table. Replace the step index prefix (for example, _1__ or _2__) with the index that matches your flow step order. Step 3: Validate the output Add or update a Log step to capture the Make a Decision output using the corrected path. Execute the flow and verify that the Log step returns the expected value for all field types. Scenario 2: Currency fields accessed through the Data Pill Picker always return $0.00 in branch-enabled configurations. Confirm that the flow uses branches and that the Log step is placed within the branch. Avoid using the Data Pill Picker for currency fields in this configuration. Use a script with the manually corrected result_elements path instead. Validate that the script returns the correct currency value at runtime. Scenario 3: The workaround does not resolve the issue and the flow continues to return incorrect values. Delete the affected flow. Recreate the flow after confirming that the fix has been applied to your instance. Verify that the script editor autocomplete now includes result_elements in dot walk suggestions for Make a Decision outputs. Note: Flows created after the fix is applied do not store stale data and are not affected by this issue. Upgrade Troubleshooting The fix corrects the stale data condition at flow creation time and prevents this issue from occurring in new flows after it is applied. However, existing flows created during the defect window are not automatically repaired. Those flows require manual remediation. Upgrade Behavior Details Prevents new issues Yes. Flows created after the fix is applied store correct output paths. Repairs existing flows No. Flows created during the defect window require manual script correction or rebuild. Affects published flows Yes, if those flows use script-based access to Make a Decision outputs. Rollback Not available. Additional Information This issue is not limited to a specific customer configuration. Any flow that uses the Make a Decision step with script-based output access and was created during the defect window may be affected. The invalid scenario of placing a Log step outside a branch in a branch-enabled, First Decision that matches configuration produces an Internal Server Error in both the current and pre-fix states. This is expected behavior and is not caused by this defect. Flows that access Make a Decision outputs using only the Data Pill Picker (no script) are affected only for currency field types in branch-enabled configurations. All other field types evaluate correctly in non-script configurations. The fix resolves stale data stored at flow creation time. Flows created after the fix is applied are not affected. Flows created during the defect window require manual remediation using the workaround steps in this article. For additional assistance, contact ServiceNow Support.