Data Flow Documentation/Diagrams

[dpgraham4401]

🚀 Feature Request

Is your feature request related to a problem? Please describe.

• Documentation (preferably with visual aids) showing the business logic (steps) Haztrak uses when interfacing with RCRAInfo.
• This is a very high level task, no code required, but would be good to do before we start diving into the meat of the project (interfacing with RCRAInfo)

Describe the solution you'd like

• the docs directory should contain a file/section on the workflow for actions that interface with RCRAInfo's web services.
• example off top of my head
  • Title: Editing a manifest through the post-submission correction processing
  1. User Select edit manifest
  2. haztrak checks that the current version is up-to-date with RCRAInfo
  3. if not, it ask the user if they'd like to update with the most recent info before editing
  4. if yes, haztrak pulls the most recent manifest from RCRAInfo and serves to user for editing

Describe alternatives you've considered

• we just wing it and don't plan this stuff out beforehand

[dpgraham4401]

closing this as this really belongs in the e-manifest documentation.