Records Log - View PDFs in Browser

[m-prodan]

• As an IAO analyst or ministry coordinator
• I want to be able to view a PDF record in a browser tab
• so that I can review the record without needing to download it first

Assumptions & Scope What are the assumptions for this story?

User will want to view and PDF in the Records Log without needing to download it first.

What is IN scope? Viewing PDFs in the browser from the Records log.

What is NOT in scope? Viewing non-PDFs

Acceptance Criteria

Scenario 1: View on Click

• GIVEN the user is on the Records log
• WHEN the user clicks on a PDF
• AND the file is NOT an email file (.eml, .msg)
• THEN the dropdown will open
• AND 'View' will now be an option

Scenario 2: Click 'View'

• GIVEN the user has opened an Record dropdown
• WHEN the user clicks 'View'
• THEN the a display of the record will open in a new browser tab

Scenario 3: Click PDF record name

• GIVEN the user is on the Records log
• WHEN the user clicks on the title of the PDF Record
• THEN the a display of the Record will open in a new browser tab

Scenario 3: Click Non-PDF record name

• GIVEN the user is on the Records log
• WHEN the user clicks on the title of a non-PDF Record
• THEN the nothing will happen

Dependencies? What is the impact of this dependency? (If so, link dependency in the ticket, make it visible in a team´s backlog)

Validation Rules? (If yes, list here)

Design @xxx - please link the Design here

Definition of Ready

1. [ ] Is there a well articulated User Story?
2. [ ] Is there Acceptance Criteria that covers all scenarios (happy/sad paths)?
3. [ ] If there is a user interface, is there a design?
4. [ ] Does the user story need user research/validation?
5. [ ] Does this User Story needs stakeholder approval?
6. [ ] Design / Solution accepted by Product Owner
7. [ ] Is this user story small enough to be completed in a Sprint? Should it be split?
8. [ ] Are the dependencies known/ understood? (technical, business, regulatory/policy)
9. [ ] Has the story been estimated?

Definition of Done

1. [ ] Passes developer unit tests
2. [ ] Passes peer code review
3. [ ] If there's a user interface, passes UX assurance
4. [ ] Passes QA of Acceptance Criteria with verification in Dev and Test
5. [ ] Confirm Test cases built and succeeding
6. [ ] No regression test failures
7. [ ] Test coverage acceptable by Product Owner
8. [ ] Ticket ready to be merged to master or story branch
9. [ ] Developer to list Config changes/ Update documents and designs
10. [ ] Can be demoed in Sprint Review
11. [ ] Tagged as part of a Release
12. [ ] Feature flagged if required
13. [ ] Change Management activities done?

[lmullane]

Can you view Word and other MS documents now from the Attachment Log or only PDFs?

[lmullane]

Updated the AC