bcgov / bcgov/SIMS

CAS - Limit how far to search for invoices on Batch

Open
#4,556 0 comments 0 reactions 0 assignees View on GitHub
Business
Dominant language
TypeScript
Stars
29
Forks
15
PR merge metrics
No merged PRs in 30d

Description

**User Story**
As a ministry user, I only want the batch to pick up invoices from within the last 365 days. This gives a limit to how far back the system will need to look for invoices, and reduces invoices coming from across multiple calendar/fiscal years. To prevent any missed invoices a warning message should be logged so that the technical team can be aware and reach out if necessary to the Finance team (should be a small edge case).

**Acceptance Criteria**

## Acceptance Criteria
> Generated by [Zenhub AI](https://www.zenhub.com/ai)

- [ ] **Scenario: Batch only searches for invoices within the last 365 days**
- Given the batch is configured with a search limit of 365 days
- When the batch processes invoices
- Then it should only pick up invoices from within the last 365 days
- [ ] **Scenario: Warning message logged for edge cases**
- Given a batch process misses an invoice due to the search limit
- When the batch completes processing
- Then a warning message should be logged, notifying the technical team to reach out to Finance if necessary

Contributor guide

No contributing guide indexed for this repository

Research direction

No files or tests are named in the issue. Start by locating the CAS batch invoice-processing entry point and its existing date-search configuration, then trace how completion and logging are handled. Done means batches search only the previous 365 days and log a warning when an invoice is missed because of that limit, with coverage for both acceptance scenarios.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
backend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.