How Data Travels Between Elements (Automatic Output Handling & Automatic Field Discovery)

<p>One of Flow’s biggest and most unique capabilities is its ability to let you set up processes where data travels from the output of one Flow element to the input of the next.</p><p>To use upstream data, the user clicks on a combobox in a Flow element property editor and selects from the available references.</p><p>For some kinds of data, these references are created automatically. For other kinds, you have to do it manually. There’s a third bucket of kinds of data that give you the choice to do it manually or have it created automatically. <a href="https://unofficialsf.com/optimizing-lightning-component-inputs-and-outputs-in-flow-screens/">More detail is available here.</a></p><p>As of Spring ’20, automatic references are generated for all kinds of Flow data except for:</p><ul><li>Subflow outputs (coming in Summer ’20)</li><li>Loop index (the reference to the current member of a collection in a loop, coming in Summer ’20)</li><li>Pause element</li></ul><h3>Automatic Field Discovery</h3><p>Automatic Field Discovery causes a Get Records to automatically pull in the necessary field values. You no longer have to manually choose them.  </p><h3>Considerations When Choosing Automatic Vs. Manual</h3><p>The future is Automatic. Use it when you can. It’s faster and easier.</p><p>When setting up Conditional Field Visibility relationships between fields, if the condition depends on the value of a screen component, make sure to use Automatic output handling. That’s because the manual variables don’t get updated until you transition to the next screen.</p><p>Currently, if you use Automatic Output Handling with a screen component attribute that you’re passing an input too, Flow will remember the most recent value for that attribute. If you Previous to a point prior to the screen and then return to the screen it will not update to a new value. This is discussed more <a href="https://unofficialsf.com/optimizing-lightning-component-inputs-and-outputs-in-flow-screens/">here</a>. We’re changing the behavior in 226 so that Next transitions will always recalculate the input attribute.</p>

Title Changes:

Removed	Added
Deleted: How Data Travels Between Elements	Added: How Data Travels Between Elements (Automatic Output Handling & Automatic Field Discovery)

Content Changes:

