Update TIA Determinations with iterative review cycles

[TracyLinder]

Apply TIA iterative review features to TIA Determinations

[TracyLinder]

Q: Do users still want to see determinations as a drop-down menu item, or roll it into TIA?

• We can model this after TIA compliance that skips scoping and goes directly to submission

Customer Portal:

• No design changes

[TracyLinder]

Next Steps

• [x] @ChrispinP will add a comment with a general guideline of issue-sized tasks that need to be performed for this work
• [ ] @TracyLinder will assist with turning this into an epic and creating sub-issues based on 👆🏼

[ChrispinP]

Below are the Assessed Tasks needed to complete this project:

1. Gather Requirements (3) Work with Stakeholders to determine ID & Access Code standardization
2. Status Alignment (3) Map Determination Statuses to their desired Case and Submission Statuses. Confer with stakeholders.
3. TS Object & Import Prep (2) Knack object, field, and record preparations. Spreadsheet import prep
4. Import Cases into TS Object (3)
5. Submission Cycle Object & Import Prep (1)
6. Import 1st Submission Cycles for each Case (3)
7. Update Workflow Rules Where necessary, page rules, email rules, display rules, etc
8. Migrate Determination PDFs from Determination object to Submission Content object (5 or 8) Spike needed to assess level of effort for preferred/proposed migration solutions

A Go Live could occur before document migration as long as Cases & Cycles are imported and rules are in place. Downtime for TIA Determination service may be needed during this time.

[TracyLinder]

• Keep TDW naming standard
• For the access code, do whatever is easier for development. If it's no extra work, TDW would make the most sense.
• The final (approved) case status should be Review Complete instead of Pending Final Memo
• Be sure we require determination to be attached during application.

[TracyLinder]

Sprint planning - Tracy will create an issue for 1-6 (in Chrispin's comment above) and put on deck.

[TracyLinder]

TDS reprioritized their requests, bumping this down to their 2nd priority. This is going back to the backlog.