Compile Usecases for ReportStream engineer access

[brick-green]

Spike Goal

Intermediary Services relies on ReportStream (RS) for essential operations, and a thorough understanding of its use cases is crucial to ensure optimal functionality and identify areas for improvement. This spike will focus on researching and documenting all existing use cases involving RS as used by TI staff.

The output of this spike will be a compiled list of use cases with notes on their functionality and any known issues, which will inform future solution development efforts.

Acceptance Criteria:

• [ ] Research and Documentation: Document all current use cases for TI staff interactions with RS.
• [ ] Functional Assessment: Identify which use cases are fully functional and which are not.
• [ ] Insights and Next Steps: Provide insights on potential areas for improvement or solutions.

Expected Outcome:

• A clear, organized list of RS use cases for TI staff.
• High-level understanding of functionality issues in RS usage.
• Actionable insights for further development or bug fixes.

Estimated Timebox: (Specify duration, e.g., 3 days, 1 sprint)

[brick-green]

Some Ideas:

• As an intermediary eng I want to view the files sent to RS prior to any sender transformations so that I can confirm the data input
• As an intermediary eng I want to view files after data transforms have been made so that I can confirm the inputs and outputs for those transformations
• As a intermediary eng I want to view the files that were sent to receivers to confirm the output from reportstream after all transformations

[basiliskus]

@brick-green This may be nitpicky, but I'd specify we need a copy of those files. Instead of "view", we could word it as "download", "get a copy", or something else