USDAForestService / NRM-Grants-Agreements

The focal point for an 18F/TTS collaboration with the USFS Natural Resource Manager (NRM)
Other
8 stars 2 forks source link

As someone creating a new proposal, I need any applicable data from workplan to be auto populated so that I can avoid data entry errors and the need to call other people to get the information. #185

Open neilmb opened 3 years ago

neilmb commented 3 years ago

Background

Current policy is that every grant/agreement needs to be linked to a "work plan" in the FS budgeting system called WorkPlan. It appears that this link is done by just including an ID number from the WorkPlan application when the agreement is created. There is some additional information with amounts and dates that is exchanged with WorkPlan but we don't know exactly how.

We should research the WorkPlan integration and figure out how we would handle it in our proposal creation flow.

We'll know we're done when...

Tasks

Related issues

MelissaBraxton commented 3 years ago

Two Qs re: workplan data:

neilmb commented 3 years ago

From Allison: Are we sure that Workplan is only one directional? Jamie mentioned something about data coming from NRM that ASC didn't like which made me think there might be a two way data flow (I also could have misunderstood!)

neilmb commented 3 years ago

Jay said today that info from NRM can overwrite what is in WorkPlan and upset the budget folks. We have also heard that info comes in from WorkPlan to start an agreement, so there is definitely a bi-directional flow of information here (but the two sides may be sequential).

tbaxter-18f commented 2 years ago

From what I've seen and heard, we should probably give this some priority. I believe (from usability research) it would likely pretty helpful to capture the workplan pretty early on, rather than late in the process. This would let us prepopulate a bunch of fields and reduce the creation burden, and I think it would be easier to capture errors/mismatches.

There's also a BIG question about whether or not that bidirectional flow of data is desirable, since the two systems are overriding one another. It may be prudent to make the flow one-way, have the fields read-only, and say "if you want to change, this do it over here".

I can also see some desire to move the workplan creation out of the legacy app, but that discussion hasn't happened yet, so I don't know.

Almost definitely blocked on #187