FOI Processing Team Queue - Number of Pages Update (PDFTron)

NOTE - need to write this story to change source of truth of number of pages from AXIS to FOI mod when redaction app goes live

* As an IAO user
* I want the number of pages to de be displayed in my queue
* so that I can better see my caseload at a glance

**Assumptions & Scope**
This is an update to existing functionality. Right now, page counts are obtained from AXIS as the source of truth. With the redaction app going live, this will shift from what is in AXIS to what is in FOI Mod. There will still be requests where the records live in AXIS and are being actively redacted while also being in FOI Mod. This story will cover both cases, where records are in AXIS only, in both AXIS and FOI Mod, and FOI Mod only.

What is IN scope?

What is NOT in scope?

**Acceptance Criteria**

**Scenario 1: Records loaded in FOI Mod **
* GIVEN a request has records uploaded to the records tab
* WHEN they finish processing
* THEN the number of pages will be displayed in the queue

**Scenario 2: Additional Records added or removed in FOI Mod **
* GIVEN a request has records uploaded to the records tab
* WHEN additional records are added, or existing records removed
* THEN the number of pages will update in the queue

**Scenario 3: Records loaded in AXIS only**
* GIVEN a request has records uploaded to AXIS
* AND NO records are uploaded to FOI Mod
* WHEN the request is synced
* THEN the number of pages from AXIS will be displayed in the queue

**Scenario 4: Records added or removed in AXIS only**
* GIVEN a request has records uploaded to AXIS
* AND NO records are uploaded to FOI Mod
* AND pages have been added or removed from AXIS
* WHEN the request is synced
* THEN the number of pages from AXIS will be updated in the queue

**Scenario 5: Records in both systems**
* GIVEN a request has records uploaded to AXIS
* AND Records are also uploaded to FOI Mod
* AND pages have been added or removed from AXIS
* WHEN the records finish processing
* THEN the number of pages will be displayed in the queue from the FOI Mod count

**Scenario 6: Additional Records added or removed in FOI Mod, with both systems**
* GIVEN a request has records uploaded to the records tab
* AND Records are also uploaded to AXIS
* WHEN additional records are added, or existing records removed from FOI Mod
* THEN the number of pages will update in the queue from the FOI Mod page count

**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?

No files, tests, or code entry points are named. Start by tracing how the queue obtains page counts during FOI Mod processing and AXIS synchronization, then verify the six acceptance scenarios for records in FOI Mod, AXIS, or both; done means the queue displays and updates the correct source count.

Written by the indexing model from the issue text.