{"text_format":"2","workbook":"xls","n_sheets":5,"sheets":["Question Tracker","Test Cases","Data Requirements","Testers","User Roles and Login"],"not_rendered":{"charts":0,"images":10,"macros":0,"external_links":2,"defined_names":22,"comments":6,"pivot_tables":0},"unopened":[],"bounds":{"document_bytes":16777216,"sheet_cells":100000,"run_cost":"one","rows_first":2000,"rows_last":500,"rows_between":2000,"halvings":0,"cell_chars":16384,"cell_head_chars":4096},"cells_cut":0,"cells_raw":0,"read":"whole","date_system":"1900","formulas":"cached_only"}

{"sheet":"Question Tracker","index":0,"n_rows":95,"n_cols":12,"rows_kept":95,"cut":false,"hidden":false,"merged":[],"flags":["formulas_cached_only"]}
[]
[]
[]
[null,null,"Special Operations | Self Check | Federal Register Questions"]
[{"$nulls":8}," "," "]
[null,null,"ID#","Source","Submitted By","Date Received","Submission Type","Category","Submission","Response","Status","Comment/Resolution"]
[]
[null,null,1,"TALX","David C Fowler (Dave.Fowler@talx.com)","2010-11-08","Question","Employment Eligibility Results","Can U.S. workers share their E-Verify results? For example, can the worker share his or her E-Verify Self Check results with a current employer, prospective employer, or a pre-employment screener, and can the worker post his or her E-Verify Self Check results on a job board?\n","We do not intend for the E-Verify Self Check results to be shared with a US worker's employer, prospective employer,  a pre-employment screener, or posted on a job board.  An E-Verify Self Check result is not a USCIS issued credential and does not guarantee a US worker's right to work in this country. A US worker's status may change in between the time that he/she runs an E-Verify Self Check and when they are check through E-Verify by their employer. Although there is no legal impediment to workers sharing their results, the E-Verify Self Check result is intended to be informational to the US worker only as to their work authorization status when used, and not a guarantee of work authorized status when seeking employment.","New","Answered"]
["",0,2,"TALX","David C Fowler (Dave.Fowler@talx.com)","2010-11-08","Question","Identity Assurance","What controls are in place to prevent a worker from running a query on someone else?\n","There are two primary controls preventing an imposter from running a query on someone else. First, the imposter must pass an identity assurance quiz where he/she must prove their identity in order to be able to run a Self Check query. Second, once he/she has passed their identity assurance quiz, the name used to pass the ID assurance part of Self Check will be pre-populated into the name field for the Self Check query and will not be able to be changed by the user. Both of these controls are sufficient under OMB 04-04 guidance in establishing a system with Level 2 security features.","New","Answered"]
["",0,3,"TALX","David C Fowler (Dave.Fowler@talx.com)","2010-11-08","Question","Identity Assurance","What is the limit on the number of times a worker can take the identity quiz or run a query?\n"," A user may run a Self Check query a few times in a given time period in the course of checking their status and making certain any changes needed are reflected in the VIS. We do keep track of the number of times used to prevent fraud or hacking into the Self Check system. Releasing the specific number of times a user may attempt to take the identity quiz and run a self-check query, and the specific time frame, would reduce the effectiveness of this fraud prevention measure and therefore USCIS will not release this information to the general public.  ","New","Answered"]
[null,null,4,"TALX","David C Fowler (Dave.Fowler@talx.com)","2010-11-08","Question","Identity Assurance","What is the timeframe used to limit the number of times a worker can take the identity quiz or run a query?\n"," A user may run a Self Check query a few times in a given time period in the course of checking their status and making certain any changes needed are reflected in the VIS. We do keep track of the number of times used to prevent fraud or hacking into the Self Check system. Releasing the specific number of times a user may attempt to take the identity quiz and run a self-check query, and the specific time frame, would reduce the effectiveness of this fraud prevention measure and therefore USCIS will not release this information to the general public. ","New","Answered"]
["",0,5,"TALX","David C Fowler (Dave.Fowler@talx.com)","2010-11-08","Question","Program/Policy"," Does a worker need to or should a worker use Self Check to confirm that their immigration and/or SSA records have been properly updated?\n","A Self Check user may want to confirm that their immigration and/or SSA records have been updated after interaction with the E-Verify Self Check process. While an individual is free to run a Self Check on him/herself after their intiial query, they also should realize that the updating of SSA and/or immigration records is not instaneous and is subject to an adjudication process in some instances.","New","Answered"]
["",0,6,"TALX","David C Fowler (Dave.Fowler@talx.com)","2010-11-08","Question","Program/Policy","Does DHS anticipate that a worker will only run a query on themselves one time?","Our operating assumption is that a worker will usually run a query on themselves one time. However, E-Vefirfy Self Check does allow for the ability to query oneself more than once, as long as it is within the fraud boundaries set by the program.","New","Answered"]
["",0,7,"TALX","David C Fowler (Dave.Fowler@talx.com)","2010-11-08","Question","Identity Assurance","The 3rd party identity authentication service must be identified. Is this one of the three credit reporting bureaus?\n","DHS fails to see a reason for broadcasting the identity of third party verification service due to the fact that it believes that disclosure could lead to  possible fraud and security implications. However, the third party verification service will meet all applicable federal government privacy and security standards before it is made operational.","New","Answered"]
["",0,8,"TALX","David C Fowler (Dave.Fowler@talx.com)","2010-11-08","Question","Program/Policy","Why is Self Check limited to individuals over the age of 16?\n","For its initial implementation, E-Verify Self Check is limited to the work authorized population. In future implementations, DHS may decide to expand the reach of its program. The 16 year old age limitation is not arbitrary as it is, generally, the age that individuals are legally permitted to work. Additionally, most, if not all of those younger than 16 would not have a big enough identity \"footprint\" for an identity proofing quiz to be generated and completed prior to verifying their employment eligibility.","New","Answered"]
["",0,9,"TALX","David C Fowler (Dave.Fowler@talx.com)","2010-11-08","Question","Employment Eligibility Results","Why inform the worker that they would ‘likely’ be employment authorized rather that stating definitively?\n","The E-Verify Self Check service can only give the user an answer to their work authorization status at that moment. It cannot accurately predict an E-Verify result since a person's work authorization status may change between the time of the Self Check query and their employer's E-Verify query.","New","Answered"]
["",0,10,"TALX","David C Fowler (Dave.Fowler@talx.com)","2010-11-08","Question","Program/System Information","What features does E-Verify envision being added to Self Check in the future, provided the program is successful?\n","Future features being considered by DHS to add to the E-Verify Self Check service include ways to give greater information and clarity about the E-verify process to the general public and looking at ways for the Self Check user to better understand how to protect their information and privacy throughout the E-Verify process.","New","Answered"]
[null,null,11,"TALX","David C Fowler (Dave.Fowler@talx.com)","2010-11-08","Question","Privacy"," Why is the information a worker submits to Self Check not considered confidential since the information could be used for identity theft?\n","The information submitted to Self Check is considered confidential and is protected according to Federal Privacy and IT Security standards, as well as the Verification Information System Systems of Records Notice. We will update our documentation to reflect this fact.","New","Change made"]
["",0,12,"TALX","David C Fowler (Dave.Fowler@talx.com)","2010-11-08","Question","Program/Policy","Why does E-Verify not intend to publish statistics on Self Check since these statistics could be used to determine the benefit and cost effectiveness of the program? USCIS states that information about each Self Check query will be retained for statistical purposes. Why not share the statistical results with the public that is paying for the service?\n","Once launched, E-Verify Self Check will be evaluated and judged in conjunction with its effect on the E-Verify service itself. E-Verify Self Check evaluations will be shared with the general public as part of reporting on E-Verify service effects.","New","Change made"]
["",0,13,"TALX","David C Fowler (Dave.Fowler@talx.com)","2010-11-08","Question","Program/Policy","Why would E-Verify allow the 3rd party identity authentication service to market other services on its website as part of the Self Check program?\n","E-Verify Self Check will not allow the third party authentication service to market other services on its website as part of the Self Check program. DHS has ownership of the screen and display of any and all information, and the third party identity verification service will not control nor/market and information through the Self Check website. Documentation has been changed accordingly.","New","Change made"]
[null,null,14,"TALX","David C Fowler (Dave.Fowler@talx.com)","2010-11-08","Suggestion","Program/Policy","The 3rd party identity authentication service website should be limited to only performing the function required by Self Check and should not be used to market other services to U.S. workers. Self Check should be a marketing tool for the 3rd party identity authentication service.\n","E-Verify Self Check will not allow the third party authentication service to market other services on its website as part of the Self Check program. DHS has ownership of the screen and display of any and all information, and the third party identity verification service will not control nor/market any information through the SElf Check website. Documentation changed accordingly.","New","Change made"]
["",0,15,"TALX","David C Fowler (Dave.Fowler@talx.com)","2010-11-08","Question","Privacy","How can USCIS say that the information collected by the 3rd party identity authentication service will only be retained for 1 year when USCIS also states that it has no control over the 3rd party?\n","USCIS controls the actions of the third party identity authentication service through a legal agreement that established the government's contracting for that service. The third party service is limited by both contract and the Fair Credit Reporting Act to a 1 year retention period and limited in its use of the information to solely fraud monitoring.","New","Answered"]
["",0,16,"TALX","David C Fowler (Dave.Fowler@talx.com)","2010-11-08","Question","Privacy","Is the Federal Credit Reporting Act (FCRA) one year data retention a minimum or maximum requirement?\n","The FCRA one year retention period for data is a maximum requirement.","New","Answered"]
[null,null,17,"TALX","David C Fowler (Dave.Fowler@talx.com)","2010-11-08","Question","Program/Policy","Why won’t USCIS at least assume responsibility for the accuracy of information provided by Self Check that originates with USCIS?\n","USCIS assumes responsibility for the accuracy of the information provided by USCIS to the extent practicable under law.","New","Answered"]
["",0,18,"TALX","David C Fowler (Dave.Fowler@talx.com)","2010-11-08","Suggestion","Program/System Information","There should be a published service level for the Self Check website.\n","Unsure of the comment.  The Terms of Use for use of Self Check are going to be published on the Self Check site.","New","Answered"]
["",0,19,"TALX","David C Fowler (Dave.Fowler@talx.com)","2010-11-08","Suggestion","Program/Policy","Since USCIS selected the 3rd party identity authentication service to be part of Self Check, which is a government system, USCIS must accept some responsibility for the information a worker is required to enter into such 3rd party website in order to access Self Check.\n","USCIS assumes responsibility for the protection of all data provided by the Self Check user in the course of the process. USCIS will be publishing a privacy impact assessment and system of record notices detailing the privacy protections of the data provided and what if any data the government retains. ","New","Answered"]
["",0,20,"TALX","David C Fowler (Dave.Fowler@talx.com)","2010-11-08","Suggestion","Program/Policy","The user’s liability must relate to ‘intentionally’ causing technical disruption. A user cannot be held liable for unintentional consequences of attempting to use the Self Check program in the prescribed manner.\n","USCIS agrees with this comment and will make the necessary changes to the Terms of use.","New","Change made"]
["",0,21,"TALX","David C Fowler (Dave.Fowler@talx.com)","2010-11-08","Question","Privacy","USCIS is committed to maintaining privacy of PII, yet USCIS does not accept any liability for requiring a user to provide PII to a 3rd party identity authentication service selected by USCIS and incorporated as a required component of Self Check. Also, USCIS considers all information submitted through Self Check to be ‘unconfidential’ and USCIS may disclose, distribute, modify, or reproduce the information a user provides to any other government agency. How is that maintaining privacy of a user’s information?\n","We agree with the comment and we will make the necessary changes to the Terms of Use to qualify that the information provided will be held as confidential and only disclosed to government agencies with the legal authority to request the data.","New","Change made"]
[null,null,22,"TALX","David C Fowler (Dave.Fowler@talx.com)","2010-11-08","Question","Identity Assurance","What data is exchanged between USCIS and the 3rd party identity authentication service to connect the results of the identity verification to the user’s Self Check session?\n","The Self Check session will create a unique user id that is transferred between the Self Check application and the third party authentication service, thereby tying the Self Check session to the identity verification transaction.","New","Answered"]
["","",23,"TALX","David C Fowler (Dave.Fowler@talx.com)","2010-11-08","Question","Privacy","On page 10 of the September 2010 proposed website content it states that the 3rd party will retain personal information for 1 year, yet on page 17 of the same document is states that the 3rd party will delete the information when the questions are answered successfully. Which is it?\n","The 3rd party will retain the data for one year. The new website content will reflect that change.","New","Change made"]
["",0,24,"TALX","David C Fowler (Dave.Fowler@talx.com)","2010-11-08","Suggestion","Self Check System","Fix the software to be smart enough to deal with Alien numbers of less than 9 digits.\n","The Self Check system leverages an existing web services interface with the Verification Information System. Future changes to  VIS will address this issue.","New","Answered"]
["",0,25,"AILA","AILA","2010-11-29","Suggestion","Policy","Prevent use of Self Check as a pre-screening tool. Upon roll-out of the Self Check service, contemporaneously amend the E-Verify MOU to include a specific provision prohibiting employers from requiring Self Check as a condition for hire or using it to perform any type of pre-employment screening. Establish sanctions to prevent the pre-screening of applicants by employers who are not enrolled in E-Verify and other third parties. Coordinate enforcement measures with the Department of Justice Office of Special Counsel. Publish advisories and make other efforts to educate employers and third parties that the Self Check service may only be used by individuals to verify their own E-Verify records and not as a tool for employers to pre-screen job applicants.","USCIS sees misuse of Self Check by employers attempting to pre-screen applicants as one of the major issues we will have to be vigilant in addressing.  Guidance on the Self Check website will specifically address this issue and amending existing E-Verify MOUs as the commenter suggested is something we will pursue in the near future. We are working with the DOJ Office of Special Counsel on how the use of Self Check can be monitored for pre-screening to ensure the protection of the US worker. Lastly, our outreach and education efforts will concentrate on worker's rights and the fact that the use of Self Check is not for employers and they should not be asking or requiring applicants to use Self Check.","New","Answered"]
[null,null,"TBD","AILA","AILA","2010-11-29","Suggestion","Policy","Protect Privacy. The proposed on-line identification mechanism does not require any biometrics or other strict access protocols for secure identification of the individual. We are also concerned about the potential sharing of personal data and information regarding the use of the Self Check mechanism among government agencies without any clearly defined limits in the proposal. We appreciate that USCIS recognizes data privacy issues but we strongly urge the agency to review and augment the proposed access protocols so that identity thieves cannot mine data from public information sources and then use that data to gain access to Self Check data. Without strict access protocols, rather than protecting\nindividuals from identity theft, Self Check would actually be a tool that identity thieves could use to verify that their victims’ stolen data will successfully pass through the E-Verify system.","DHS has designed the Self Check application to guard against the use of Self Check as a tool for identity thieves to validate personal data. The use of knowledge based identity verification procedures will allow us to know that a person \"is who they say the are\" before we allow them to determine if they are work authorized in the United States. This  level of identity authentication is in line with the secure access protocols for a Level 2 system as defined in OMB M 04-04 and NIST guidelines. We believe that the level of authentication incorporated into Self Check is sufficient and addresses the concerns of the comment. We plan to actively monitor the use of Self Check during its initial implementation to guard against fraud and misuse and we will adjust the security protocls accordingly during its initial implementation. Furthermore, there is no \"Self Check data\" that an identity thief could obtain as no new personally identifiable information is shown to the user via the application. Also, Self Check will not share data with any government agency unless their is a legal obligation to do so under the E-Verify authorizing statute or other applicable laws. There are not any data sharing MOUs that currently exist to which the sharing of E-Verify Self Check data is subject to.","New","Answered"]
["",0,"TBD","AILA","AILA","2010-11-29","Suggestion","Policy","Provide Options for Self Check Access to Individuals Without Credit Histories. Our final concern is that because the proposed access protocol for Self Check relies entirely on background checks, it will render Self Check unavailable to populations of foreign nationals who have only recently arrived in the United States and therefore do not have a credit history. The individuals who are most likely to have complicated immigration situations—and corresponding errors in their E-Verify records—are refugees, asylees, and individuals with temporary protected status (TPS). Due to their recent arrival in the United States, these individuals will often lack the financial and credit history necessary to generate the questions for access into the Self Check system. Due to their often complex work authorization documentation, it is exactly these individuals who are likely to have the greatest need to update or correct their EVerify records through Self Check. The proposed system of access based on credit history will leave those who are most likely to need the Self Check mechanism the least able to access it. We urge the agency to consider alternate means of identity verification to access the Self Check system, such as presentation of identity documents at an InfoPass appointment or Application Support Center and then conducting the Self Check query at that government office. Again, because asylees, refugees and TPS holders are among those who most need the opportunity to correct errors in the E-Verify system, we urge the agency to provide meaningful mechanisms\nthrough which these vulnerable populations can avail themselves of the benefit of the Self Check process.","USCIS recognizes that the workers who could see the most benefit from using the Self Check service may be those who have the lightest identity \"footprint\" because they will have arrived in the United States very recently. We are looking into ways to increase the availablility of the service to those persons, including finding additional databases to utilize during the identity proofing process. We thank you for your suggestion for addressing this concern by making visits to field offices or application support centers and will take the development of these processes in the future into consideration.                                                                                                                                                                    ","New","Answered"]
["",0,"TBD","NILC","NILC","2010-11-30","Suggestion","Policy","E-Verify “Self-Check” should guarantee that no data from Self-Check will be shared with other components within the Department of Homeland Security (DHS) or the Social Security Administration (SSA). Without this guarantee, the quantity and quality of information that DHS receives through Self-Check will be highly limited.  Individuals unsure of their employment eligibility or immigration status will be afraid to use Self-Check, essentially vitiating the purpose of the program.  Self-Check’s design enables a worker who is unsure of their employment eligibility to obtain vital information and expedite his entry into the workforce through this program. However, if a worker fears inputting their information into Self-Check, it will significantly decrease the utility of the information sought through this program.","E-Verify Self Check is subject to the legal obligations for data sharing that are set out in the E-Verify (Basic Pilot) authorizing statute. The sharing of E-Verify Self Check information is not subject to any data sharing MOUs that the E-Verify program has entered into with the Department of Justice Office of Special Counsel and DHS Immigration and Customs Enforcement. DHS believes it is important that individuals feel comfortable in their use of the E-Verify Self Check and take advantage of this important service.","New","Answered"]
["",0,"TBD","NILC","NILC","2010-11-30","Suggestion","Policy","USCIS should develop an appeals process for workers wrongfully denied, rejected, or miscategorized by Self-Check and a complaint process for workers subject to employer misuse of E-Verify. Self-Check or E-Verify may be abused by employers who choose to use it as part of the hiring process, use it on existing employees for employers that are not Federal Contractors, or who engage in any other practice that violates the terms of the MOU.  Additionally, protections should be in place to ensure employers that are not signatories to an MOU do not use Self-Check in place of signing up for E-Verify, further abusing the Self-Check program. \n\nNILC recommends that DHS and SSA develop procedures to prevent employers from using Self-Check on behalf of workers.  Furthermore, NILC recommends that the agencies develop a procedure to redress individual workers harmed by employer misuse of the E-Verify and/or Self-Check programs.  This procedure should entail a petition and appeals process, and provide a means to reach a satisfactory resolution for individual workers.","As Self Check is providing no benefit or credential to the user, and users cannot be denied a job based on a failure to successfully complete the Self Check process, there is no immediate need to develop an appeals process. We will continue to evaluate the possible utility of an appeals process in the future. Additionally, guidance on the Self Check website will inform visitors that the use of Self Check does not infer the granting of a beneft or credential. DHS will continue to stress the use, benefits, and limitations of E-Verify Self Check in education and outreach materials provided to the public during the time leading up to and and after its implementation.","New"]
["",0,"TBD","NILC","NILC","2010-11-30","Suggestion","Policy","As a matter of policy, USCIS should not follow-up with individuals who fail to correct their information under Self-Check. NILC recommends that SSA and DHS both issue guidance committing not to track an individual in this situation.  Additionally, to avoid future privacy infringements, NILC recommends that SSA and DHS destroy the information transmitted from the individual to the agency as part of Self-Check. ","USCIS has no authority to follow up with individuals who fail to correct their information upon receiving a Self Check mismatch, just as we have no authority to follow up with those workers who fail to contest an E-Verify TNC. We will ensure that all outreach and educational materials address this fact. Additionally, the government will never know anything about the identity proofing portion of Self Check other than the fact that an identity proofing transaction occurred and whether it was successfully completed. We will not retain any personally identifiable information from the transaction unless the user chooses to confirm his/her work authorization status after a successful identity verification. However, we are unable destroy all of the information used to check DHS and SSA records due to data retention requirements and the way the Verification Information System (VIS), which is the system used by E-Verify and will be used by Self Check, is currently configured.  We believe that configuring VIS to destroy this information would severely impact the reporting capabilities for both E-Verify and Self Check such that we would be greatly limited in our ability to detect fraud, system misuse, and discriminatory practices. We are working with NARA to establish a seperate record retention schedule for E-Verify Self Check query information that would limit our retention to 1 year for the above stated purposes.","New","Answered"]
[null,null,"TBD","NILC","NILC","2010-11-30","Suggestion","Policy","Self-Check is not sufficiently available to individuals who read languages other than English or Spanish. NILC recommends that DHS provides Self-Check in languages including, but not limited to, Mandarin (Chinese), Carolinian, Chamorro, Japanese, Korean, Urdu, Punjabi, Gujarati and Tagalog.   Since the language-needs cannot likely be provided at the outset, a phased approach may be beneficial.","USCIS is taking a phased-in approach to the implementation of E-Verify Self Check to provide for adequate feedback based on the live system before making it available to all U.S. workers. Given this approach and the rationale behind it, Self Check will initially be available only in English, with mismatch guidance also available in Spanish. We plan to make the service available in multiple languages in future releases.","New","Answered"]
["",0,"TBD","NILC","NILC","2010-11-30","Suggestion","Policy","Currently, there is no schedule posted that discusses how and when Self-Check will become active.  A proposed or target schedule would provide individuals and others advance notice of when this feature is to roll-out  This is particularly beneficial to advocacy organizations such as NILC, whom the public will look to for information about Self-Check.  NILC recommends that a schedule be posted by DHS on a publicly-accessible section of the DHS website.","USCIS is currently pushing toward a March roll-out of the E-Verify Self Check service. The exact date, scope, and locations of the initial release are not yet solidified. USCIS will make this information available as the anticipated roll out date approaches. We look forward to work with NILC and others in the stakeholder and advocacy community to ensure a successful implementation of this important service for US workers.","New","Answered"]
[null,null,"TBD"]
["",0,"TBD"]
[null,null,"TBD"]
["",0,"TBD"]
[null,null,"TBD"]
["",0,"TBD"]
[null,null,"TBD"]
["",0,"TBD"]
[null,null,"TBD"]
["",0,"TBD"]
[null,null,"TBD"]
[null,null,"TBD"]
["",0,"TBD"]
[null,null,"TBD"]
["",0,"TBD"]
[null,null,"TBD"]
["",0,"TBD"]
["",0,"TBD"]
[null,null,"TBD"]
["",0,"TBD"]
["",0,"TBD"]
[null,null,"TBD"]
["",0,"TBD"]
[null,null,"TBD"]
["",0,"TBD"]
[null,null,"TBD"]
["",0,"TBD"]
["",0,"TBD"]
["",0,"TBD"]
[null,null,"TBD"]
["",0,"TBD"]
[null,null,"TBD"]
["",0]
["",0]
["",0]
[]
["",0]
["",0]
[]
["",0]
["",0]
[]
["",0]
["",0]
["",0]
[]
["",0]
["",0]
["",0]
[]
["",0]
[]
[]
["",0]
[]
["",0]

