RNE PCS Maintenance Table

Title Issue type Priority Taken in Patch Release System OTRS ticket nr.
PCS EC Sprint 18


     Jira No                 Brief description

  1. RNE014-2218 - [Dev] Edit train parameters step - checkbox with an intermediate state
  2. RNE014-2339 - [Dev] Copy Parameters from Template
  3. RNE014-2340 - [Dev] Save as a template
  4. RNE014-2404 - [Dev] Adding coordinating C-OSS to territory pair
  5. RNE014-2416 - [Dev] Integrate confirmation modals in all places
  6. RNE014-2418 - [Dev] Valdr for backend
  7. RNE014-2453 - [Dev] Observations
  8. RNE014-2511 - [Dev] Unify usages of Path section selection component
  9. RNE014-2597 - [UX] Copy Dossier
  10. RNE014-2620 - [Dev] Creating a user variant with PaP - Train parameters step
  11. RNE014-2621 - [Dev] Creating a user variant with PaP - Calendar step
  12. RNE014-2623 - [Dev] Inserting a PaP into a new sub-path - Train parameters step
  13. RNE014-2624 - [Dev] Inserting a PaP into a new sub-path - Calendar step
  14. RNE014-2634  - [UX] Fix dossier archives dropdown height
Story Major 24/12/2018
PCS EC Sprint 19


      Jira No                 Brief description​​​​​​​

  1. RNE014-2328 - [Dev] Warnings calculations and a preview of changes
  2. RNE014-2356 - [Dev] Replace IM with RU timetable
  3. RNE014-2372 - [Dev] UI view to display table with dossier archives
  4. RNE014-2415  - [Dev] Leave page handler
  5. RNE014-2439 - [UX] Compare view, layout and flipped path-section
  6. RNE014-2529 - [Dev] Adapt the model for EC
  7. RNE014-2633 - [UX] Train parameters styling issues
  8. RNE014-2635 - [Dev] Activity type code list update
  9. RNE014-2636 - [Dev] Push-Pull train field in common train params
  10. RNE014-2637 - [Dev] Multiple Train CC systems in traction entries
  11. RNE014-2639 - [Dev] Max Axle Weight minimum value
  12. RNE014-2643 - [UX] Compare view - timetable selection dropdown
  13. RNE014-2644 - [UX] Compare view - path section states
  14. RNE014-2646  - [Dev] Refactor confirmation modals with reason
  15. RNE014-2647  - [Dev] Copy Parameters from Template - finalize
Story Major 14/01/2019
PCS EC Sprint 20


      Jira No                Brief description

  1. RNE014-2555 - [Dev] Pap Request details view
  2. RNE014-2556 - [Dev] Pap Request Handling
  3. RNE014-2630 - [Dev] Loading of archived version
  4. RNE014-2642 - [UX] Path section in read-only: replace inputs with text fields to save space
  5. RNE014-2654 - Analyze architecture changes and improvements
  6. RNE014-2655 - Integrate schema draft version
  7. RNE014-2656 - Web services authentication
  8. RNE014-2657 - Web services test clean up
  9. RNE014-2660 - [Dev] Train composition - Cargo dossiers
  10. RNE014-2661 - [Dev] Pap Request details view - Implement header
  11. RNE014-2662 - [Dev] Pap Request details view - Pap request status legend
  12. RNE014-2663 - [Dev] Pap Request details - Show pap requests per user variant
  13. RNE014-2665 - [Dev] Pap Request details - pap request action selection
  14. RNE014-2670  - Fix train parameters copy destinations view
Story Major 28/01/2019
PCS EC Sprint 21


     Jira No                  Brief description

  1. RNE014-2559  - [Dev] Conflict resolution view - backend
  2. RNE014-2564 - [Dev] COSS acceptance indicators change
  3. RNE014-2604 - [UX] Pap Request details view
  4. RNE014-2616 - [Dev] Identifiers for entities that are not saved
  5. RNE014-2664 - [Dev] Pap Request details - Pap request status changes
  6. RNE014-2668 - [UX] Legend component
  7. RNE014-2676 - [Dev] Train composition (Cargo dossiers) - read-only mode
  8. RNE014-2677 - [Dev] Train composition (Cargo dossiers) - calendar on Train composition item
  9. RNE014-2678 - [Dev] Train composition (Cargo dossiers) - drag and drop of composition items
  10. RNE014-2680 - Reference data resolver refactoring
  11. RNE014-2682 - Dozer conversion consolidation
  12. RNE014-2687 - GetDossier operation check
  13. RNE014-2689 - [Dev] Sync dossier version in dossier context after dossier persistence
  14. RNE014-2690 - [Dev] Conflict resolution view - frontend - initial setup
  15. RNE014-2692 - [UX testing] Styling issues
  16. RNE014-2696 - [Dev] Bug fixing
Story Major 11/02/2019
The user address was not saved in the personal profile.

PCS NG version (prod, test 2, test 4, pcsschool, and taftsitest1)

Bug Minor 15/03/2018 2018031387000079
Calculate mandatory times flags when times are copied from RU to IM TT in FS

PCS NG version (prod, test 2, test 4, pcsschool, and taftsitest1)

Story Major 15/03/2018
Prevent NPE when validating agency parameters in case when RU agency in pair is changed.

PCS NG version (prod, test 2, test 4, pcsschool, and taftsitest1)

