![]() ![]() You'd just select that option to refresh inputs. You'd create a LWC for these types of inputs where you want to provide a default value that should respond to user-provided changes if they re-visit. Access the screen flow and provide a first and last name. I have a lot of different ScreenFlow preferences and supporting files from the different versions going back to v. ScreenFlow is the best application to capture screens and create video screencasts on Mac OS X. Could problem be related to recent MacOS update to 10.5.4 At one point not long ago I upgraded to the version 9 trial and then switched back which was a little messy if I recall. So what can you do to workaround the behavior of Flow?Ĭonsidering the behavior above, you're really left only with the option to leverage a LWC component for this specific use-case. ScreenFlow was working fine until very recently. Text fields in flow are optimized for a case where the value may need to be initialized to a default value, but once the user enters something else, the text field should not be reset. They provide a video highlighting this behavior that matches your question. ![]() Unofficialsf covers this behavior in the article covering optimizing lightning component inputs and outputs in flow screens. ![]() The options for revisited screen component values are available only for Lightning components. Click to upgrade your ScreenFlow license from a previous version, thereby enabling full access to the features of the current ScreenFlow version. Previously, a screen component always used the same values that the user entered. Changes elsewhere in the flow are incorporated in the refreshed values. When a user navigates to a previous screen, then proceeds forward to a screen that they visited already, the flow can refresh screen component values. This is somewhat called out in the Spring '21 release notes that released the LWC component feature: Run a Screen Flow from a Button in a Slack View (Beta) Run a Screen Flow from a Slack Shortcut (Beta) Use Flows with MuleSoft RPA. However, there's no such feature for standard flow inputs (as noted in my comment, display text will incorporate changes). They released the ability for LWC components to define whether inputs are refreshed or use values from when the user last visited. Telestream has issued ScreenFlow 10.0.9, a bug fix update for the screencast recording and video-editing app. I believe this is expected behavior and how Flow works. ![]()
0 Comments
Leave a Reply. |