changed 4 years ago
Linked with GitHub

Dispatch Special Issues Investivation

Refs

Dispatch & Special Issues Investigation #14433

Problem

WTF special issues? Dispatch? aaaaa

Investigation

Q1: How do cases get to "ready for dispatch", for both AMA and Legacy cases

A: Legacy: The case has an unassigned Dispatch::Task type object. AMA do not go through Dispatch

Log

starting point: Dispatch ui: two possiblities - "cases ready for dispatch" is displayed on load, and "Establish claim" button to start one

pursuing the text - starts in client/app/containers/CaseWorker/HeaderMessage.jsx which displays it based on availableTasks & tasksRemaining
pulled into client/app/containers/CaseWorker/CasejkWorkerIndex.jsx
props pulled straight through
props loaded in app/views/dispatch/establish_claims/index.html.erb via tasks.any_assignable_to?(current_user)
unsurprisingly, that lives in app/models/dispatch/task.rb

important: Dispatch::Task is not a Task, it's its own thing
it does not appear in Task Trees

Q1b: Where do Dispatch::Tasks come from?

A: Nightly job queries VACOLS for cases in a couple states, and creates the EstablishClaim for an appeal

Log

Dispatch::Tasks live in app/models/dispatch/task.rb and this object serves as the superclass for the EstablishClaim object, which lives app/models/establish_claim.rb. Dispatch::Tasks also have a ClaimEstablishment object.

Dispatch::Task is largely concerned with managing the process in Caseflow, agnositc of the third party we're interfacing with.

EstablishClaim is more specifically concerned with interacting with VBMS (and BGS?)

Dispatch::Tasks belong to a LegacyAppeals, it looks like in the form of an EstablishClaim - when are these created?

CreateEstablishClaimTasksJob find/creates EstablishClaims for Legacy Appeals based on the queries:
AppealRepository.amc_full_grants - Full Grants
AppealRepository.remands_ready_for_claims_establishment - Partial Grants

Full Grants: app/repositories/appeal_repository.rb:amc_full_grants calls VACOLS::Case.amc_full_grants
Query VACOLS for VBMS cases in HIS status (BVA action completed) with allowed issue(s) and no remanded issue(s) since the param date

Partial Grants: app/repositories/appeal_repository.rb:remands_ready_for_claims_establishment calls VACOLS::CASE.remands_ready_for_claims_establishment
Query VACOLS for VBMS cases in Remand statue, sitting in location 97.

QTangent 1: Who uses Caseflow Dispatch

which user are we interrogating? those with role "Manage Claim Establishment", "Establish Claim"
(either)

A: anyone with some roles - back to the Q

QTangent 2: Whats a ClaimEstablishment?

Theory: represents the result of establishing the claim in VBMS?

Q2: Does Dispatch understand that the SpecialIssuesList object exists

A: No

Q3: How does Dispatch interact with LegacyAppeals on-object SpecialIssues

A: Special Issues, as defined by LegacyAppeal, can be updated on the associated LegacyAppeal

Log

You can hit put dispatch/establish-claim/update-appeal with a list of updated special issues in the params.
this invokes app/controllers/dispatch/establish_claims_controller.rb:update_appeal which passes the params that pass special_issues_params, which permits LegacyAppeal::SPECIAL_ISSUES.keys to be passed to an update call on the associated LegacyAppeal.

Q4: How does the SpecialIssues information leave caseflow, for AMA and for Legacy

A: AMA does not

A: Legacy affects the behavior in Caseflow (whether an extra step is required), but does not appear to affect the EndProduct itself

Log

Leave for where:

  • VACOLS
  • VBMS
VBMS

No. Some Special Issues cause routing to be handled distinctly, but no info goes out

VACOLS

Q5: Does Dispatch handle all Legacy appeals, or just a subset?

A: I don't think we can answer this.

Q6: Do dispatch users see the Special Issues page in production on AMA?

A: No AMA in Dispatch

Q7: Does Judge Checkout update VACOLS or LegacyAppeals with the Special Issues?

Question Storage

Helpful Additional Information

  • Why does Dispatch offer all Special Issues on AMA appeals?
  • When can we expect that a legacy case is "Done" in Caseflow, in the happy path?
Select a repo