{"sheet":"Test Cases","index":1,"n_rows":65,"n_cols":14,"rows_kept":65,"cut":false,"hidden":true,"merged":[],"flags":["formulas_cached_only"]}
["","",null,null,""]
["","",null,null,""]
["","",null,null,""]
["","",null,null,"","USCIS Special Operations | JobLock UAT | Test Cases",{"$nulls":4},"2010-12-09T13:29:57.770",null,null,"Last updated: 12/09/2010"]
["","",null,null,""]
["","",null,null,"","#","Case Name","Case Description","Precondition","Steps","Expected Outcome","Pass/Fail","Defect #s","Comments"]
["","",null,null,"","TC1","Assign JULS Case to MPA","Test that a new JULS Case can be located by a Supervisor and assigned to an MPA","Unassigned JULS case","* Log in as a Supervisor\n* Find JULS Case in unassigned queue\n* Open Case\n* Assign to MPA","Assigned JULS case","","",""]
["","",null,null,"","TC2","Approve a new JULS Case","Test than an MPA can locate a JULS Case, approve the JobLock application (lock the SSN), and receive the correct notification email","Assigned JULS case","* Log in as an MPA\n* Find JULS Case in assigned queue\n* Open JULS Case\n* Choose resolution to Lock SSN\n* Add comments\n* Receive correct email notice","* Approved Application / Locked SSN\n* Comments added\n* Email notice of successful application received","","",""]
["","",null,null,"","TC3","Reject a new JULS Case (FTC complaint not found)","Test that an MPA can locate a JULS Case, reject the JobLock application (for the reason that no matching FTC complaint was found), and receive the correct notification email","Assigned JULS case","* Log in as an MPA\n* Find JULS Case in assigned queue\n* Open JULS Case\n* Select resolution to Reject Case for \"Application not Found in FTC\"\n* Add comments\n* Receive correct email notice","* Rejected Application\n* Data purged\n* Comments added\n* Email notice of rejected application received","","",""]
["","",null,null,"","TC4","Reject a new JULS Case (Complaint does not match App)","Test that an MPA can locate a JULS Case, reject the JobLock application (for the reason that the FTC complaint data does not match the JULS Case), and receive the correct notification email","Assigned JULS case","* Log in as an MPA\n* Find JULS Case in assigned queue\n* Open JULS Case\n* Select resolution to Reject Case for \"FTC Does not Match Application\"\n* Add comments\n* Receive correct email notice","* Rejected Application\n* Data purged\n* Comments added\n* Email notice of rejected application received","","",""]
["","",null,null,"","TC5","Set a new JULS Case to Pending (FTC Complaint Verification)","Test that an MPA can locate a JULS Case, place it into a Pending state (for the reason that the FTC Complaint has not been Verified), and receive the correct notification email","Assigned JULS case","* Log in as an MPA\n* Find JULS Case in assigned queue\n* Open JULS Case\n* Select resolution to set Case to Pending for \"FTC Not Validated\"\n* Add comments\n* Receive correct email notice","* Pending Application\n* Comments added\n* Email notice of pending application received","","",""]
["","",null,null,"","TC6","System changes Pending JULS Case to unassigned","Test that the system will move Pending JULS Cases into the unassigned queue after 15 days have elapsed","Pending JULS case not in a workflow queue","* System determines that 15 days have elapsed\n* System moves the Pending Case into the unassigned queue","Unassigned JULS case","","","Automated system action"]
["","",null,null,"","TC7","Assign JULS Case to MPA (after Pending timer has expired)","Test that a JULS Case can be located by a Supervisor (after the Pending timer expires) and assigned to an MPA","Unassigned JULS case","* Log in as a Supervisor\n* Find JULS Case in unassigned queue\n* Open Case\n* Assign to MPA","Assigned JULS case","","",""]
["","",null,null,"","TC8","Assign JULS Case to MPA (before Pending timer has expired)","Test that a JULS Case can be located by a Supervisor (before the Pending timer expires) and assigned to an MPA","Pending JULS case not in a workflow queue","* Log in as a Supervisor\n* Search for JULS Case\n* Open Case\n* Assign to MPA","Assigned JULS case","","",""]
["","",null,null,"","TC9","Approve a JULS Case after it has been Pending","Test than an MPA can locate a JULS Case (after it has been Pending and then assigned back out), approve the JobLock application (lock the SSN), and receive the correct notification email","Assigned JULS case","* Log in as an MPA\n* Find JULS Case in assigned queue\n* Open JULS Case\n* Select resolution to Lock SSN\n* Add comments\n* Receive correct email notice","* Approved Application / Locked SSN\n* Comments added\n* Email notice of successful application received","","",""]
["","",null,null,"","TC10","Reject a JULS Case after it has been Pending (FTC complaint not found)","Test that an MPA can locate a JULS Case (after it has been Pending and then assigned back out), reject the JobLock application (for the reason that no matching FTC complaint was found), and receive the correct notification email","Assigned JULS case","* Log in as an MPA\n* Find JULS Case in assigned queue\n* Open JULS Case\n* Select resolution to Reject Case for \"Application not Found in FTC\"\n* Add comments\n* Receive correct email notice","* Rejected Application\n* Data purged\n* Comments added\n* Email notice of rejected application received","","",""]
["","",null,null,"","TC11","Reject a JULS Case after it has been Pending (Complaint does not match App)","Test that an MPA can locate a JULS Case (after it has been Pending and then assigned back out), reject the JobLock application (for the reason that the FTC complaint data does not match the JULS Case), and receive the correct notification email","Assigned JULS case","* Log in as an MPA\n* Find JULS Case in assigned queue\n* Open JULS Case\n* Select resolution to Reject Case for \"FTC Does not Match Application\"\n* Add comments\n* Receive correct email notice","* Rejected Application\n* Data purged\n* Comments added\n* Email notice of rejected application received","","",""]
["","",null,null,"","TC12","Reject a JULS Case after it has been Pending (FTC Complaint Verified)","Test that an MPA can locate a JULS Case (after it has been Pending and then assigned back out), reject the JobLock application (for the reason that the FTC complaint was not verified), and receive the correct notification email","Assigned JULS case","* Log in as an MPA\n* Find JULS Case in assigned queue\n* Open JULS Case\n* Select resolution to Reject Case  for \"FTC Not Validated\"\n* Add comments\n* Receive correct email notice","* Rejected Application\n* Data purged\n* Comments added\n* Email notice of rejected application received","","",""]
["","",null,null,"","TC13","Reassign a JULS Case","Test that a Supervisor can locate a JULS Case currently assigned to an MPA and can assign to a different MPA","Assigned JULS case","* Log in as a Supervisor\n* Search for JULS Case\n* Open Case\n* Assign to different MPA\n* Add comments","* Assigned JULS case\n* Comments added","","",""]
["","",null,null,"","TC14","Reassign a JULS Case after is has been Pending","Test that a Supervisor can locate a JULS Case currently assigned to an MPA and can assign to a different MPA, after the Case has been Pending","Assigned JULS case","* Log in as a Supervisor\n* Search for JULS Case\n* Open Case\n* Assign to different MPA\n* Add comments","* Assigned JULS case\n* Comments added","","",""]
["","",null,null,"","TC15","Unlock a Case in JULS after Challenge Question answered correctly","Test than an MPA can locate a locked SSN in JULS, unlock it in the situation that a Challenge Question has been answered correctly, and receive the correct notification email","Locked SSN","* Log in as an MPA\n* Find JULS Case\n* Open Case\n* Select resolution to Unlock \n* Add comments\n* Receive correct email notice","* Unlocked SSN / Closed JULS case\n* Comments added\n* Email notice of unlocked SSN received","","","Same as TC18? (successful ASC visit)"]
["","",null,null,"","TC16","Respond to Challenge Questions all failed (without a TNC)","Test that an MPA can locate a locked SSN in JULS, respond to a failed unlock attempt (where all Challenge Questions were answered incorrectly) outside of the TNC process, and receive the correct notification email with ASC referral instructions","Locked SSN","* Log in as an MPA\n* Find JULS Case\n* Open Case\n* Select \"Challenge Questions Failed\" option to send email to participant\n* Add comments\n* Receive correct email notice","* Locked SSN\n* Comments added\n* Email notice of failed unlock attempt received (ASC referral instructions)","",""]
["","",null,null,"","TC17","Purge JULS Case data after a successful unlock","Test that an MPA can purge a JobLock participant's personal information from JULS after a successful unlock request","Unlocked SSN / Closed JULS case","* Select to \"Purge\" Data\n* Add comments","* Data purged\n* Comments added","",""]
["","",null,null,"","TC18","Unlock a Case in JULS after successful ASC visit email","Test that an MPA can locate a locked SSN in JULS, unlock it in response to email notification of a successful ASC visit (where the employee's identity was authenticated), and receive the correct notification email","Locked SSN","* Log in as an MPA\n* Find JULS Case\n* Open Case\n* Select resolution to Unlock \n* Add comments\n* Receive correct email notice","* Unlocked SSN / Closed JULS case\n* Comments added\n* Email notice of unlocked SSN received","","","Same as TC15? (Ch Q's correct)"]
["","",null,null,"","TC19","Respond to unsuccessful ASC visit email","Test that an MPA can locate a locked SSN in JULS and respond to email notification of an unsuccessful ASC visit (where the employee visited an ASC but did not authenticate his/her identity appropriately)","Locked SSN","* Log in as an MPA\n* Find JULS Case\n* Open Case\n* Select resolution to record unsuccessful ASC visit\n* Add comments","* Locked SSN\n* Comments added","","",""]
["","",null,null,"","TC20","Clear a new JobLock TNC, keeping the SSN locked","Test that an MPA can open a JobLock TNC and clear it, using the option that the SSN will remain locked","New JobLock TNC","* Open SVS Case (using provided Test Data)\n* Select resolution: JobLock Authorized - SSN Remains Locked\n* Submit\n* Receive correct email notice","* Resolved TNC: JobLock Authorized - SSN Remains Locked\n* Email notice of successful SSN usage received","","",""]
["","",null,null,"","TC21","Clear a new JobLock TNC, unlocking the SSN","Test that an MPA can open a JobLock TNC and clear it, using the option that the SSN will be unlocked","New JobLock TNC","* Open SVS Case (using provided Test Data)\n* Select resolution: JobLock Authorized - Unlock SSN\n* Submit","* Resolved TNC: JobLock Authorized - SSN Unlocked","","",""]
["","",null,null,"","TC22","Refer a new JobLock TNC to an ASC (Pending)","Test that an MPA can open a JobLock TNC and place the TNC into a Pending state (referring the caller/employee to an ASC for identity authentication)","New JobLock TNC","* Open SVS Case (using provided Test Data)\n* Select resolution: Pending JobLock\n* Submit","* Unresolved TNC: Pending JobLock","","",""]
["","",null,null,"","TC23","After a successful ASC visit (email notice), clear a JobLock TNC","Test that an MPA can clear a JobLock TNC after it has been placed into Pending (in the case that the employee confirms his/her identity at an ASC)","Unresolved TNC: Pending JobLock","* Select resolution: JobLock Authorized - Unlock SSN\n* Submit","* Resolved TNC: JobLock Authorized - SSN Unlocked","","",""]
["","",null,null,"","TC24","After an unsuccessful ASC visit (email notice), set the JobLock TNC to an FNC","Test than an MPA can set a JobLock TNC to an FNC after receiving it has been placed into Pending (in the case that an ASC reports the employee being unable to confirm his/her identity)","Unresolved TNC: Pending JobLock","* Select resolution: JobLock FNC\n* Submit","* Resolved TNC: JobLock FNC - ASC Visit Failed","","",""]
["","",null,null,"","TC25","System changes \"Pending JobLock\" TNC to FNC after ASC visit timer expires","Test that the system will change a JobLock TNC to an FNC after the Pending timer expires with no communication from an ASC (in the case of an ASC no show) ","Unresolved TNC: Pending JobLock","* System determines that 32 days have elapsed\n* System changes JobLock resolution to \"JobLock FNC - No Show'","* Resolved TNC: JobLock FNC - ASC No Show","","","Automated system action"]
["","",null,null,"","TC26","Open a new JobLock & DHS TNC, clear the JobLock TNC keeping the SSN locked, and clear the DHS TNC","Test that an MPA can open a new JobLock/DHS \"double\" TNC and clear both TNC reasons, keeping the SSN locked for the JobLock TNC","New JobLock & DHS TNC","* Open SVS Case (using provided Test Data)\n* Select resolution: \"JobLock Authorized - SSN Remains Locked\"\n* Select resolution: \"DHS Authorized\"\n* Submit\n* Receive correct email notice","* Resolved JobLock TNC: JobLock Authorized - SSN Remains Locked \n* Resolved DHS TNC: DHS Authorized\n* Email notice of successful SSN usage received","","",""]
["","",null,null,"","TC27","Open a new JobLock & DHS TNC, clear the JobLock TNC keeping the SSN locked, and do not change the DHS resolution","Test that an MPA can open a new JobLock/DHS \"double\" TNC and clear the JobLock TNC, keeping the SSN locked, without changing the DHS resolution","New JobLock & DHS TNC","* Open SVS Case (using provided Test Data)\n* Select resolution: \"JobLock Authorized - SSN Remains Locked\"\n* Submit\n* Receive correct email notice","* Resolved JobLock TNC: JobLock Authorized - SSN Remains Locked\n* Unresolved DHS TNC: No Resolution\n* Email notice of successful SSN usage received","","",""]
["","",null,null,"","TC28","Update a TNC from no DHS resolution to DHS Authorized","Test that an MPA can update a TNC from no DHS resolution to DHS Authorized, with the JobLock TNC already cleared and the SSN remaining locked","* Resolved JobLock TNC: JobLock Authorized - SSN Remains Locked\n* Unresolved DHS TNC: No Resolution","* Select resolution: \"DHS Authorized\"\n* Submit","* Resolved JobLock TNC: JobLock Authorized - SSN Remains Locked\n* Resolved DHS TNC: DHS Authorized","","",""]
["","",null,null,"","TC29","Update a TNC from no DHS resolution to DHS FNC (any type)","Test than an MPA can update a TNC from no DHS resolution to a type of DHS FNC, with the JobLock TNC already cleared and the SSN remaining locked","* Resolved JobLock TNC: JobLock Authorized - SSN Remains Locked\n* Unresolved DHS TNC: No Resolution","* Select resolution: \"DHS FNC\"\n* Submit","* Resolved JobLock TNC: JobLock Authorized - SSN Remains Locked\n* Resolved DHS TNC: DHS FNC (any type)","","",""]
["","",null,null,"","TC30","Update a TNC from no DHS resolution to Continue to Process","Test that an MPA can update a TNC from no DHS resolution to Continue to Process, with the JobLock TNC already cleared and the SSN remaining locked","* Resolved JobLock TNC: JobLock Authorized - SSN Remains Locked\n* Unresolved DHS TNC: No Resolution","* Select resolution: \"DHS Continue to Process\"\n* Submit","* Resolved JobLock TNC: JobLock Authorized - SSN Remains Locked\n* Unresolved DHS TNC: Continue to Process","","",""]
["","",null,null,"","TC31","Update a TNC from Continue to Process to DHS Authorized","Test that an MPA can update a TNC from Continue to Process to DHS Authorized, with the JobLock TNC already cleared and the SSN remaining locked","* Resolved JobLock TNC: JobLock Authorized - SSN Remains Locked\n* Unresolved DHS TNC: Continue to Process","* Select resolution: \"DHS Authorized\"\n* Submit","* Resolved JobLock TNC: JobLock Authorized - SSN Remains Locked\n* Resolved DHS TNC: DHS Authorized","","",""]
["","",null,null,"","TC32","Update a TNC from Continue to Process to DHS FNC (any type)","Test that an MPA can update a TNC from Continue to Process to a type of DHS FNC, with the JobLock TNC already cleared and the SSN remaining locked","* Resolved JobLock TNC: JobLock Authorized - SSN Remains Locked\n* Unresolved DHS TNC: Continue to Process","* Select resolution: \"DHS FNC\"\n* Submit","* Resolved JobLock TNC: JobLock Authorized - SSN Remains Locked\n* Resolved DHS TNC: DHS FNC (any type)","","",""]
["","",null,null,"","TC33","Open a new JobLock & DHS TNC, clear the JobLock TNC unlocking the SSN, and clear the DHS TNC","Test that an MPA can open a new JobLock/DHS \"double\" TNC and clear both TNC reasons, unlocking the SSN for the JobLock TNC","New JobLock & DHS TNC","* Open SVS Case (using provided Test Data)\n* Select resolution: \"JobLock Authorized - Unlock SSN\"\n* Select resolution: \"DHS Authorized\"","* Resolved JobLock TNC: JobLock Authorized - SSN Unlocked \n* Resolved DHS TNC: DHS Authorized","","",""]
["","",null,null,"","TC34","Open a new JobLock & DHS TNC, clear the JobLock TNC unlocking the SSN, and do not change the DHS resolution","Test that an MPA can open a new JobLock/DHS \"double\" TNC and clear the JobLock TNC, unlocking the SSN, without changing the DHS resolution","New JobLock & DHS TNC","* Open SVS Case (using provided Test Data)\n* Select resolution: \"JobLock Authorized - Unlock SSN\"\n* Submit","* Resolved JobLock TNC: JobLock Authorized - SSN Unlocked\n* Unresolved DHS TNC: No Resolution","","",""]
["","",null,null,"","TC35","Update a TNC from no DHS resolution to DHS Authorized","Test that an MPA can update a TNC from no DHS resolution to DHS Authorized, with the JobLock TNC already cleared and the SSN unlocked","* Resolved JobLock TNC: JobLock Authorized - SSN Unlocked\n* Unresolved DHS TNC: No Resolution","* Select resolution: \"DHS Authorized\"\n* Submit","* Resolved JobLock TNC: JobLock Authorized - SSN Unlocked\n* Resolved DHS TNC: DHS Authorized","","",""]
["","",null,null,"","TC36","Update a TNC from no DHS resolution to DHS FNC (any type)","Test than an MPA can update a TNC from no DHS resolution to a type of DHS FNC, with the JobLock TNC already cleared and the SSN unlocked","* Resolved JobLock TNC: JobLock Authorized - SSN Unlocked\n* Unresolved DHS TNC: No Resolution","* Select resolution: \"DHS FNC\"\n* Submit","* Resolved JobLock TNC: JobLock Authorized - SSN Unlocked\n* Resolved DHS TNC: DHS FNC (any type)","","",""]
["","",null,null,"","TC37","Update a TNC from no DHS resolution to Continue to Process","Test that an MPA can update a TNC from no DHS resolution to Continue to Process, with the JobLock TNC already cleared and the SSN unlocked","* Resolved JobLock TNC: JobLock Authorized - SSN Unlocked\n* Unresolved DHS TNC: No Resolution","* Select resolution: \"DHS Continue to Process\"\n* Submit","* Resolved JobLock TNC: JobLock Authorized - SSN Unlocked\n* Unresolved DHS TNC: Continue to Process","","",""]
["","",null,null,"","TC38","Update a TNC from Continue to Process to DHS Authorized","Test that an MPA can update a TNC from Continue to Process to DHS Authorized, with the JobLock TNC already cleared and the SSN unlocked","* Resolved JobLock TNC: JobLock Authorized - SSN Unlocked\n* Unresolved DHS TNC: Continue to Process","* Select resolution: \"DHS Authorized\"\n* Submit","* Resolved JobLock TNC: JobLock Authorized - SSN Unlocked\n* Resolved DHS TNC: DHS Authorized","","",""]
["","",null,null,"","TC39","Update a TNC from Continue to Process to DHS FNC (any type)","Test that an MPA can update a TNC from Continue to Process to a type of DHS FNC, with the JobLock TNC already cleared and the SSN unlocked","* Resolved JobLock TNC: JobLock Authorized - SSN Unlocked\n* Unresolved DHS TNC: Continue to Process","* Select resolution: \"DHS FNC\"\n* Submit","* Resolved JobLock TNC: JobLock Authorized - SSN Unlocked\n* Resolved DHS TNC: DHS FNC (any type)","","",""]
["","",null,null,"","TC40","Open a new JobLock & DHS TNC, set the JobLock TNC to Pending (ASC referral), and clear the DHS TNC","Test that an MPA can open a new JobLock/DHS \"double\" TNC, set the JobLock TNC to Pending (in the case of failed Challenge Questions and ASC referral), and clear the DHS TNC","New JobLock & DHS TNC","* Open SVS Case (using provided Test Data)\n* Select resolution: \"Pending JobLock\"\n* Select resolution: \"DHS Authorized\"\n* Submit","* Unresolved JobLock TNC: Pending JobLock\n* Resolved DHS TNC: DHS Authorized","","",""]
["","",null,null,"","TC41","Open a new JobLock & DHS TNC, set the JobLock TNC to Pending (ASC referral), and do not change the DHS resolution","Test that an MPA can open a new JobLock/DHS \"double\" TNC and set the JobLock TNC to Pending (in the case of failed Challenge Questions and ASC referral) without changing the DHS resolution","New JobLock & DHS TNC","* Open SVS Case (using provided Test Data)\n* Select resolution: \"Pending JobLock\"\n* Submit","* Unresolved JobLock TNC: Pending JobLock\n* Unresolved DHS TNC: No Resolution","","",""]
["","",null,null,"","TC42","Update a TNC from no DHS resolution to DHS Authorized","Test that an MPA can update a TNC from no DHS resolution to DHS Authorized, while the JobLock TNC is set to Pending","* Unresolved JobLock TNC: Pending JobLock\n* Unresolved DHS TNC: No Resolution","* Select resolution: \"DHS Authorized\"\n* Submit","* Unresolved JobLock TNC: Pending JobLock\n* Resolved DHS TNC: DHS Authorized","","",""]
["","",null,null,"","TC43","Update a TNC from Pending to JobLock Authorized (unlocking the SSN)","Test that an MPA can update a TNC from Pending to JobLock Authorized (unlocking the SSN), when the DHS TNC has already been cleared","* Unresolved JobLock TNC: Pending JobLock\n* Resolved DHS TNC: DHS Authorized","* Select resolution: \"JobLock Authorized - Unlock SSN\"\n* Submit","* Resolved JobLock TNC: JobLock Authorized - SSN Unlocked\n* Resolved DHS TNC: DHS Authorized","","",""]
["","",null,null,"","TC44","Update a TNC from Pending to JobLock FNC (unsuccessful ASC visit)","Test that an MPA can update a TNC from Pending to JobLock FNC (unsuccessful ASC visit), when the DHS TNC has already been cleared","* Unresolved JobLock TNC: Pending JobLock\n* Resolved DHS TNC: DHS Authorized","* Select resolution: \"JobLock FNC - ASC visit failed\"\n* Submit","* Resolved JobLock TNC: JobLock FNC - ASC Visit Failed\n* Resolved DHS TNC: DHS Authorized","","",""]
["","",null,null,"","TC45","System changes a TNC from Pending to JobLock FNC (ASC no show)","Test that the system will change a JobLock TNC to an FNC after the Pending timer expires with no communication from an ASC (in the case of an ASC no show) - this will occur even if a DHS TNC has already been cleared","* Unresolved JobLock TNC: Pending JobLock\n* Resolved DHS TNC: DHS Authorized","* System determines that 32 days have elapsed\n* System changes JobLock resolution to \"JobLock FNC - No Show'","* Resolved JobLock TNC: JobLock FNC - ASC No Show\n* Resolved DHS TNC: DHS Authorized",null,"",""]
["","",null,null,"","TC46","Update a TNC from no DHS resolution to DHS FNC (any type)","Test that an MPA can update a TNC from no DHS resolution to DHS FNC (any type), while the JobLock TNC is set to Pending","* Unresolved JobLock TNC: Pending JobLock\n* Unresolved DHS TNC: No Resolution","* Select resolution: \"DHS FNC\"\n* Submit","* Unresolved JobLock TNC: Pending JobLock\n* Resolved DHS TNC: DHS FNC (any type)","","",""]
["","",null,null,"","TC47","Update a TNC from no DHS resolution to Continue to Process","Test that an MPA can update a TNC from no DHS resolution to Continue to Process, while the JobLock TNC is set to Pending","* Unresolved JobLock TNC: Pending JobLock\n* Unresolved DHS TNC: No Resolution","* Select resolution: \"DHS Continue to Process\"\n* Submit","* Unresolved JobLock TNC: Pending JobLock\n* Unresolved DHS TNC: Continue to Process","","",""]
["","",null,null,"","TC48","Update a TNC from Continue to Process to DHS Authorized","Test that an MPA can update a TNC from Continue to Process to DHS Authorized, while the JobLock TNC is set to Pending","* Unresolved JobLock TNC: Pending JobLock\n* Unresolved DHS TNC: Continue to Process","* Select resolution: \"DHS Authorized\"\n* Submit","* Unresolved JobLock TNC: Pending JobLock\n* Resolved DHS TNC: DHS Authorized","","",""]
["","",null,null,"","TC49","Update a TNC from Continue to Process to DHS FNC (any type)","Test that an MPA can update a TNC from Continue to Process to a type of DHS FNC, while the JobLock TNC is set to Pending","* Unresolved JobLock TNC: Pending JobLock\n* Unresolved DHS TNC: Continue to Process","* Select resolution: \"DHS FNC\"\n* Submit","* Unresolved JobLock TNC: Pending JobLock\n* Resolved DHS TNC: DHS FNC (any type)","","",""]
["","",null,null,"","TC50","Update a TNC from Pending to JobLock Authorized (unlocking the SSN)","Test that an MPA can update a TNC from Pending to JobLock Authorized (unlocking the SSN), while the DHS TNC is in Continuance","* Unresolved JobLock TNC: Pending JobLock\n* Unresolved DHS TNC: Continue to Process","* Select resolution: \"JobLock Authorized - Unlock SSN\"\n* Submit","* Resolved JobLock TNC: JobLock Authorized - SSN Unlocked\n* Unresolved DHS TNC: Continue to Process","","",""]
["","",null,null,"","TC51","Update a TNC from Pending to JobLock FNC (unsuccessful ASC visit)","Test that an MPA can update a TNC from Pending to JobLock FNC (unsuccessful ASC visit), while the DHS TNC is in Continuance","* Unresolved JobLock TNC: Pending JobLock\n* Unresolved DHS TNC: Continue to Process","* Select resolution: \"JobLock FNC - ASC visit failed\"\n* Submit","* Resolved JobLock TNC: JobLock FNC - ASC Visit Failed\n* Unresolved DHS TNC: Continue to Process","","",""]
["","",null,null,"","TC52","System changes a TNC from Pending to JobLock FNC (ASC no show)","Test that the system will change a JobLock TNC to an FNC after the Pending timer expires with no communication from an ASC (in the case of an ASC no show) - this will occur even if a DHS TNC is in Continuance","* Unresolved JobLock TNC: Pending JobLock\n* Unresolved DHS TNC: Continue to Process","* System determines that 32 days have elapsed\n* System changes JobLock resolution to \"JobLock FNC - No Show'","* Resolved JobLock TNC: JobLock FNC - ASC No Show\n* Unresolved DHS TNC: Continue to Process","","",""]
["","",null,null,"","TC53","Attempt to use JULS without proper access","Test that users without sufficient rights in JULS can not use the system","* SVS user accounts with various level sof JULS access","* Log in as MPA\n* Attempt to perform Supervisor actions\n* Log in with Read Only access\nAttempt to perform MPA and Supervisor actions","* MPA user account unable to perform Supervisor actions\n* Read Only user account unable to perform MPA actions","","",""]
["","",null,null,"","TC54","Search for JULS Cases","Search for JULS Cases by SSN, Verification Number, and Receipt Number","* Various types of JULS Cases","* Log in as MPA\n* Use JULS search functions to find Cases by Receipt Number (JobLock Reference Number)\n* … by Social Security NUmber\n* … by Verification Number (after TNCs have been generated due to JULS Cases)","* Search results displayed for each type of search criteria","","",""]
["","",null,null,"","TC55","Attempt to modify closed JULS Cases","Attempt to manipulate an unlocked (closed) JULS Case","* JULS Cases that have been unlocked","* Log in as an MPA\n* Open an unlocked JULS Case\n* Attempt to modify the status or data of the Case","* MPA user account unable to modify the status or data in an unlocked JULS Case","","",""]
["","",null,null,"","TC56","Generate JobLock TNC documentation","Generate TNC and Referral documents for JobLock TNC","* SSN locked in JULS (and related personal information known)","* Log into E-Verify\n* Perform a query using the information of a locked SSN","* JobLock TNC generated","","",""]
["","",null,null,"","TC57","Generate JobLock and DHS mismatch documentation","Generate TNC and Referral documents for JobLock & DHS mismatch \"dual\" TNC","* Non-Citizen SSN locked in JULS (and related personal information known)","* Log into E-Verify\n* Perform a query using the information of a locked SSN (and incorrect immigration information)","* JobLock and DHS mismatch \"double\" TNC generated","","",""]
["","",null,null,"","TC58","Create and modify JULS user accounts","Create/Set up JULS user","* SVS/JULS Superuser account","* Log into SVS as a Superuser\n* Modify the JULS access rights an SVS user account\n* Log into JULS with each access level","* Ability to modify JULS access rights of an SVS account\n* Ability to perform JULS actions appropriate for each access level","","",""]
["","",null,null,"","TC59","Identify JULS Case in a Pending state","Test that the JULS Case exists in the Pending state and does not appear in any work queues","* JULS Case in a Pending state","* Log into JULS as a Supervisor\n* Search unassigned and assigned work queues for Pending JULS Case\n* Search all JULS Cases for Pending Case\n","* Pending Case does not appear in unassigned or assigned work queues\n* Pending Case can be found by searching all JULS Cases","","",""]