Bug Major 15/03/2018 2018030987000078
Restrict editing of loco type number, weight, length, cc systems and v-max for locos that are used in dossiers.

PCS NG version (prod, test 2, test 4, pcsschool, and taftsitest1)

Story Major 15/03/2018
TTP 2020 opened on production and school for IM parameters creation.

PCS NG version (prod and pcstest1, pcsschool, pcs-taftsitest1)

- Copy loco types to next timetable period corrected
- TTP 2020 IM params copy default values
- TTP 2020 auto promotion dates update

Story Major 05/11/2018
Predefined filters creation order corrected

PCS NG version (prod and pcstest1, pcsschool, pcs-taftsitest1)

Bug Major
Croation translations update

PCS NG version (prod and pcstest1, pcsschool, pcs-taftsitest1)

Improvement Minor 05/11/2018
Administration rest controller protected from unauthorized access

PCS NG version (prod and all test systems)

Story Major 29/06/2018 2018062687000094
PCS EC Sprint 22

       Jira No                  Brief description

  1. RNE014-2563 - [Dev] COSS Timetable editing
  2. RNE014-2565 - [Dev] Timetable ACL rules per agency type
  3. RNE014-2606 - [UX] Conflict resolution view - placeholder
  4. RNE014-2679  - [Dev] Train composition (Passenger dossiers) - backend adaptations
  5. RNE014-2684 - Additional EC schema changes
  6. RNE014-2688 - Deployment on pcstest3
  7. RNE014-2691 - [Dev] Conflict resolution view - frontend - finalize
  8. RNE014-2702 - Update dossier operation adaptations and check
  9. RNE014-2703 - Update operations resolving
  10. RNE014-2704 - Basic data validation - Update dossier
  11. RNE014-2706 - [Dev] Train composition (Passenger dossiers) - frontend - edit mode
  12. RNE014-2712 - Operation point repo queryForObject
  13. RNE014-2716 - [UX] Train composition - cargo dossier (styling issues)
  14. RNE014-2719  - [Dev] Train composition (Passenger dossiers) - additional fields
  15. RNE014-2725  - Calendar editing issues
  16. RNE014-2726  - [Dev] Reset store issues
  17. RNE014-2728  - Import loco types and params in pcstest3
  18. RNE014-2731  - Preparation for EC Testing
  19. RNE014-2734  - Define and edit sub-path title is not possible
  20. RNE014-2738  - Dossier ACL related issues
  21. RNE014-2740  - PaP cannot be opened in the search results
  22. RNE014-2756  - Add new territory
Story Major 25/02/2019
Prevent NPE when creating PAMT Report

Prevent Null Pointer Exception when creating PAMT Report , in case when pap request archive is empty.

Bug Major 25/04/2018
(Infrabel) 302 for dossier 478502 pcstest2

Loco types in the dossier are from previous ttp, during copying of dossiers to next ttp the loco types are not resolved.

Bug Major 25/04/2018 2018042387000031
(SNCF) No agency notifications received in past several months Story Major 2018022387000098
Not able to return capacity to IMs

When user was trying to manually return capacity NO_CHANGES found was thrown when PCS System was trying to persist CT Dossier -> Solution: force new version when CT dossier is being saved in RFC capacity return process

Story Major 02/05/2018 2018042487000065
Dwell time validation - take into account midnight crossing
  • During the migration of dwell time from string to number validation was not check (dwell time should be less than the difference between the departure and the arrival times) -> as a result of that there are dossiers with an invalid dwell time
  • fix affected path sections from RU/COSS TTs
  • fix dossiers that were not fixed by Mate
Story Major 09/05/2018 2018042987000011
Imported Czech translations Story Minor 09/05/2018 2017121187000094
GDPR implementation and password enhancements

PCS NG version (prod and all test systems)

GDPR acceptance page

PCS user accounts are created upon RNE OTRS request by the RNE support team. The first time they login in PCS instead of being redirected to the dashboard they should be redirected to the GDPR acceptance page.

The page shows two checkboxes (unchecked by default) with the following text:

  • I have read the RNE privacy notice and agree to the processing of my personal data by RNE according to the GDPR (General Data Protection Regulation).
  • I agree that RNE can send to my email address the PCS Newsletter. You can withdraw your agreement at any time. In this case please contact us at support.pcs@rne.eu.

The first checkbox must be checked in order to be able to proceed or access any other PCS page. Once checked an 'I agree' button becomes enabled. Upon clicking on 'I agree' the system should store the current date and time in RNE_GDPR_ACCEPTED_DATE and update PCS_NEWSLETTER_SUBSCRIPTION to 1 if the second checkbox was checked.

Ask for password change after GDPR acceptance

It should be a separate step dependent on separate fields. The password change shows up if last login date is null and the GDPR page shows up if acceptance date is null.

Password hashing algorithm improvement

Because we will ask all users to change their password we should take advantage to improve the security of the passwords. New encryption is applied and minimum length too (6 digits).

Story Major 12/06/2018
Reset locoIdents in case when operation point is changed with different responsible agency

PCS NG version (prod and all test systems)

When adding path sections on the border parameters are copied from next/previous path section.Loco from neighbouring IM is copied and silently saved.

Bug Major 12/06/2018 2018042587000072
Web services returned 302 for dossiers with composite relations

PCS NG version (prod and all test systems)

Bug Critical 12/06/2018 2018051787000111
PCS IP progress status update error

PCS NG version (prod and all test systems)

