---
# System prepended metadata

title: Small Changes Theme

---

---
title: Small Changes Theme 
---

### **IMTA-9204 Populating Importer, Consignee and Person Responsible when 'Copying as New'**



**As an** Importer/Agent
**I want** to be able to copy a notification with a selected delegated authority 
**So that** I do not have to re-enter information for a similar imported consignment 


**Description** 

This story ensures the CHED-PP  ‘copy as new’ feature functions for notifications with a selected delegated authority 

**Acceptance Criteria** 

**Given** I am an Importer
**When** I copy as new a notification that has been raised on my behalf
**Then** I want the Importer, Consignee and Responsible person to be copied across to the new notification
**And** the notification is no longer treated as a notification raised on my behalf

**Given** I am an Agent
**When** I copy as new a notification that has been raised on behalf of someone else
**Then** I want the Importer, Consignee and Responsible person to be copied across to the new notification
**And** the notification is still raised on behalf the importer

**Given** I am an Agent
**When** I copy as new a notification that has been raised by the importer
**Then** I want the Importer, Consignee and Responsible person to be copied across to the new notification
**And** the notification is now raised on behalf of the importer by my agency


**Technical Notes** 
* Backend notification-microservice determines if economic operators still exist
    * Ensure they're always copied, as they aren't economic operators
* Only copy agency organisation ID if the copy-as-new action is taken by a delegated agent.
* Always copy *Importer*, *Consignee* and *Responsible person* fields when using copy-as-new for a CHEDPP notification

---


### **IMTA-9242 Remove Customs Reference (DUCR)**

**As** DEFRA
**I want** the  customs reference (DUCR) removed from the CHED-PP journey
**So that** Traders are not required to enter it 

**Description**

IMTA-8249 was implemented previously to allow DUCR number to be matched with customs declarations and/or to support with DEFRA charging processes. This has now changed with the CHED notification number being the primary number for matching/charging. 

**Acceptance Criteria**

**Given** I am an Importer/Agent
**When** I select CHED_PP as a notification type
**Then** I want the “Customs Reference (DUCR)” field removed from the journey (i.e. the Origin of the import page), review page, overview pages (P1 and P2), and certificate


**UX Designs**

Needs a UX/UI of new certificate layout?


**Technical Notes** 
* Schema changes due to validation
* Backwards compatibility, leave it in the schema
* Leave in the data dictionary, mark it as to be removed
* Mapping-library changes, needs removed from the mapping

**Test notes**
* Update UI tests to remove the DUCR
* Update performance tests to remove DUCR
* Run Soap tests using Jenkins job
* Test one 

---



---

### **IMTA-8995 Quantity and Quantity Type**

As an Importer/Agent
I want to be able to enter a quantity and quantity type when adding a commodity
So that Inspectors have full visibility of the commodity being imported 


**Description**

This story introduces new values on the commodity details page to allow a trader to enter a quantity and related type 


**Acceptance Criteria** 

***Quantity and Quantity Type Fields***

**Given** I have selected CHED-PP as a notification type
**When** I open the commodity details page 
**Then** I want to see the option to enter a “Quantity” [numerical with a max value of xxxx]
**And** a “Quantity Type” [types: ‘Stems, Bulbs, Corms and rhizomes, Plants in tissue culture, Seeds or Kilograms’]

