---
# System prepended metadata

title: APPELLANT POA

---

## APPELLANT POA 

[Dogfooding](https://deviq.com/practices/dogfooding) is to run through as many relevant user scenarios as possible. Ideally, the individual scenarios work perfectly as intended. The reason it's important that we go through this process is to ensure the feature is ready for production. The purpose of internal testing is to identify potential gaps or defects so that items can be resolved prior to release.



## Capturing deficiencies
It's best that we document any issues that we discover in as much of a uniform standard as possible so that upon later review, we're able to parse the individual instances as easily as possible for potential translation to tech debt/tech improvement Jira tickets. </br>
Here's the template that we've decided to use for this session.  So the goal is to fill it our for each individual discovery as throroughly as possible to capture the maximum amount of information on the particular issue:
1. Description of issue -> After intaking HLR or SC with Unrecognized Claimant with a POA, when we try to hit the Refresh button, POA information disappears and if we reload the page it reappears. 
2. Expected result (what **should've** occurred) -> POA information should have persist
3. Actual result (what **did** occur)
4. Steps to reproduce In decision review for HLR with veteran id: 345456783, it will load with POA information but if you hit refresh POA button, POA information is refreshed with message "Successfully refresh. No Power of attorney information was found at this time."
5. Severity (**low**: minimal/non-blocking, **medium**: potentially blocking, **high**: significant blocker/work stoppage)
5. Relevant screenshot(s)
    * screenshots are easy to add to hackMD, simply capture the shot you want on your machine, then drag and drop it into the doc like so:![](https://i.imgur.com/BMGvEp7.png)

Scenario 2
1. Description of issue -> When you click 'Refresh POA' with 'No known POA' displaying, and no POA information is found, the 'No Known POA' text changes to 'Power of Attorney (POA) data comes from VBMS'
2. Expected result (what **should've** occurred) -> The 'No Known POA' text should not change if no POA is found
3. Actual result (what **did** occur) - The text changes to 'Power of Attorney (POA) data comes from VBMS'
4. Steps to reproduce In decision review: Follow scenario 2
5. Severity (**low**: minimal/non-blocking, **medium**: potentially blocking, **high**: significant blocker/work stoppage)
5. Relevant screenshot(s)
## USERS
INTAKE CF_KIRK_283

| Tester   | Scenario | VET ID   |
|  Prajwal |     1    | 345456783|Fail 
|   Clay   |     2    | 700031878|Fail
|  Heather |     3    | 700019431|Pass
|  Craig   |     4    | 777220019|Pass
|    Faraz |     1    | 796121909|fail
|    Jay   |     3    | 700032022|Pass 

Other VetID that can be used: 517246262, 12345678, 700061867 (with POA+)

## Scenarios 

## 1 : Intake VHA HLR for Unrecognized Claimant with a POA

1. Login to the UAT env as CF_KIRK_283
2. Navigate to intake /intake 
3. Select Higher Level Review form 
4. Search for a Veteran ID: 
5. Fill out the form with all required information 
	Was this form submitted through VA.gov? 
-	No
	What is the receipt date of this form? 
-	08/22/2023
	What is the benefit type? 
-	Veterans Health Administration 
	Was an informal conference requested? 
-	No 
	Is the claimant someone other than the veteran? 
-	Yes
-	Claimant not listed
	Did the veteran check the Opt-In from SOC/SSOC box on the form? 
-	N/A
	Click the “Continue to next step” button  
6. From the “Relationship to Veteran” dropdown select “Child”
7. Fill out all required fields 
- First Name: Jane
- Last name: Doe 
- Do you have a VA form 21-22 for this claimant: Yes 
- Click the “Continue to next step” button 
8. In the “Representative’s name” dropdown, type in and select “John C YOO”
9.	Select “Continue to next step”
10.	Select “Confirm” on the modal
11.	Verify on the Add Issues Page there is a field for “Claimant’s POA” and there is a POA name in that field. 
12.	Verify the POA name is “John C Yoo”
13.	Click the “Add issues” button and fill out the modal that pops up 
-	Issue Category 
-	Clothing Allowance
-	Decision Date
-	08/23/2023
-   Issue Description 
-	Any text you’d like ex: “Test Scenario 1 [Tester name]” or "Damn I wish I was as cool as Faraz"
14.	Click the add issue button and establish the higher level review
15.	Select the Higher Level Review you performed an intake on (Should be at the top of the queue, you can double check with the Veteran ID you used)
16.	Verify you are brought to the details page and there is a section on the page called “Appellant’s Power of Attorney” 
17.	Verify the following is in this section 
-	Attorney: 
-	Address:
-	Email Address: 
18.	Click the “Refresh POA” button a message stating "Successfully refreshed" or "Information is current at this time. Please try again in {cooldown_period_remaining} minutes"

## 2  Intake VHA SC for Unrecognized Claimant with no POA

1. Login to the UAT env as CF_KIRK_283 
2.	Navigate to Navigate to https://appeals.cf.uat.ds.va.gov/intake
3.	Select a “Supplemental Claim VA Form 20-0995” from the dropdown 
4.	Search for a veteran ID from the table above 
5.	Fill out the form with all required information 
6.	Was this form submitted through VA.gov? 
-	No
	What is the receipt date of this form? 
-	08/22/2023
	What is the benefit type? 
-	Veterans Health Administration 
	Was an informal conference requested? 
-	No 
	Is the claimant someone other than the veteran? 
-	Yes
-	Claimant not listed
7.	Did the veteran check the Opt-In from SOC/SSOC box on the form? 
-	N/A
8.	Click the “Continue to next step” button  
9.	From the “Relationship to Veteran” dropdown select “Child”
10.	Fill out all required fields. 
11.	First Name: Jane
12.	Last name: Doe 
13.	Do you have a VA form 21-22 for this claimant: No
14.	Click the “Continue to next step” button 
15.	Verify the modal state that the intake does not have a Form 21-22
16.	Select “Confirm” on the review modal
17. Verify on the Add Issues Page there is a field for “Claimant’s POA” and there is “No known POA” written in the field
18. Click the “Add issues” button and fill out the modal that pops up 
	Issue Category 
-	Clothing Allowance
	Decision Date
-	08/23/2023
	Issue Description 
- Any text you’d like ex: “Test Scenario 2 [Tester name]” or "Why is Faraz so good at QA stuff"
19.	Click the add issue button and establish the supplemental claim
20.	Select the Supplemental Claim you performed an intake on (Should be at the top of the queue, you can double check with the Veteran ID you used)
21.	Verify you are brought to the details page and there is a section on the page called “Appellant’s Power of Attorney”
22.	Verify the section states “No known POA.”
23.	Click the “Refresh POA” button and verify no POA is added and a message stating "Successfully refreshed. No power of attorney information was found at this time."
	
## 3 Intake VHA SC with no recognized POA 
1.  Login to the UAT env as CF_KIRK_283 
2.	Navigate to Navigate to https://appeals.cf.uat.ds.va.gov/intake
3.	Select a “Supplemental Claim VA Form 20-0995” from the dropdown 
4.	Search for a veteran ID from the table above 
5.	Fill out the form with all required information 
6.	Was this form submitted through VA.gov? 
-	No
	What is the receipt date of this form? 
-	08/22/2023
	What is the benefit type? 
-	Veterans Health Administration 
	Was an informal conference requested? 
-	No 
	Is the claimant someone other than the veteran? 
-	No
7.	Did the veteran check the Opt-In from SOC/SSOC box on the form? 
-	N/A
8.	Click the “Continue to next step” button  
9.	Verify on the Add Issues Page there is a field for “Claimant’s POA” and there is “No known POA” written in the field
10. Click the “Add issues” button and fill out the modal that pops up 
	Issue Category 
-	Clothing Allowance
	Decision Date
-	08/23/2023
	Issue Description 
- Any text you’d like ex: “Test Scenario 2 [Tester name]” or "why is Faraz so cool"
11.	Click the add issue button and establish the supplemental claim
12.	Select the Supplemental Claim you performed an intake on (Should be at the top of the queue, you can double check with the Veteran ID you used)
13.	Verify you are brought to the details page and there is a section on the page called “Appellant’s Power of Attorney”
14.	Verify the section states “No known POA.”
15.	Click the “Refresh POA” button and verify no POA is added and a message stating "Successfully refreshed. No power of attorney information was found at this time."


## 4 Intake VHA HLR with a POA
1. Login to the UAT env as CF_KIRK_283
2. Navigate to intake /intake 
3. Select Higher Level Review form 
4. Search for a Veteran ID: 
5. Fill out the form with all required information 
	Was this form submitted through VA.gov? 
-	No
	What is the receipt date of this form? 
-	08/22/2023
	What is the benefit type? 
-	Veterans Health Administration 
	Was an informal conference requested? 
-	No 
	Is the claimant someone other than the veteran? 
-   No
	Did the veteran check the Opt-In from SOC/SSOC box on the form? 
-	N/A
6. Verify the Claimant's POA section has a POA present 
7. Click the “Add issues” button and fill out the modal that pops up 
	Issue Category 
-	Clothing Allowance
	Decision Date
-	08/23/2023
	Issue Description 
- Any text you’d like ex: “Test Scenario 4 [Tester name]” or "where did Faraz get such great fashion sense"
8.	Click the add issue button and establish the HLR
9.	Select the HLR you just performed an intake on from the Decision review queue
10.	Verify you are brought to the details page and there is a section on the page called “Appellant’s Power of Attorney” 
11.	Verify the following is in this section 
-	Attorney: 
-	Address:
-	Email Address: 
12. Click the “Refresh POA” button a message stating "Successfully refreshed" or "Information is current at this time. Please try again in {cooldown_period_remaining} minutes"
