-
Type: Story
-
Status: Closed (View Workflow)
-
Resolution: Completed
-
Affects Version/s: None
-
Fix Version/s: CFA 2019R1
-
Component/s: AutoNotification
-
Labels:
-
Sprint:CFAMX 2019R1 Sprint 4, CFAMX 2019R1 Sprint 5
-
SOW (Time Tracking) Project:44863
-
Work Type Classification:Sustaining
As a supply chain user in InFORM, I would like to receive more detail in the warnings sent via email for my ASN orders.
Use Case
Current ASN Failures sent via email contain no information on what order failed and why. This makes it impossible for an Operator to troubleshoot.
Notes
- Config of an ASN Import Failure Auto Notification:
- The following fields should be contained in the email generated for ASN Failures:
- Name of Vendor who sent the file (each vendor has a separate import process)
- Store number (assuming that the file has not failed before being able to get this data)
- Order number (assuming that the file has not failed before being able to get this data)
- One of the following should also be included in the ASN Failure message:
- Attachment of the actual ASN XML file.
- If attaching the actual XML file is not possible/recommended, we need at minimum to have the actual file name included in error email so we can determine additional info.
Acceptance Criteria:
- Any data points added to the Failure Auto Notification should be included in the System Generated Message
- Confirm when the ASN Failure Auto Notification is generated, it contains the name of the Vendor who sent the file.
- Confirm when the ASN Failure Auto Notification is generated, it contains the store number for the ASN Failure.
- Confirm when the ASN Failure Auto Notification is generated, it contains the order number for the ASN Failure.
- Confirm when the ASN Failure Auto Notification is generated, it contains either:
- An attachment, which is the XML file of the failed order
- The actual file name of the file that failed to process
- implements
-
CFAMX-984 Improve the level of detail that is sent in the ASN import failure notification email - INF-10160
- Done
There are no Sub-Tasks for this issue.