Tech Discovery - How to release Toxic Exposure and new pdf version with a sticky feature flag

[RakshindaAslam]

Issue Description

Toxic Exposure and the new pdf version need to be released together and to smaller subset of Veterans. This ticket is to understand how a user is consistently sent down the path of the Toxic Exposure flow across multiple sessions till submission via the TE feature flag.

---

Tasks

• [x] Understand how flipper works - does it work for user accounts
• [x] If not, how can we make TE sticky for all facets of user journey from FrontEnd to Backup submission
• [x] Check with the Burial team

Acceptance Criteria

• [x] Does the flipper work with sticky path as currently implemented? - Yes
• [x] If not, document path for implementing sticky path

---

How to configure this issue

• [ ] Attached to a Milestone (when will this be completed?)
• [ ] Attached to an Epic (what body of work is this a part of?)
• [ ] Labeled with Team (product support, analytics-insights, operations, service-design, Console-Services, tools-fe)
• [ ] Labeled with Practice Area (backend, frontend, devops, design, research, product, ia, qa, analytics, contact center, research, accessibility, content)
• [ ] Labeled with Type (bug, request, discovery, documentation, etc.)

[aurora-a-k-a-lightning]

TL;DR: The Flipper feature flags are "sticky", but there may be some complications in the business logic and in the middle-tier "submit job" land that needs answering before we implement the new version of form 21-526EZ.

All is explained in this diagram:

Notes:

1. The Flipper feature flag does stick with the user until the end i.e. the flag is, indeed, "sticky".
2. We are assuming the Veteran needs to know which form we are filing for them on their behalf.
3. How do we relay this information to Veterans?
4. Veterans who are chosen with the Flipper flag - will they have to start over the form? Or will a simple pop-up suffice?
5. Veterans who are chosen with the Flipper flag/if we decide to roll back and are in "submit land" - will we have to send them a message/email telling them to start over? Or skip over that Veteran based on knowing which form they filled out, which we have no way of doing yet.
6. We need a way to capture which version of the form the Veteran was filling out.

We are closing this ticket for now until another team that is in the midst of this process rolls out to get more answers to these questions.