Removed	Added
Deleted: <p>One of Flow's biggest and most unique capabilities is its ability to let you set up processes where data travels from the output of one Flow element to the input of the next.</p><p>To use upstream data, the user clicks on a combobox in a Flow element property editor and selects from the available references.</p><p>For some kinds of data, these references are created automatically. For other kinds, you have to do it manually. There's a third bucket of kinds of data that give you the choice to do it manually or have it created automatically. <a href="https://unofficialsf.com/optimizing-lightning-component-inputs-and-outputs-in-flow-screens/">More detail is available here.</a></p><p>As of Spring '20, automatic references are generated for all kinds of Flow data except for:</p><ul><li>Subflow outputs (coming in Summer '20)</li><li>Loop index (the reference to the current member of a collection in a loop, coming in Summer '20)</li><li>Pause element</li></ul><h3>Automatic Field Discovery</h3><p>Automatic Field Discovery causes a Get Records to automatically pull in the necessary field values. You no longer have to manually choose them. </p><h3>Considerations When Choosing Automatic Vs. Manual</h3><p>The future is Automatic. Use it when you can. It's faster and easier.</p><p>When setting up Conditional Field Visibility relationships between fields, if the condition depends on the value of a screen component, make sure to use Automatic output handling. That's because the manual variables don't get updated until you transition to the next screen.</p><p>Currently, if you use Automatic Output Handling with a screen component attribute that you're passing an input too, Flow will remember the most recent value for that attribute. If you Previous to a point prior to the screen and then return to the screen it will not update to a new value. This is discussed more <a href="https://unofficialsf.com/optimizing-lightning-component-inputs-and-outputs-in-flow-screens/">here</a>. We're changing the behavior in 226 so that Next transitions will always recalculate the input attribute.~~</p><p>~~ </p>	Added: <p>One of Flow’s biggest and most unique capabilities is its ability to let you set up processes where data travels from the output of one Flow element to the input of the next.</p><p>To use upstream data, the user clicks on a combobox in a Flow element property editor and selects from the available references.</p><p>For some kinds of data, these references are created automatically. For other kinds, you have to do it manually. There’s a third bucket of kinds of data that give you the choice to do it manually or have it created automatically. <a href="https://unofficialsf.com/optimizing-lightning-component-inputs-and-outputs-in-flow-screens/">More detail is available here.</a></p><p>As of Spring ’20, automatic references are generated for all kinds of Flow data except for:</p><ul><li>Subflow outputs (coming in Summer ’20)</li><li>Loop index (the reference to the current member of a collection in a loop, coming in Summer ’20)</li><li>Pause element</li></ul><h3>Automatic Field Discovery</h3><p>Automatic Field Discovery causes a Get Records to automatically pull in the necessary field values. You no longer have to manually choose them. </p><h3>Considerations When Choosing Automatic Vs. Manual</h3><p>The future is Automatic. Use it when you can. It’s faster and easier.</p><p>When setting up Conditional Field Visibility relationships between fields, if the condition depends on the value of a screen component, make sure to use Automatic output handling. That’s because the manual variables don’t get updated until you transition to the next screen.</p><p>Currently, if you use Automatic Output Handling with a screen component attribute that you’re passing an input too, Flow will remember the most recent value for that attribute. If you Previous to a point prior to the screen and then return to the screen it will not update to a new value. This is discussed more <a href="https://unofficialsf.com/optimizing-lightning-component-inputs-and-outputs-in-flow-screens/">here</a>. We’re changing the behavior in 226 so that Next transitions will always recalculate the input attribute.</p>

Removed

Added

<p>One of Flow's biggest and most unique capabilities is its ability to let you set up processes where data travels from the output of one Flow element to the input of the next.</p><p>To use upstream data, the user clicks on a combobox in a Flow element property editor and selects from the available references.</p><p>For some kinds of data, these references are created automatically. For other kinds, you have to do it manually. There's a third bucket of kinds of data that give you the choice to do it manually or have it created automatically. <a href="https://unofficialsf.com/optimizing-lightning-component-inputs-and-outputs-in-flow-screens/">More detail is available here.</a></p><p>As of Spring '20, automatic references are generated for all kinds of Flow data except for:</p><ul><li>Subflow outputs (coming in Summer '20)</li><li>Loop index (the reference to the current member of a collection in a loop, coming in Summer '20)</li><li>Pause element</li></ul><h3>Automatic Field Discovery</h3><p>Automatic Field Discovery causes a Get Records to automatically pull in the necessary field values. You no longer have to manually choose them. </p><h3>Considerations When Choosing Automatic Vs. Manual</h3><p>The future is Automatic. Use it when you can. It's faster and easier.</p><p>When setting up Conditional Field Visibility relationships between fields, if the condition depends on the value of a screen component, make sure to use Automatic output handling. That's because the manual variables don't get updated until you transition to the next screen.</p><p>Currently, if you use Automatic Output Handling with a screen component attribute that you're passing an input too, Flow will remember the most recent value for that attribute. If you Previous to a point prior to the screen and then return to the screen it will not update to a new value. This is discussed more <a href="https://unofficialsf.com/optimizing-lightning-component-inputs-and-outputs-in-flow-screens/">here</a>. We're changing the behavior in 226 so that Next transitions will always recalculate the input attribute.~~</p><p>~~ </p>

<p>One of Flow’s biggest and most unique capabilities is its ability to let you set up processes where data travels from the output of one Flow element to the input of the next.</p><p>To use upstream data, the user clicks on a combobox in a Flow element property editor and selects from the available references.</p><p>For some kinds of data, these references are created automatically. For other kinds, you have to do it manually. There’s a third bucket of kinds of data that give you the choice to do it manually or have it created automatically. <a href="https://unofficialsf.com/optimizing-lightning-component-inputs-and-outputs-in-flow-screens/">More detail is available here.</a></p><p>As of Spring ’20, automatic references are generated for all kinds of Flow data except for:</p><ul><li>Subflow outputs (coming in Summer ’20)</li><li>Loop index (the reference to the current member of a collection in a loop, coming in Summer ’20)</li><li>Pause element</li></ul><h3>Automatic Field Discovery</h3><p>Automatic Field Discovery causes a Get Records to automatically pull in the necessary field values. You no longer have to manually choose them. </p><h3>Considerations When Choosing Automatic Vs. Manual</h3><p>The future is Automatic. Use it when you can. It’s faster and easier.</p><p>When setting up Conditional Field Visibility relationships between fields, if the condition depends on the value of a screen component, make sure to use Automatic output handling. That’s because the manual variables don’t get updated until you transition to the next screen.</p><p>Currently, if you use Automatic Output Handling with a screen component attribute that you’re passing an input too, Flow will remember the most recent value for that attribute. If you Previous to a point prior to the screen and then return to the screen it will not update to a new value. This is discussed more <a href="https://unofficialsf.com/optimizing-lightning-component-inputs-and-outputs-in-flow-screens/">here</a>. We’re changing the behavior in 226 so that Next transitions will always recalculate the input attribute.</p>