| Key No. | Brief Description | Issue type |
| [RNE014-4211] | RFC KPI - Define KPI report DB table to store data for the report generation | Story |
| [RNE014-4212] | RFC KPI - Generate KPI data: prepare RFC KPI data for :
1. Offered capacity at
- X-11 + 1 - the calculations should be made based on PaPs intended for New Path Requests
- X-10.5 + 1 - the calculations should be made based on PaPs intended for New Path Requests
- X-2 + 1 - calculations should be made based on PaPs intended for Late Requests (Late Path Request, Ad-Hoc Path Request, Ad-Hoc Pre Accepted, Rolling planning)
2. Requested capacity at:
- X-8 + 1 - calculations should be made under dossiers that are using PaPs intended for New Path Requests
- X+12 + 1 - calculations should be made under dossiers that are using PaPs intended for Late Requests (Late Path Request, Ad-Hoc Path Request, Ad-Hoc Pre Accepted, Rolling planning)
3. Reserved capacity at:
- X-7.5 + 1 - calculations should be made under dossiers that are using PaPs intended for New Path Requests | Story |
| [RNE014-4214] | RFC KPI - Prepare KPI reports: generate reports from prepared RFC KPI data.
1. RFC Users: RFC user should be able to download available KPI reports for own corridor.
2. Admin users: admin users should be able to download available KPI reports for selected corridors | Story |
| [RNE014-4231] | RFC KPI endpoint: add support for a manual run of the task for RFC KPI data generation. | Story |
| [RNE014-4217] | Composite relation - define train number on composite dossier level (backend). The entered train number will be copied to every sub-path of the new dossier. This means that all path sections from all territories will have the same national train number. | Story |
| [RNE014-4218] | Composite relation - define train id on composite dossier level (backend). The user should be able to define train id (Company code and Core element) on the new composite relation dossier. | Story |
| [RNE014-4219] | Composite relation - replace popovers with new pages. Add/Edit composite relations will be shown on a new page. | Story |
| [RNE014-4220] | Composite relation - define train number on composite dossier level (frontend). Introduce train number input on composite relation dossier level. | Story |
| [RNE014-4222] | Composite relation - define train id on composite dossier level (frontend). The user should be able to define train id on composite relation dossier. | Story |
| [RNE014-4221] | Composite relation - redesign implementation- Stylize re-organized composite relation view. | Story |
| [RNE014-4233] | The dossier cannot be updated - WS 221 error. Fix of UNKNOWN_TRAIN_TYPE(221) web service error. Deskero ticket: https://rne.deskero.com/agent/ticket/view/60c9fe9ae4b04019be37a389 | Bug |