The updateDossierRUIMPair requests of SNCF Réseau contained only their pairs. Because of this, PCS reconstructed the pairs after the update and with this the lights of the others were set again to blue and dossier level parameters were deleted.

The issue was fixed, the lights and the parameters were restored to the previous stage.

Bug Critical 20/06/2018
(SNCF) Web service errors in prod

PCS NG version (prod and all test systems)

SNCF Réseau tried to update their dossiers. The analysis showed two issues related to the connections and composite relations element. The others were issues among the dwell time and IM parameters.

Story Major 20/06/2018 2018061587000061
OP fields empty in PDF exports

PCS NG version (prod and all test systems)

We've got the information from MÁV-START that the operation point fields are empty in the PDF exports. You can take a look on the attachment, it's the part of the train composition of the dossier 186444 from prod (mav-p).

It would be great to have a fix before the FTE C/D Conference (3-5 July).

Bug Critical 29/06/2018
Validation of loco type number via web service

PCS NG version (prod and all test systems)

Bug Major 29/06/2018 2018061487000081
PCS EC Sprint 1


       Jira No.              Brief description

  1. RNE014-1946  Project setup 
  2. RNE014-1947  [UX] Component: Input (basic + read-only) 
  3. RNE014-1950  [UX] Component: button (default, primary, link, w/(o) icon) 
  4. RNE014-1960  [RE] Wireframe: Update existing EC wireframes with new terminology 
  5. RNE014-1968  [RE] Wireframes: Entry of TSI Variant Identifiers 
  6. RNE014-1969  [RE] Wireframes update: Copy parameters Wizard 
  7. RNE014-1973  Backend: upgrade to Girders 4, upgrade other libraries 
  8. RNE014-1974  [UX] General: create basic helper styles (variables, mixins, fonts, icons) 
  9. RNE014-1984  [UX] Add lint rules for scss 
Story Major 02/04/2018
PCS EC Sprint 2


        Jira No.                 Brief description

  1. RNE014-1948 - [UX] Component: select-single (basic and readonly)
  2. RNE014-1951 - [UX] Component: button-toggle (on/off button)
  3. RNE014-1953 - [UX] Component (Path): operation-point
  4. RNE014-1955 - [UX] Component (Path): path-section-times
  5. RNE014-1956 - [Dev] Component: input-time (basic + readonly)
  6. RNE014-1957 - [UX] Component (Path): path-section
  7. RNE014-1961 - [RE] Dossier editing by IM
  8. RNE014-1963 - [Web Services] schema changes v.6, migration guide
  9. RNE014-1967 - [UX] Component: select-multi (basic and readonly)
  10. RNE014-1972 - [UX] Component: text-field
  11. RNE014-1975 - [UX] General: Layout component
  12. RNE014-1976 - [UX] General: header & footer components
  13. RNE014-1977 - [UX] General: side menu component
  14. RNE014-1982 - [UX] Component: date-picker
  15. RNE014-1992 - [Dev] Component: button-press (on/off button)
  16. RNE014-1993 - [Dev] Component: accordion
  17. RNE014-1994 - [Dev] Component: select-multi (basic and readonly)
  18. RNE014-1995 - [Dev] Component: select-single (basic and readonly)
  19. RNE014-1998 - [Dev] Component (Path): operation-point
  20. RNE014-1999 - Adjust Javers tests
  21. RNE014-2000 - Flyway (latest version)
  22. RNE014-2001 - Fix warnings for deprecated fields
  23. RNE014-2002 - Check WS endpoint
  24. RNE014-2004 - Use getMapping/postMapping in REST controllers
  25. RNE014-2006 - Check email templates and exports
  26. RNE014-2008 - Adjust the trasse model
  27. RNE014-2009 - Adjust the trasse element
Story Major 23/04/2018
PCS EC Sprint 3


       Jira No.              Brief description

  1. RNE014-1949  - [UX] Component: checkbox (basic and read-only)
  2. RNE014-1954  - [UX] Component (Path): pap-header
  3. RNE014-1971  - [UX] Component (Path): sub-path
  4. RNE014-1996  - [Dev] General: Layout component
  5. RNE014-2003  - Healthcheck actuator
  6. RNE014-2005  - Move login to the frontend
  7. RNE014-2007  - Initial test deployment on the extranet
  8. RNE014-2012  - Service for subpath splitting
  9. RNE014-2038 - [Dev] Component: input-time-options
  10. RNE014-2039 - [UX] Component: input-time-options
  11. RNE014-2043 - [UX] Component: wizard and wizard steps
  12. RNE014-2044 - [Dev] Component: wizard and wizard steps
  13. RNE014-2046 - [UX] Component: dossier basic data
  14. RNE014-2049 - [Dev] Upgrade to girders4 - review pull req. comments
  15. RNE014-2050 - [Dev] Valdr validation service
  16. RNE014-2051 - Refactor components to work with RxJS
  17. RNE014-2052 - Adjust bootstrap of frontend app
  18. RNE014-2055 - [UX] Input fields validation
  19. RNE014-2056 - [Dev] Valdr validation on frontend evaluation
Story Major 07/05/2019
PCS EC Sprint 4


