USEPA / e-manifest

API services documentation and reference material for the e-Manifest hazardous waste tracking system
https://www.epa.gov/e-manifest
Creative Commons Zero v1.0 Universal
26 stars 22 forks source link

EM-3173 Services: Able to create an electronic manifest in scheduled without a TSDF #1621

Closed e-manifest closed 2 months ago

e-manifest commented 2 months ago

Draft Need to test Generator and Transporter

[~accountid:60748bb6c642ff0070cbc6a1] was assisting a site with electronic adoption when they found this bug:

They sent a manifest via services and did not put in the TSDF in their JSON. that then created a manifest that could not be used via the UI.

!image-20240209-220216.png|width=887,height=329!

If the TSDF is missing an a site is trying to submit a manifest via services the system should respond like we do for paper with:

{noformat} "errors": [ { "field": "Emanifest.tsdf.epaSiteId", "message": "Mandatory Field is Not Provided" }, { "field": "Emanifest.tsdf.siteAddress", "message": "Mandatory Field is Not Provided" }, { "field": "Emanifest.tsdf.name", "message": "Value is not provided" }, { "field": "Emanifest.tsdf.contact.phone.number", "message": "Mandatory Field is Not Provided" } ],{noformat}

For your reference here is the JSON and a dev manifest

{{In dev "manifestTrackingNumber": "100038013ELC",}}

{{ "manifestTrackingNumber": "100038014ELC",}}

[^payload.json]



Acceptance Criteria
(x) TSDF is mandatory for a manifest in the scheduled status

(x) If a TSDF is not submitted then the following error should be provided:

{noformat}"errors": [ { "field": "Emanifest.designatedFacility", "message": "For Scheduled status a Designated Facility shall be provided" } ],{noformat}

(x) Image manifests can be submitted without Transporters present on the manifest