{"sheet":"Data Requirements","index":2,"n_rows":19,"n_cols":7,"rows_kept":19,"cut":false,"hidden":true,"merged":[[17,4,17,5],[18,4,18,5]],"flags":["formulas_cached_only"]}
[]
[]
[]
[null,null,null,"USCIS Special Operations | JobLock UAT | Test Data Requirements",null,"2010-12-09T13:29:57.770","Last updated: 12/09/2010"]
[]
[null,null,null,"Data Type","Description","Special Conditions","Quantity"]
[null,null,null,"New JobLock Applications","JobLock Applications waiting in the JULS unassigned queue as they would appear after arriving from E-Filing","Please see the Additional Notes below","5 Applications/Tester\n3 Testers/Group\n4 Groups\n60 Applications"]
[null,null,null,"Pending JobLock Applications","JobLock Applications in JULS with a Pending status (awaiting FTC complaint verification), timed such that the 15 day timer will elapse during UAT","Please see the Additional Notes below\n\nThese JULS Case should be set to elapse soon after the first day of UAT - this will allow testers to identify that the JULS Case is in the Pending state at the beginning of UAT\n\nThese JULS Cases should be set to elapse before the last day of UAT - this will allow testers to test that the system has placed these Cases into the proper status","1 Application/Group\n4 Groups\n4 Applications"]
[null,null,null,"Locked SSNs","SSNs locked in JULS that can be unlocked during testing","Please see the Additional Notes below\n\nThese locked SSNs are necessary in the event that testers are not able to test with locked SSNs that result from testing the lock process","2 Cases/Tester\n4 Groups\n8 Cases"]
[null,null,null,"JobLock TNCs","New TNCs in SVS generated due to a JobLock reason (without SSA or DHS mismatches)","Please see the Additional Notes below","4 JobLock TNCs/Tester\n4 Groups\n16 JobLock TNCs"]
[null,null,null,"Pending JobLock TNCs","JobLock TNCs in SVS in a Pending status (referred to ASC), timed such that the 32 day timer will elapse during UAT","Please see the Additional Notes below\n\nPlease see the Special Conditions listed above in the Pending JobLock Applications Data Type, as system actions in SVS need to be tested in the same way as in JULS","1 Pending JL TNC/Grp\n4 Groups\n4 Pending JL TNCs"]
[null,null,null,"JobLock and DHS Mismatch TNCs","New TNCs with both a JobLock reason and a DHS mismatch","Please see the Additional Notes below","8 Dual TNCs/Tester\n4 Groups\n32 Dual TNCs"]
[null,null,null,"Pending JobLock and DHS Mismatch TNCs","TNCs, with both a JobLock reason and a DHS mismatch, in a Pending Status (referred to ASC), timed such that the 32 day timer will elapse during UAT","Please see the Additional Notes below\n\nThe status of the DHS mismatch may be either \"Authorized\" or \"Continue to Process,\" as the elapsed timer should cause an FNC in either situation.  The DHS resolution must not be an \"FNC.\"","1 Pending Dual TNC/Grp\n4 Groups\n4 Pending Dual TNCs"]
[null,null,null,"Locked SSN that will clear an SSA automated check","A Name, Date of Birth, and SSN combination, with the SSN locked in JULS, that will produce a JobLock TNC (and no other TNCs) when queried in E-Verify","All of the data necessary to run an E-Verify query will be needed to test the TNC generation\n\nThe queried data will need to clear an SSA check and generate a JobLock TNC without a DHS mismatch","1 Locked SSN  with related data"]
[null,null,null,"Locked immigrant SSN that will clear an SSA automated check","A Name, Date of Birth, and SSN combination, with the SSN locked in JULS, that will produce a JobLock and DHS mismatch TNC when queried in E-Verify","All of the data necessary to run an E-Verify query will be needed to test the TNC generation\n\nThe queried data will need to clear an SSA check and generate a TNC that has both a JobLock reason and a DHS mismatch","1 Locked SSN  with related data"]
[]
[null,null,null,"Additional Notes"]
[null,null,null,"Test Data Designation by Location","UAT will be performed by the following four distinct organizational/geographic groups:\n- 3 SVO staff in Los Angeles\n- 3 SVO staff in Buffalo\n- 3 SVO and Special Operations staff in Washington, DC\n- 3 CCO staff\n\nWith these separate Groups, we would like a method for testers to identify which test data they should be using.  We believe the test cases can be designated for use by a specific group through identifiers in the mock data:\n- For JULS Cases, through fields such as Receipt Number, SSN, Name, or other field (e.g., the Name fields of JULS Cases to be used by the SVO Buffalo staff are \"BuffaloTesterOne,\" \"BuffaloTesterTwo,\" etc)\n- For TNCs, through Verification Case Number or other field"]
[null,null,null,"Email Addresses in Test Data","Each testing Group will need to view the emails generated by their JULS and SVS testing.  To facilitate this, the JULS test data designated for each Group should use an email address that a member of that Group can monitor (e.g., the DHS email address of the Group's testing lead).\n\nFor TNC test data, the underlying JULS Case (the SSN that was locked to generate the TNC) should also use email addresses corresponding to each Group to ensure that any SVS-generated emails are sent to a monitored email address.\n\nThe specific email addresses to use for each Group will be provided as soon as the testers in each Group have been identified."]