Jira No              Brief description 

  1. RNE014-1952 - [UX] Component: accordion
  2. RNE014-2014 - [Dev] Revise RU/IM pair resolving
  3. RNE014-2019 - GraphQL proof of concept
  4. RNE014-2045 - [Dev] Component: dossier basic data
  5. RNE014-2072 - [UX] Login page style
  6. RNE014-2073 - [Dev] RU Timetable step
  7. RNE014-2077 - [UX] pcs-mandatory input
  8. RNE014-2078 - [Dev] pcs-mandatory input
  9. RNE014-2084 - [UX] Sub-path selection component
Story Major 21/05/2018
PCS EC Sprint 5


Jira No              Brief description

  1. RNE014-2010 - Define the createDossier presentation model
  2. RNE014-2074 - [Dev] Dossier-level data step
  3. RNE014-2075 - [UX] Dossier-level data step
  4. RNE014-2079 - [UX] RU Timetable step
  5. RNE014-2080  - [Dev] input parameter types
  6. RNE014-2081 - [Dev] valdr frontend integration
  7. RNE014-2082 - [UX] valdr frontend integration
  8. RNE014-2083 - [UX] Calendar html presentation
  9. RNE014-2093  - [Dev] Sub-path selection component
  10. RNE014-2101  - [UX] Sub-path step
  11. RNE014-2103  - [Dev] Adjust presentation model for IM parameters on path section level
Story Major 04/06/2018
PCS EC Sprint 6


      Jira No                Brief description

  1. RNE014-2047 - [Dev] Component: Move and adjust code for Outline from prototype
  2. RNE014-2076 - [Dev] Timetable data validation
  3. RNE014-2094 - [Dev] Edit train parameters step
  4. RNE014-2096 - [UX] Edit train parameters step - copy options
  5. RNE014-2097 - [UX] Edit train parameters step
  6. RNE014-2100 - [Dev] Sub-path step
  7. RNE014-2104 - New dossier creation endpoint
  8. RNE014-2107 - [UX] Calendar html presentation - colors + tooltip
  9. RNE014-2120 - [Dev] Calendar wizard step
  10. RNE014-2121 - [UX] pcs-ec Layout: Header/Content/Footer
  11. RNE014-2137 - [Dev] Path section selection component
  12. RNE014-2138 - [Dev] Adjust TrainParameters presentation model and converters
  13. RNE014-2140 - [Dev] Keep dictionaries in service, instead of store
  14. RNE014-2143 - [Dev] Use GraphQL in Dossier Level Data step
  15. RNE014-2150 - [UX] IM parameters layout
  16. RNE014-2157  - Presentation model for Agency, new dictionaries rest
Story Major 18/06/2018
PCS EC Sprint 7


      Jira No                  Brief description

  1. RNE014-2013 - Service for calendar switching
  2. RNE014-2015 - Remove mandatory input flags on RU/IM pair and dossier agency level
  3. RNE014-2102  - EC domain model changes
  4. RNE014-2122 - [Dev] Dossier side menu
  5. RNE014-2141  - [Dev] Adjust PathSection presentation model and converters
  6. RNE014-2144 - [Dev] Use GraphQL in Sub-Paths step
  7. RNE014-2147 - Changes in DossierRUIMPairModel
  8. RNE014-2148 - Changes in TrasseModel
  9. RNE014-2149 - [Dev] Use GraphQL in Calendar step
  10. RNE014-2169 - [UX] Fix minor presentation issues with the wizard (overall task)
  11. RNE014-2170 - [Dev] Use GraphQL for train parameters
  12. RNE014-2171 - [Dev] Train parameters step - keep selected path section in the store
  13. RNE014-2185  - [UX] Calendar html element refactoring
Story Major 02/07/2018
PCS EC Sprint 8


      Jira No                  Brief description

  1. RNE014-2011 - Service for creating dossier from dossier draft
  2. RNE014-2098 - [Dev] Edit train parameters step - copy destinations
  3. RNE014-2099 - [UX] Edit train parameters step - copy destinations
  4. RNE014-2115 - JWT authentication for rest services (pcs-ui)
  5. RNE014-2116 - Prepare deployment for pcs and pcs-ec
  6. RNE014-2117 - Use dashboard from pcs
  7. RNE014-2118 - Dossier links from dashboard should go to EC
  8. RNE014-2119 - Hide other parts from the menu (show only Dashboard)
  9. RNE014-2125 - [Dev] Sub-paths geography view (read-only mode)
  10. RNE014-2130 - [Dev] Sub-paths calendar view (read-only and edit mode)
  11. RNE014-2136 - [Dev] Select and use already existing draft (min version)
  12. RNE014-2159 - Pcs User account GDPR
  13. RNE014-2164 - [UX/Dev] Investigate usage of deep selectors in components
  14. RNE014-2167 - [Dev] Sub-paths geography view (edit mode)
  15. RNE014-2173 - [UX] Wireframe for TT combinations (DB Cargo algorithm vs. as it is today)
  16. RNE014-2191 - [Dev] Timetable resolvers and converters
  17. RNE014-2193 - [Dev] Train parameters compact read-only view
  18. RNE014-2194 - [UX] Train parameters compact read-only view
  19. RNE014-2195 - [UX] Transfer dossier wizard buttons into a component
  20. RNE014-2196  - [UX] Fix issues in the dossier wizard
  21. RNE014-2217  - pcs-online -> pcstest3 db import
  22. RNE014-2220  - TrainId company code is not shown in basic data
  23. RNE014-2221  - [UX] Dossier view - make it pretty
