[NUR Consent] Support Road Manager Dual Ownership Consent in Network Update Requests

Process Flow for Dual Ownership Consent in Network Update Requests:

https://www.figma.com/board/cn8mqtyXmdGDxcuodps2kV/Process-Flows---Access-Applications%2C-Consent-Requests%2C-Renewals-and-NUR---Scenarios?node-id=0-1&t=Jzjkd0iJwGxXv1od-0

Before Draft is saved:

• On create/edit and selecting a dual-managed segment in 1st NUR a message is being displayed informing that there are some dual managed segments in the current NUR;

Draft state:

After NUR1 draft was saved, a user is prompted to generate Information Request (IR) to resolve any potential issues between RM1 and RM2;

• RM1 won’t be able to submit NUR1 until IR(s) generated;

• RM1 won’t be able to submit NUR1 until IR(s) has been responded to by the other RM(s);

• Removing dual-managed segment(s) from NUR1 would delete related IR(s);

Overall generating IR(s) and disabling the Submit button is a  pre-submit stage. It forces collaboration between RMs and prevents a user from submitting an NUR that potentially could be rejected by other RM(s).

• System populates Draft IR on NUR1 against the affected RM;

• IR provides a Read Only access to NUR1 for RM2;

• RM2 can liaise with initiator (RM1) to ask for changes or removal prior to an Accept or Decline of the IR.

• The recording of the IR interactions between RM1 and RM2 will assist in future processes (where required, such as refer to the Road Authority).

• Regardless of the outcome of the IR (RM2 can Accept or Decline IR) RM1 would be able to submit NUR1;

Changes to existing Logic

• Currently IR is a plain text, we need action flag (Accept or Decline);

• On creating IR, an empty NUR2 in Draft state is spinned automatically to facilitate communication. We need to copy dual-managed segments into NUR2.

• NUR2 should be in view only mode, for this to work need to add properties to NUR model: isPrimary?: boolean, nurType?: ‘dualManage’ | ‘intersection’

Front-end tickets order:

Back-end tickets order: