Version 2.8.1 Changes



2020.11.20 PCS EC version 2.8.1 was deployed on production, test1, test4.

WS 6.1 was deployed.


  • Fixed styling issues for underlined items in the header menu
  • Added path section selection component into the Calendar Step
  • Fixed the error in add subpath view
  • Fixed incorrect time formatting in the path section
  • Update the schema version to 6.1 and removed old versioning support
  • Remove WS operation point - update operations
  • Loco type structure - adjust loco types in web services(import, update, delete and search)
  • Loco type WS operations - get reference data (import, update, delete, and adjusted getActivity types)
  • Activity types - carry forward of dossiers
  • Resolve correct activity type during the process of dossier carry forward
    • Try to map activity types for TTP with the one from TTP +1 using the code and agency.
    • In case of invalid activity types, give the option to the user to resolve them (to choose the valid one)
    • Introduce the activity type step in the carry forward wizard
  • Grid customization - column reordering and resizing in the grid library and on the dashboard
  • Previous/Next button dossier sort order. The defined sort order will be kept when the user navigates with the previous/next dossier buttons.
  • Automatic update of the calculation for train length/weight
  • Slimmer outline
  • Automatic update of the calculation for train length/weight. Train parameters will be re-grouped. A weight-length section will be created and the pre-calculation option will be added there. In case of an update in the traction details, PCS will automatically update the train weight and length fields. The re-calculation won't work for train max speed.
  • Copy dossier in PA/PM
  •  Fixed sort ordering of subpaths. The user will be able to change the sort order of the sub-paths and save this change. This option will be available in the geography view.
  •  Show sub-path information during train parameter editing
  •  Copy dossier with an inverted timetable and with clear path numbers. We will invert and copy the territories, sub-paths with their locations and all the parameters. Alternative origins will become alternative destinations. Origin of each sub-path will have default departure time 00:00 and as default calendar will be set the first day of timetable period.
  • Show sub-path information during train parameter editing. Sub-path information will be added to the train parameters editing view with its: title, validity period, circulation days pattern, just like in the territory view. This information will be available in: sub-path train parameters editing, add sub-path with PaP and add PaP in already existing sub-path.
  • Replace tailor-made points with PaPs. When a user wants to add a new PaP in an already existing subpath, the user should click on the "Add PaP" button in geography view and then be redirected to PaP Search to find the PaP. After that, the user will be navigated to the wizard where the first step is "Reorder PaPs", where the user will have the chance to reorder. The next step is "Sub-Path". Here the user will be able to add/remove Feeder, Outflow, Intermediate locations, remove locations from inserted PaPs, remove whole PaPs or make locations from PaP as tailor-made. From this step, the user will be able to click "Save" or to continue through the wizard as today. If the user clicks "Save" in case of not available days, a timetable preview will be shown, where the user will be able to save the sub-path or cancel the action. If all days are available, the preview will not be shown.
  • Mark the copied parameter: Parameters that are selected to be copied will be highlighted.
  • Responsible RU/IM in path variant views. Responsible Applicant and IM will be shown in Path Variants and operational IMs of the locations will be shown in the Territories.
  • Correction of the suggestion logic for activity type. Activity type values will be shown in alphabetical order according to the language setting of the user. The auto-suggestion will work also according to the user's language setting. E.g. Ve -> Verkehrshalt.
  •  Read-only access for IMs to other IMs data
  •  Path Request as a milestone for NPR and LPR. Path Request dossier status shall become a milestone for New Path Request and Late Path Request process. It shall work the same way as it works for Ad-Hoc and Rolling Planning.
  •  Warning for invalid operation points. Operation points that are with a validity period that is not in range of the sub-path validity period should be marked with a warning
  •  Get location data from RNE BigData DB. Mapping of operation points and synchronization on a daily level and deactivated not mapped operation points.
  •  Adjust PCS OP structure and Grid overview of OP in PCS administration. A read-only overview of operation points The view should be available for all users (placed in Administration tab) Search by country (single select), primary location code (input), operation point status (active, inactive) Country should be mandatory Operation point status should be active by default. Operation point information that should be shown ID, name, primary location code, valid from, valid to, longitude, and latitude.
  • Activity types - edit form. The IM users shall be able to add new and edit existing activity types. To allow this, create a form that will be used for adding and editing activity types. To update an existing activity type, it must not be used in a dossier. The user can add and edit activity types only in a specific period. You can retrieve the information whether the action is enabled or not from the back-end. Add info on whether the activity type is editable or not in the presentation model. The activity type has two attributes:
    • Code: 4 characters, e.g. CZ02 - Validate uniqueness of the code asynchronously (the validator already exists)
    • Description, e.g. Stop shorter than 1/2 min

(PCS EC Sprint 62 created, please visit for detailed description)