![](https://i.imgur.com/lkNczQT.png)




***Validation Message***

**Given** that I am on the commodity details page 
**When** I enter a “Quantity” without having selected a “Quantity Type” (or vice versa)
**And** select 'save and continue/return to hub' 
**Then** I want to see a page and field-level validation message 


![](https://i.imgur.com/1y5xTqn.png)



**Given** that I am on the review page
**When** I fail to enter a Quantity and/or Quantity Type on the commodity details page
**Then** I want to see a review page and field-level validation 


![](https://i.imgur.com/8QRQO9m.png)





***Review/Overview/Certificate Updates***

**Given** “Quantity” and “Quantity Type” have been added to the notification
**When** a user navigates to the review, overview pages (P1 and P2) and certificate
**Then** “Quantity” and “Quantity Type” should be displayed 


***Copy as New***


**Given** that I have selected a CHED-PP notification
**When** I select 'Copy as New'
**Then** I want Quantity and Quantity Type to be removed 


**Technical Notes**
* Out of scope - JSON Mapping needs updating and communication to Dynamics (will be played in the separate story)
* Check data dictionary for commodity data, update if required
* Schema change for review page validation



---
# STORIES LEFT TO REFINE 24/03/21

### **IMTA-9217 Remove Transporter**


**As** DEFRA
**I want** ‘Transporter’ removed from the CHED-PP notification 
**So that** users are not forced to enter information that is not required for a plant import 

**Description**

This story removes the Transporter sections across the CHED-PP journey and adds logic to the way in which the Transport after BCP page works

**Acceptance Criteria** 

Re-label 'Do you need to provide transporter details?

**Given** I have selected CHED_PP as a notification type
**When** I navigate to the “Origin of the Imports” page
**Then** I want “Do you need to provide transporter details?” to be relabelled as “Do you need to provide Means of Transport after Border Control Post (BCP) details?”

Logic to hide/display Border Control Post (BCP)

**Given** I am on the  “Origin of the Imports” page 
**When** I select “YES”  to “Do you need to provide Means of Transport after Border Control Post (BCP) details?”
**Then** I want the “Means of Transport after Border Control Post (BCP)” page to be displayed in the journey 

**Given** I am on the  “Origin of the Imports” page 
**When** I select  “NO” to “Do you need to provide Means of Transport after Border Control Post (BCP) details?”
**Then** I want the “Means of Transport after Border Control Post (BCP)” page to be hidden in the journey

Hide Transporter

**Given** I am an Importer/Agent
**When** I select CHED_PP as a notification type
**Then** I want “Transporter” hidden from the journey (i.e. the transporter page), hub page, review page, overview pages (P1 and P2), and certificate

**Given** “Transporter” has been hidden from the CHED-PP journey
**When** I select ‘Save and Continue’ from the Trader page
**And**  ‘Yes’ has been selected for ‘Do you need to provide Means of transport after BCP details?’
**Then** I want to be taken to the ‘Means of Transport after BCP' page

**Technical Notes**
- Schema changes for review page validation
- Mapping-library changes, needs removed from the mapping
- No impact on SOAP, not currently mapped
- Check copy as new

**Out of scope**
- Blocking page access via URL: transporter, search, create


**Test notes**
- UI tests need to be updated
- Performance tests need to be updated

---




### **IMTA-9220 B2C Notifier "Read-Only" Role**

**As** DEFRA
**I want** IPAFFS permissions to be updated
**So that** users accessing P1 with a “Notifier Read-Only (B2C)” can be granted a Read-Only role 

**Description**

This story expands existing permission/roles for IPAFFS by introducing Read-Only permission for B2C Notifiers 

**Note** - this story assumes the “Notifier Read-Only (B2C)” role exists in Customer Identity 

**Acceptance Criteria**

**Given** I am a user with the role “Notifier Read-Only (B2C)”
**When** I log into IPAFFS
**Then** I should only be able to read Part One notifications


**Technical Notes**

- documentation is updated with the change implemented in this ticket
- Updates to table in permission-ms and copied to docker-local





---

### **IMTA-9212 Make Phytosanitary Certificate Mandatory**

As an Inspector
I want notifiers to attach a Phytosanitary Certificate as mandatory when submitting a notification
So that it reduces rejections or time spent seeking missing documents 

**Description**

This story introduces changes to make the Phytosanitary Certificate mandatory in the CHED_PP journey for notifications that contain at least one commodity regulated by PHSI or Joint



**Acceptance Criteria** 

**Given** that I have completed a CHED-PP notification
**And** the notification contains at least one commodity regulated by PHSI or Joint
**When** I open the review page without having added a Phytosanitary Certificate Then I want to see a page and field-level validation (as per the example below)

![](https://i.imgur.com/L1CzpTL.png)


**Given** that I have selected “Phytosanitary Certificate” as a document type
**And** have entered a Document Reference and Date of Issue 
**When** I open the review page without uploaded an attachment 
**Then** I want to see a page and field-level validation (as per the example below)


![](https://i.imgur.com/dEveNF3.png)



**Technical Notes**

- Two validators in two different places: one for "Phytosanitary certificate" document type not being added, one for attachment not being added
- Every added Phytosanitary certifiate must have an attachment (so validation error for each)

**Test notes**
- UI tests might need to be updated
- Performance tests might need to be updated