Story Major 16/07/2018
PCS EC Sprint 9


       Jira No                 Brief description

  1. RNE014-1997 - [DEV/UX] icon font generator
  2. RNE014-2053 - Migrate app to Angular 6
  3. RNE014-2168 - [DEV] Select and use already existing draft (proper version)
  4. RNE014-2172 - [DEV] Train parameters step - loco idents
  5. RNE014-2198 - [DEV] Do not show the input fields in read-only mode
  6. RNE014-2200 - [DEV] Single-select should not be case sensitive
  7. RNE014-2214 - [DEV] TrainParameters conversion refactoring and copy service
  8. RNE014-2223 - [UX] Create tabs component
  9. RNE014-2224 - [DEV] Create tabs component
  10. RNE014-2226 - [UX/DEV] Fix the read-only state of inputs/selects in firefox (color + not selectable)
  11. RNE014-2227 - [DEV] Remove the tabs when creating new sub-path from geography view
  12. RNE014-2228 - [DEV] Select component show a complete list of properties
  13. RNE014-2229 - [DEV] Dossier wizard cancel buttons are not functional
  14. RNE014-2231 - [DEV] Dossier wizard - last continue should be renamed to Create a dossier
  15. RNE014-2232 - [DEV] Dossier wizard navigation - support multiple sub steps
  16. RNE014-2234 - [DEV] Dwell time validation for the number on UI, check backend validation
  17. RNE014-2235 - [DEV] Geography view show train parameters
  18. RNE014-2236 - [DEV] Rename ref. point to construction and make sure it is saved
  19. RNE014-2237 - [DEV] Sub-paths editing check all fields are saved properly
  20. RNE014-2240 - [UX] Dossier draft selection (w/o) grid
  21. RNE014-2245 - [DEV] Remove "fix" controllers and converters that are not used anymore
  22. RNE014-2247 - [DEV] Dossier Wizard implement the creation of User Variants
  23. RNE014-2248 - [DEV] Geography implement Create New User Variants
  24. RNE014-2249 - [UX] Select - limit the width of the list
  25. RNE014-2251 - [UX] Tabindex (and shift + tab for select component) in Firefox
  26. RNE014-2252 - [DEV] remove submit functionality from time input
  27. RNE014-2253 - [UX] Wizard look small adjustments
  28. RNE014-2254 - [UX] Path-section icon - train for RU and/or rail for IM for the construction point (change the bell)
  29. RNE014-2256 - [DEV] translate button titles
  30. RNE014-2257 - [DEV] backspace in times input in firefox
  31. RNE014-2259 - [DEV] Add IM agency in territory title with short names
  32. RNE014-2261  - [UX] Dossier header information
  33. RNE014-2262  - [UX] Add full text for read-only input fields in tooltip
Story Major 06/08/2018
Bug fix for adding new PAPs in Combined pap dossier

Bug fix for adding new PAPs in Combined pap dossier; set origin corridor catalogue id in path sections w/o capacity in alternative offer for combined PAP dossier.

dossier id: 191140


  • PaP removed from Main and again added to dossier resulted in not cleaning up catalogue flags
  • affected dossiers: 191282, 191511, 191884

What was done:

  • catalogue flags from main TT cleared 
  • pap request and pap request related data (requested locations, pap request archive, pap request conflict archive) removed 
  • state of the dossier fixed 
Bug Major 04/04/2018
Mandatory common parameters flag for IM timetable was wrongly set


Wrong setter was used for IM missing mandatory common parameters

Approx. number of affected dossiers:

-- Harmonziationa: 191845, 191933, 191985, 192013, 190521, 192144, 192136, 190283, 190974, 191564, 190146, 190147, 190497, 191124, 190615, 192110, 192142, 190282, 191932, 191952, 192020, 190489, 192063, 191922, 190148, 192021, 190799, 192118, 190826, 190821, 190498, 191841, 191512, 191966, 191846, 190820, 190819, 191931, 191938, 191983, 192045, 192126, 191030, 190264, 190722, 191934, 191783, 192145, 191937, 191973, 191129, 191623, 191923, 191633, 191950, 191511, 191901, 192121, 190181, 190163, 190102, 192148, 192005, 192007, 192041, 191943, 192128, 191967, 192052, 191968, 191963, 191972, 191971, 191884, 191961, 191206, 192047, 191962, 192119, 191123, 192135, 190262, 192064, 191722, 192061, 192093, 191579, 191580, 192044, 192062, 192138, 191886, 192096, 188825, 190648, 192116, 191965 -- Harmonization Conference: 186270, 186399, 186400, 186828, 186886, 186403, 184189, 189962, 184179, 189945, 186402, 192169, 189946, 185396, 186839 select DISTINCT drip.dossier_id from DOSSIER_RUIMPAIR drip where drip.DOSSIERSTATUS_ID in ('C', 'Q') and drip.IM_PARAMS_WARNING = '1' and EXISTS (SELECT * from TRASSE where agencytype_id = 'KM') and (drip.STAMP like '2018-03-29%' or drip.stamp like '2018-03-28%');

