-
Type: Story
-
Status: Open (View Workflow)
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: None
-
Work Type Classification:Sustaining
As a third party system I want receive one Petty Cash Category file per Country so that I can then distribute each file to the relevant POS systems
Notes:
- Today, one unique file is generated for each active store in InFORM and sent to the store every day
- This request is to replace this store level integration with an above store integration, sending one file per country:
- United States
- Canada
- Puerto Rico
- Today, the data contained within the files, that is store specific, is also Country specific.
- CA categories are not sent to US stores and vice versa
- Confluence page for configuring categories by Country
Production Server Manager config:
Archived (sent) files, US vs CA
Sample files, from Prod:
- US Store: InformPettyCashCategories_04906_A_20220125_020823.xml
- CA Store: InformPettyCashCategories_30001_A_20220125_020823.xml
- Note: Some codes may be present in both files, those for US and those for CA, but in the database, there are actually two entries, one for each country
- When this new interface is switched on, it will send to an S3 bucket, and the old job which Sends To Store will not be used
Acceptance Criteria
- Confirm that there is a new mechanism to generate one Petty Cash Category file per country
- I am not sure if this will be new, or some version/configuration of the old job, hence mechanism
- Confirm that the file naming convention is:
- InFORMPettyCashCategory_United States (For United States)
- InFORMPettyCashCategory_Canada (For Canada)
- InFORMPettyCashCategory_Puerto Rico (For Puerto Rico)
- Confirm that if the same code is configured for each country, that code is included in each file
- There will be multiple instances of the code, with a different Country, in the database [LedgerChartOfAccountsCountry]
- Confirm that if a code is only configured for a specific country, it is only included in the file for that country
- Confirm that the format of the file remains the same, as it is today (see examples above)
- Confirm that it is possible to generate files either the old way (one per store) or the new way (one per country)
- implements
-
CFAMX-14120 CloudLink - MVP
- Open
1.
|
Create Test Scripts | Ready for QA | Unassigned |
|
|||||||
2.
|
Review Test Scripts | Ready for QA | Unassigned |
|
|||||||
3.
|
Deploy | Ready for QA | Unassigned |
|
|||||||
4.
|
Execute Test Cases | Ready for QA | Unassigned |
|
|||||||
5.
|
Functional Review with QA | Ready for Developer | Unassigned |
|
|||||||
6.
|
DIT | Ready for Developer | Unassigned |
|
|||||||
7.
|
Design Review | Ready for Developer | Unassigned |
|
|||||||
8.
|
Story Documentation | Ready for Developer | Unassigned |
|