Create a screen flow with some input fields on the Screen-1. Assign a value to a variable based on the inputs on screen-1. It could be any data type. Now navigate to the next Screen-2, and click "Previous" button to return to the first screen. Observe that the variable loses it's value assigned to it via the input screen. Although the input screen might still retain those values.
In another scenario, save values from input screen-1 into a variable and perform a DB operation to insert/update a record and display screen-2 with record values. Now navigate to the previous flow screen by clicking the "Previous" button. Although the DB operation is complete and the record is inserted/updated. Observe that the variable, which was assigned values from screen-1, goes NULL. This may cause problems if we use it in a decision element to check whether the record in the first step was already created/updated or not, while moving forward again.
This screen flow behavior is working as designed. To avoid this situation, follow one of the workarounds listed below:
000380596

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.