dossiers where version was made:

  • leading RU [2060]: 190147, 190163, 190181, 190183, 190258, 190259, 190262, 190263, 190264, 190282, 190283, 190286, 190287, 190489, 190497, 190498, 190722, 190819, 190820, 190821, 190974
  • leading RU [2320]: 190102, 190799
  • leading RU [216]: 192093, 192116
  • leading RU [3480]: 192005
  • leading RU [780]: 192061
  • leading RU [16]: 190615,191030,191968,192020,192021,192047
  • leading RU [19]: 191123, 191124
  • leading RU [196]: 191886,191922,191923,191934,191938,191943,191961
  • leading RU [1700]: 191801,191802
  • leading RU [120]: 191511,191901,191932,191952,191971
  • leading RU [189]: 185396
  • leading RU [120]: 192169
  • leading RU [194]: 189962
  • leading RU [2840]: 186839
  • leading RU [24]: 184179,184189,186270,189946
  • leading RU [2]: 186399, 186400, 186402, 186403,186828, 186886
Bug Major 04/04/2018
Empty calendar was checked only on the main timetable reference point

Empty calendar was checked only on the main timetable reference point. Now it is checked in every timetable.

Bug Major 04/04/2018
Email notification subscription - indicate agency type

Add the affected agencies in brackets in the notification settings. Because we show there every notification for everybody, but an IM will never get an e-mail the harmonization was released. Just simply add an explanation like this:

  • Path Request submitted (IM)
  • Report generated (All)

If possible it is better to filter the notifications according to the type.

Story Major 04/04/2018
Enable the possibility COSS to remove intermediate path section which is marked as reference point.

Enable the possibility C-OSS to remove intermediate path section which is marked as reference point.

Story Major 04/04/2018
Redesign of PCS Workflow Process Improvement Major 04/04/2018
Dwell time validation and constraints

Dwell time should have a standard format defined in minutes and should be taken into account when validating times.

Also, implement in WS, and create a different error code.

We are checking only on one path section if the dwell time is lower than the difference between arrival and departure times. Checked only if both times are entered.

We do not validate the value unless both arr and dep times are entered.

Story Major 04/04/2018
IM Timetable editing in Observations

Allow IM's to edit their timetable in Observations phase. 

Test cases covered:

  • create dossier, edit IM timetable in Observation, pass the dossier through the phases until Active Timetable reached
  • create dossier with paps, edit IM timetable in Observation, pass the dossier through the phases until Active Timetable reached
  • create adhoc dossier, edit IM timetable in Acceptance, pass the dossier through the phases until Active Timetable reached
  • create ad-hoc dossier with pap, edit IM timetable in Acceptance, pass the dossier through the phases until Active Timetable reached
Story Major 04/04/2018
Dossier close in later phases, autopromotion

The following transitions should be added:

Observations/Final Offer -> RU should be able to close the dossier

Observations/Final Offer -> background promotion if traffic lights of all RUs are red -> close the dossier

Post Processing -> IM/COSS should be able to close the dossier

This doesn't result in new dossier statuses, but new process steps will be implemented.
For dossiers that use capacity we do nothing, we don't return capacity or clean catalogue flags.

In the meantime automatic dossier promotion will be also added:


Until start of the current timetable period PCS should check every night and close every dossier where all the lights are red.
Today until mid September PCS checks every night and promote every dossier to Active Timetable where all the lights are green. Change this also to the start of the current timetable period.

For Ad-hoc

Promotions should run nightly throughout the year. It should promote everything to Closed when all lights are set to red, only from Acceptance and Final Offer phase.

Story Major 04/04/2018
PaP capacity handling in Path Elaboration

In the self-correcting function that update NR capacity the pap requests from C-OSS timetable should be considered.

Story Major 04/04/2018
C-OSS TT common and IM train parameters editing

C-OSS TT common and IM train parameters editing. Allowed editing of common and IM train parameters for coss users; added coss flags for missing mandatory times and operation point; prevented editing of common and IM train parameters on intermediate path section.

Currently, C-OSS users can edit common train parameters only for path sections that belong to an Alternative Offer Pap.

It should now be possible for C-OSS to always edit parameters see RNE014-1877. 

With the ACL in place, this should already work. It should be checked and the editing should work for IM parameters too.

Story Major 04/04/2018
C-OSS TT editing times validation

C-OSS users will be able to change times of Flex pap path sections but with some restrictions. The reason for this is that the calendar of the timetable cannot be changed by C-OSS users.

New error message upon TT Save action:

In order to avoid the need for recalculation of the calendar a validation should be performed: the change of times in a path section should not create (additional) offset with:

  • adjoining Pap path sections: An error message should be displayed: "The times of path section <Op. point name> does not conform to the running days in adjoining Pap sections".
  • in the same Pap section: An error message should be displayed: "The times of path section <Op. point name> does not conform to the running days in this Pap section".

New warning message upon TT Save action:

When the change in times will lead to (additional) offset against the adjoining F/O/IFO path sections an ACTION_REQUIRED type of error message should be shown: "The times of path section <Op. point name> does not conform to the running days in adjoining path sections <F/O/IFO op. point name>. Should the times in the path section be cleared?". If the user confirms the times of the adjoining F/O/IFO path sections will be cleared.

