462. EPMO Open Source Coordination Office Redaction File Detail Report

Produced by Araxis Merge on 6/22/2018 1:32:13 PM Central Daylight Time. See www.araxis.com for information about Merge. This report uses XHTML and CSS2, and is best viewed with a modern standards-compliant browser. For optimum results when printing this report, use landscape orientation and enable printing of background images and colours in your browser.

462.1 Files compared

#	Location	File	Last Modified
1			Fri Jun 22 18:32:12 2018 UTC
2	v1603_release_60.zip\Docs	180972 - VCCM_6_S#572280_Enhancement_ Change _Note Title_ to _Comment Title_.docx	Thu Jun 21 20:36:49 2018 UTC

462.2 Comparison summary

Description	Between Files 1 and 2
Description	Text Blocks	Lines
Unchanged	0	0
Changed	0	0
Inserted	1	143
Removed	0	0

462.3 Comparison options

Whitespace
Character case	Differences in character case are significant
Line endings	Differences in line endings (`CR` and `LF` characters) are ignored
CR/LF characters	Not shown in the comparison detail

462.4 Active regular expressions

No regular expressions were active.

462.5 Comparison detail

				1		180972: VC CM_6_S#572 280_Enhanc ement: Cha nge "Note Title" to "Comment T itle"
				2		Creation D ate: May 16, 2018 3 :26:11 PM (UTC-05:00 )Last Modi fied: May 21, 2018 8 :55:12 AM (UTC-05:00 )
				3
				4		State: App roved
				5		Originator : Pribyl, Brent (BA H)Owner:
				6		Type: Manu al
				7		Test Data: Unassigne d
				8
				9		Descriptio n: As a C RM User, I want CRM Notes to b e renamed "Comments" so that I can diffe rentiate b etween Pro gress Note s and CRM "Comments"
				10
				11		Replace "N ote" with "Comment" when refer encing a C RM Note. A pplies to:
				12		Progress N ote Form ( Interactio n and Requ est Notes Grid and a pplied CRM note text . See atta ched)
				13		Request Fo rm (Commen t Grid and applied C RM comment text)
				14		Rename sub -header la bel from " NOTES" to "COMMENTS" on Intera ction Form
				15
				16		Summary
				17
				18		Categories
				19		Function: Unassigned
				20		Test Phase : Develope r Test
				21
				22		Formal Rev iew
				23
				24
				25		General Co mments
				26
				27		Manual Ste ps
				28
				29
				30		Step 1
				31		Execution Step
				32
				33		Descriptio n*
				34		In the VCC M CRM appl ication, l og-in to t he system as an FTP CCA/TAN/Ph armacy/Pha rmacyTech test user
				35
				36		Expected R esults
				37		The user i s able to log-in as a FTP CCA/ TAN/Pharma cy/Pharmac yTech test user Comm ents
				38		Validates
				39
				40		Attachment s
				41
				42
				43		Step 2
				44		Execution Step
				45
				46		Descriptio n*
				47		Click on M VI Search from the U SD ribbon
				48
				49		Expected R esults
				50		The user i s directed to the MV I search p age
				51
				52		Comments
				53
				54
				55
				56		Validates
				57
				58		Attachment s
				59
				60
				61		Step 3
				62		Execution Step
				63
				64		Descriptio n*
				65		Search for a Veteran (by trait s or EDIPI )
				66
				67		Test Veter an Record: George VC CMAlberts 333624237, 10/18/197 4 Expected Results
				68		Veteran re cord is re trieved fr om MVI. Co mments
				69		Validates
				70
				71		Attachment s
				72
				73
				74		Step 4
				75		Execution Step
				76
				77		Descriptio n*
				78		Click on t he test fa cility for the Veter an record
				79
				80		Expected R esults
				81		An interac tion is ge nerated al ong with V eteran Inf o and Medi cal Charts tabs Comm ents
				82		Validates
				83
				84		Attachment s
				85
				86
				87		Step 5
				88		Execution Step
				89
				90		Descriptio n*
				91		User popul ates the r equired fi elds on th e Interact ion form a nd verifie s the "Not e" section name has changed to "Comments " and then adds a No te in the "Comments" section o f the Inte raction fo rm and mak es First C all Resolu tion = No and clicks Save
				92
				93		Expected R esults
				94		The reques t form is generated and "Comme nts" secti on is disp layed Comm ents
				95		Validates
				96
				97		Attachment s
				98
				99
				100		Step 6
				101		Execution Step
				102
				103
				104
				105		Descriptio n*
				106		On the Req uest form the user n avigates t o the "Com ments" sec tion (righ t below th e summary on the top of the re quest form ) and veri fies the I nteraction Comment i s listed i n the Comm ent grid a nd the fie ld is auto matically set to "In teraction Comment"
				107
				108		Expected R esults
				109		Interactio n Comment is listed in the gri d and it i s automati cally labe led as "In teraction Comment" C omments
				110		Validates
				111
				112		Attachment s
				113
				114
				115		Step 7
				116		Execution Step
				117
				118		Descriptio n*
				119		User appli es the int eraction c omment to the Progre ss Notes a nd then fi lls out th e required informati on for a w orkload/hi storical p rogress no te then sa ves the pr ogress not e to Vista
				120
				121		Expected R esults
				122		Progress N ote is sav ed to vist a Comments
				123		Validates
				124
				125		Attachment s
				126
				127
				128		Step 8
				129		Execution Step
				130
				131		Descriptio n*
				132		User opens up the Pr ogress Not e form and verifies that "Note " has chan ged to "Co mment" in the Intera ction and Request No tes grid
				133
				134		Expected R esults
				135		All instan ces of the word "Not e" have ch anged to " Comment" o n the Prog ress Notes form Comm ents
				136		Validates
				137
				138		Attachment s
				139
				140		Associated E-Signatu res
				141
				142
				143		SignedActi onSignerCo mmentAddit ional Info rmation