{"sheet":"Testers","index":3,"n_rows":18,"n_cols":10,"rows_kept":18,"cut":false,"hidden":true,"merged":[],"flags":["formulas_cached_only"]}
[]
[]
[]
[null,null,null,"USCIS Special Operations | JobLock UAT | Testers",{"$nulls":4},"2010-12-09T13:29:57.770","Last updated: 12/09/2010"]
[]
[null,null,null,"#","Name","Organization","Location","Role","Phone","Email"]
[{"$nulls":4},"JeNeil Teel","Customer Contact Operations","Washington, DC","Tester","202-358-7503","JeNeil.Teel@dhs.gov"]
[{"$nulls":4},"Mike Mayhew","Special Operations","Washington, DC","Supervisor","202-358-7726","Michael.Mayhew@dhs.gov"]
[{"$nulls":4},"Timothy Cooke","Special Operations","Washington, DC","Tester","202-264-0071","Timothy.Cooke@dhs.gov"]
[{"$nulls":4},"David Pittman","Special Operations","Washington, DC","Tester","202-358-7829","David.M.Pittman1@dhs.gov"]
[{"$nulls":4},"Lesha Glenn-Pryer","Status Verification Operations","Buffalo, NY","Tester","716-843-8923","Lesha.Glenn-Pryer@dhs.gov"]
[{"$nulls":4},"Mark Frankel","Status Verification Operations","Buffalo, NY","Tester","716-843-8929","Mark.Frankel@dhs.gov"]
[{"$nulls":4},"Aileen Masterson","Status Verification Operations","Buffalo, NY","Supervisor","716-843-8946","Aileen.Masterson@dhs.gov"]
[{"$nulls":4},"Ross Christopher","Status Verification Operations","Buffalo, NY","Supervisor","716-843-8920","Ross.Christopher@dhs.gov"]
[{"$nulls":4},"Angel Masmela","Status Verification Operations","Los Angeles, CA","Supervisor","213-893-1301","Angel.Masmela@dhs.gov"]
[{"$nulls":4},"Omar Larais","Status Verification Operations","Los Angeles, CA","Tester","213-893-1305","Nofal.Larais@dhs.gov"]
[{"$nulls":4},"Archiemedes Tolentino","Status Verification Operations","Los Angeles, CA","Tester","213-893-1340","Archiemedes.Tolentino@dhs.gov"]
[{"$nulls":4},"Sonja Bailon","Status Verification Operations","Los Angeles, CA","Tester","213-893-1303","Sonja.Bailon@dhs.gov"]

{"sheet":"User Roles and Login","index":4,"n_rows":6,"n_cols":10,"rows_kept":6,"cut":false,"hidden":true,"merged":[],"flags":["formulas_cached_only"]}
[]
[]
[]
[null,null,null,"USCIS Special Operations | JobLock UAT | User Roles and Login",{"$nulls":4},"2010-12-09T13:29:57.770","Last updated: 12/09/2010"]
[]
[null,null,null,"#"]