Test cases

  • (case1.png) PS7: 01:15 -> 02:45 (offset removed) -> error message
  • (case1.png) PS13: 00:05 -> 23:55 (offset removed) -> error message
  • (case1.png) PS7: 01:15 -> 13:13 (create offset in adjoining Pap) -> error message
  • (case1.png) PS5: 01:30 -> 00:03 (offset with PS4 - Feeder) -> warning message (times in PS4 will be removed)
  • (case2.png) PS5: 02:55 -> 23:45; 03:00 -> 23:48; PS6: 04:00 -> 23:50; PS7: 06:00 -> 23:55 -> error message - new offset is involved with adjoining pap
  • (case2.png) PS5: 02:55 -> 23:25; 03:00 -> 23:30; PS6: 04:00 -> 23:40; PS7: 06:00 -> 23:45 -> error message  - new offset is not involved, because it's still the same day
  • (case2.png) PS7: 06:00 -> 06:20 (offset with PS8) -> warning message (times in PS8 will be removed)
  • (case2.png) PS7: 06:00 -> 08:00 (offset with PS8, PS9, PS10) -> warning message (times in PS8, PS9, PS10 will be removed)
  • (case2.png) PS11: n/a -> 07:10 (offset with PS9 (departure), PS10) -> warning message (times in PS9 (departure), PS10 will be removed)
  • (case2.png) PS12: n/a -> 23:05 (offset with PS13 (arrival)) -> warning message (times in PS13 (arrival) will be removed)
Story Major 04/04/2018
TT warnings about duplicated arr/dep times on borders
  1. In the case where a border path section is duplicated with exact same operation point and arr/dep times and different IM agency is responsible than midnight crossing offset is not calculated.
  • (to be checked if it has to be the exact same OP) -> the rule is applied for borders, it should not be exact same OP
  1. The same should be implemented for interchange (handover) points.
  2. Additionally, a warning should be placed on the offset for potential inconsistency (such as duplicated arr/dep times) even in case where there is no responsibility change (no border/handover). 

The goal is to avoid offset changes especially in dossiers with Pap's that can later be corrected neither by C-OSS nor by IM's.

Example dossier id: 177803, agency: db-nz. Manual offset is used in this case to cancel out the auto generated offset.

Story Major 04/04/2018
Reset of Coss acceptance indicators

RFC traffic lights should be reset when Path Elaboration is released and Final Offer is submit so they have chance to check the offer.

Story Major 04/04/2018
Pap Alternative offer workflow configuration

Alternative Offer Workflow phases

Add to DossierStatus enum and review existing enum utility methods for impact.

The following Dossier Statuses should be created:

Alternative Offer Reserved (AS)

The dossier with this status has Alternative Pap inserted in the C-OSS timetable that should be accepted by impacted RU's. In this phase the the C-OSS have edit access to the C-OSS timetable.

Alternative Offer Created (AE)

In this phase the the C-OSS have edit access to the C-OSS timetable.

Alternative Offered (AF)

C-OSS promotes the dossier to this phase once the changed C-OSS timetable is ready to be sent to the RU's for acceptance of the modified Path Request. 

Alternative Offer Accepted (AA)

The modification to the Path Request has been reviewed and accepted by impacted RU's and has been promoted by leading RU.

Alternative Offer Rejected (AR)

The modification to the Path Request has been reviewed and rejected by one of the impacted RU's and has been promoted by leading RU.


C-OSS transitions

  1. Pre-Booking -> Alternative Offer Reserved
    1. not available in Control, triggered by Alternative Pap selected by C-OSS user
    2. handler: update pap requests status to ALTERNATIVE_RESERVED
  2. Pre-Booking -> Alternative Offer Created
    1. no changes to C-OSS traffic lights
    2. no changes or conditions against pap request status
  3. Withdraw Alternative Offer: Alternative Offer Reserved -> Pre-Booking
  4. Withdraw Alternative Offer: Alternative Offer Created -> Pre-Booking
    1. reset C-OSS lights
    2. handler: withdraw to pre-booking dossier version
  5. Proceed to Pre-Booking: Alternative Offered Accepted/Rejected -> Pre-Booking
  6. Submit Alternative Offer: Alternative Offer Reserved -> Alternative Offered
    1. reset impacted RU traffic lights
    2. condition: all pap requests in status of category Reserved
    3. handler: change pap request status to ALTERNATIVE_OFFERED
  7. Submit Alternative Offer: Alternative Offer Created -> Alternative Offered
    1. reset impacted RU traffic lights
    2. handler: change pap request status to ALTERNATIVE_OFFERED

RU Transitions

  1. Accept Alternative Offer: Alternative Offered -> Alternative Offer Accepted
    1. conditions: all RU traffic lights on red or green
    2. handler: update pap requests status from ALTERNATIVE_OFFERED to ALTERNATIVE_ACCEPTED
  2. Reject Alternative Offer: Alternative Offered -> Alternative Offer Rejected
    1. conditions: all RU traffic lights on red or green
    2. handler: update pap requests status from ALTERNATIVE_OFFERED to ALTERNATIVE_REJECTED, PapRequestAgencyStatusModel is not needed anymore and should be removed
Story Major 04/04/2018
Pap Alternative offer branch in Control view

Adaptation of the Control view to work with the Alternative offer branch phases.

Story Major 04/04/2018
C-OSS Dashboard - Selection of Alternative PaP

The phases for the Alternative Offer branch of the workflow are elaborate in  RNE014-1881.

The selection of Alternative Pap option will remain in Pap Request Details view. The reason for this is that the action depends on selecting a particular Pap that is in the dossier to be replaced by another pap i.e. the Alternative Pap, which means it cannot be reduced to simply initiating a transition via Control view.

The process will remain the same except that the action of selecting and inserting of Alternative Pap in the dossier should also trigger a workflow transition to Alternative Offer Reserved phase.

Story Major 04/04/2018
PaP Alternative offer timetable times validation

