or
or
By clicking below, you agree to our terms of service.
New to HackMD? Sign up
Syntax | Example | Reference | |
---|---|---|---|
# Header | Header | 基本排版 | |
- Unordered List |
|
||
1. Ordered List |
|
||
- [ ] Todo List |
|
||
> Blockquote | Blockquote |
||
**Bold font** | Bold font | ||
*Italics font* | Italics font | ||
~~Strikethrough~~ | |||
19^th^ | 19th | ||
H~2~O | H2O | ||
++Inserted text++ | Inserted text | ||
==Marked text== | Marked text | ||
[link text](https:// "title") | Link | ||
 | Image | ||
`Code` | Code |
在筆記中貼入程式碼 | |
```javascript var i = 0; ``` |
|
||
:smile: | ![]() |
Emoji list | |
{%youtube youtube_id %} | Externals | ||
$L^aT_eX$ | LaTeX | ||
:::info This is a alert area. ::: |
This is a alert area. |
On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?
Please give us some advice and help us improve HackMD.
Do you want to remove this version name and description?
Syncing
xxxxxxxxxx
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 DispatchLog
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 onavailableTasks
&tasksRemaining
pulled into
client/app/containers/CaseWorker/CasejkWorkerIndex.jsx
props pulled straight through…
props loaded in
app/views/dispatch/establish_claims/index.html.erb
viatasks.any_assignable_to?(current_user)
unsurprisingly, that lives in
app/models/dispatch/task.rb
important:
Dispatch::Task
is not aTask
, it's its own thingit 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 inapp/models/dispatch/task.rb
and this object serves as the superclass for theEstablishClaim
object, which livesapp/models/establish_claim.rb
.Dispatch::Tasks
also have aClaimEstablishment
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 aLegacyAppeals
, it looks like in the form of anEstablishClaim
- when are these created?CreateEstablishClaimTasksJob
find/creates EstablishClaims for Legacy Appeals based on the queries:AppealRepository.amc_full_grants
- Full GrantsAppealRepository.remands_ready_for_claims_establishment
- Partial GrantsFull Grants:
app/repositories/appeal_repository.rb:amc_full_grants
callsVACOLS::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
callsVACOLS::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 passspecial_issues_params
, which permitsLegacyAppeal::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:
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