New error messages are introduced related to C-OSS TT editing.

The same logic and errors should be applied when selecting a Pap for Alternative offer.

  • If the calendar of the alternative catalogue is different than the calendar of the old catalogue then the times of feeder and outflow path sections should be removed
  • Otherwise, the cossTimetableTimesEditingWarningService is used to decide which times should be removed

Also, the calendar for the alternative should be calculated in the following way:
Leave the time as is, shift the time of the alternative path section one day earlier and one day later. Then calculate the difference between old path section arrival/departure time and those 3 times. Get the minimum difference and shift the calendar accordingly. If the minimum is calculated with the time one day earlier, then the calendar should be shifted one day earlier. If it is calculated with the time one day later, then the calendar should be shifted one day later. Otherwise, the calendar should be same as the old calendar.

When there is a change in the calendar or in the offset, some of the path section times should be removed because the calendar must not be changed. But in order for the times to be removed, the user must confirm the action. 
When ACTION_REQUIRED validation exception is thrown, show a modal dialogue to the user with the following message: "The times of path section <Op. point name> does not conform to the running days in adjoining path sections <F/O/IFO op. point name>. Should the times in the path section be cleared?". If he confirms the action then remove the times.
This should be implemented for Alternative Reservation and Coss timetable editing.

Story Major 04/04/2018
PaP Alternative offer for C-OSS TT editing

The new Alternative offer branch in the workflow for dossiers that use Pap capacity will be applied also in the case where C-OSS timetable is changed (times, parameters) without inserting Alternative Pap.

C-OSS user will trigger the workflow in Control view by switching the dossier to Alternative Offer that has the status Alternative Offer Created. In this phase the C-OSS.

The configuration of ACL rules for the editing should be configured with task. Here the editing should be fully verified for both phases.

Story Major 04/04/2018
PaP Alternative offer - RU acceptance

Currently, when Alternative Offer is sent to the RU's they are notified by email with a link to a specific view for alternative offer comparison where they can see a comparison between the RU and IM main timetables and can take an action to accept or reject it. The status of their decision is kept per pap request in PapRequestAgencyStatusModel. 

Now, this should be handled via Control. The RU can find the dossiers under 'My Unresolved' filter as the status of the alternative offer acceptance will be handled with the traffic light. 

The view for comparison will be kept but it will not offer any action. Each involved RU in the Alternative offer will instead need to set their light to green for accepting or red for rejecting the alternative offer. Once all lights are green the leading RU can promote the dossier to Alternative Accepted. In the case of at least one light set to red the leading RU can promote the dossier to Alternative Rejected.

Test cases that should be considered (with single/multiple RUs involved in the alternative pap):

  • check if the dossier with the alternative offer is under 'My Unresolved' filter  
  • the view for comparison should not offer any action  
  • check whether the conditions for acceptance an alternative offer apply (all RUs have green lights)  
  • check whether the conditions for rejecting an alternative offer apply (at least one RU has red lights)  
Story Major 04/04/2018
Alternative Offer - reset acceptance indicator only for affected RUs

Alternative Offer - reset acceptance indicator only for affected RUs

Story Major 04/04/2018
C-OSS Dashboard - Undo Alternative Offer reservation

Withdraw option from Alternative Offer Reserved / Created phases. It should be analysed more exhaustively but briefly, these points should be handled.

Alternative Offer Reserved

The C-OSS timetable should be replaced with the one from the first version in Pre-booking phase. This means that the original Pap(s) should be inserted in the dossier again and all pap request should be re-requested (for LPR / AdHoc re-reserved). The state might be different in case initial Pap is not available anymore. This option does not exist currently. If several consecutive Alternative Offer loops withdrawing to Pre-booking might potentially lead to confusing results where all Pap's will be in waiting for alternative status.

Alternative Offer Created 

There should be no changes in pap requests and reserved capacity, only the C-OSS timetable should be replaced with the one from the first version in Pre-booking phase.

If the Alternative Offer is withdrawn from Alternative Offered, the RU should receive a withdraw notification mail.

Test cases covered:

  • withdraw from alternative offer reserved and original pap is inserted in the dossier  
  • withdraw from alternative offer created 
  • withdraw from alternative offered 
Story Major 04/04/2018
(DB-Netz) Loco type value is blanked when copying parameters

Option to copy loco types was applied only to the loco type fields. It is now related to copying the entire loco ident entry. A separate message is shown now when train max and planned speed are higher than the allowed value according to the targets loco type and loco type copy option is not selected. The message now indicates that the copying is not possible because of incompatible loco ident train parameters, previously it was showing the catalogue incompatibility message.

Story Major 28/02/2018 https://ts.railneteurope.info/otrs/index.pl?Action=AgentTicketZoom;TicketID=72708#118190
Copy parameters modal dialog did not show up for intermediate path sections Bug Major 28/02/2018 https://ts.railneteurope.info/otrs/index.pl?Action=AgentTicketZoom;TicketID=72754
Switch to Partial Harmonization improvement

- acceptance of GTC is not requested for non pcs members  
- switch to Partial Harmonization is disabled when there are non-PCS member agencies involved

See: https://cms.rne.eu/node/537

if there is non-PCS member agency in dossier switching to partial harmonization should be disabled (All process types)

To do:

add condition AllPathSectionsHavePcsMemberResponsibleAgency

use that condition in workflow configurers

Improvement Major 28/02/2018