RNE PCS Maintenance Table

Title Issue type Priority Taken in Patch Release System OTRS ticket nr.
Advanced search criteria - improvement

"Reset fields" button should be more visible

show hidden fields if there are hidden fields in the active search criteria when you come back to the page

clear the values of the hidden fields if show all is unchecked.

If there are no search results, hide the Columns dropdown.

Improvement Minor 28/02/2018
Visibility of "add Path section" button improved

Make more visible (maybe darker) add path section button

Improvement Major 28/02/2018
Rename field: "days in service on this path"

field "days in service on this path" should be renamed to "Service days for reference point on this path"

check it on GUI, reports

Improvement Minor 28/02/2018
Change Traffic lights color

make clearer distinction between green, blue, grey

Improvement Major 28/02/2018
Dashboard labels improvements - incoming/outgoing icon is shown next to a shared label

Show an incoming/outgoing icon next to a shared label depending on whether someone shared it with the logged in user or he shared it with other users.

  • show outgoing icon for the user who shared the label.
  • show incoming icon for the user with whom the label is shared.
  • display the icons in "Label Filters", "Labels" and in the grid.
  • display tooltip above the icon to make it clearer.
Story Major 28/02/2018
Administration view of user filters is implemented

Create a specific administration view under personal settings for filters. More or less the same as for labels

  • In personal settings add 'Manage filters' button (Add 'Manage labels' button also).
  • Create specific 'Manage filters view' that contains the grid for the userdefined filters (Create 'Manage labels view' also).
  • Columns: Name, Valid From, Valid To, Owner, Shared, Edit Info, Edit Search Criteria, Share, Delete
  • Edit Info: Modal where name, valid from and valid to fields can be changed. Add the button to the dashboard also.
  • Edit Search Criteria: Redirect to Advanced Search. Rename the button in the dashboard also
Story Major 28/02/2018
User labels in a separate column in Dashboard search results

On the Dashboard, labels should go to their own column and not directly next to the dossier name. Column should be filterable and sortable (starts with, is equal to, is not equal to).

Especially it should be possible to search for "empty" i.e. dossiers that have no labels via the grid filter.

Story Major 28/02/2018
Administration view for of user labels

Specific administration view under personal settings for labels.

List all labels for the logged in user in a table with columns: 

  •  - name: the name of the label
  •  - description: description of the label
  •  - owner: Yes/No designating if the logged in user is the creator of the label
  •  - shared: Yes/No/Not Applicable designating if the user has shared the label with other users and Not Applicable in case owner = No
  • , and allow filtering by name/description and sharing option (grid filtering should be enough).

Option to Edit/Delete/Share a label. The edit option allows changing the description of the label but also the name. The name is mandatory. If the name is changed the user should be asked for confirmation and we advised that this will be reflected in the dossiers labeled with this label.

Edit option added in the dashboard, next to the Share and Delete options that show up when only one label is selected.

Deleting a label that is used in dossiers ask for a specific confirmation with warning that the label is used in dossiers and will be removed from them.

DB Change

Modify LABEL table add column DESCRIPTION. Add a corresponding field in the model.

Displaying labels

**Labels displayed with the description as on hover title.

  •  - dashboard labels menu
  •  - dashboard search results
  •  - dashboard search results top bar
  •  - dossier details

On the Dashboard, labels go to their own column and not directly next to the dossier name. Column should be filterable and sortable (starts with, is equal to, is not equal to).

Possible to search for "empty" i.e. dossiers that have no labels via the grid filter.

Story Major 28/02/2018
PAMT Search for RU/IM users
  • PAMT Search should be available for RU/IM users, not PAMT report.
  • RU/IM users want to have notification to them about pap statuses at X-8 and x-7.5 -> instead of sending notifications they can use PAMT Search
  • PAMT search results - single search result PAP dossier and NPR dossiers where that PAP dossier is used and this RU/IM is involved
  • PAMT search criteria: fields Show PAP dossiers and Show pap requests should not be shown for RU/IM users, because they should search only for PAP dossiers with requests only and pap requests are the one that are important for them
Improvement Major 28/02/2018
Path Request phase is milestone in adhoc process types
  • - Fixed wrong transition code from Path Request to Pre-Booking  
  • - Before saving the dossier draft, set its ttp to the ttp of the dossier model because that is the value that is changing when we select new ttp.
Improvement Major 28/02/2018
Improvements in catalogue import wizard
  • - do not show cancel buttons when an import is in progress;
    - train id is not required if taf-tsi is disabled;
    - "Path number" label is hidden if there is no value for it;
    - traffic period select is removed if there are no traffic periods.
Improvement Minor 28/02/2018
Check path sections without Operation point on dossier acceptance

1. Wizard steps were not properly marked - the current step was not highlighted, and the completed step was missing a checkmark… if you jump around all the steps seem disabled but they were still clickable.

2. Reorder paps -> hide “path number” if there’s no value 

3. Use traffic period removed if there are no traffic periods (empty select box)

4. Dossier level data - > the accordion with content either have arrows or should NOT be collapsible

Improvement Minor 28/02/2018
Grid sorting options are stored in display settings

When the grid data is changed (including sorting/filtering), the newly queried dossiers are stored in local storage so the prev/next buttons would work properly.

Improvement Major 28/02/2018
RU should see only published PaP Calendar

RU uses should see only published PaP calendar (requested and reserved calendar should not be shown to them)

Improvement Major 28/02/2018
Mark as unread option implemented in Dashboard

New button added to the Dashboard, Advanced Search and recent activity, when dossiers are selected. "Mark as unread" button added next to the current button "Mark as read".

Story Major 28/02/2018
Deletion of draft dossiers

In the dossier draft selection modal in the search results add a column with a delete button for each row. This allow removing a dossier draft one by one. Deletion have a confirmation dialog and after confirming the draft will be removed from the table.New button added to the Dashboard, Advanced Search and recent activity, when dossiers are selected. "Mark as unread" button added next to the current button "Mark as read".

Story Major 28/02/2018
Selection list of loco types - remove n/a

Removed n/a from the selection list for loco types in case there is no description defined.

Story Major 28/02/2018
Crash on copy dossier in TAF/TSI test system
  • validate validity period of path through WS
  • validate number of path sections in path (min 2 path sections)
Bug Major 08/03/2018 https://ts.railneteurope.info/otrs/index.pl?Action=AgentTicketZoom;TicketID=73066#120129
Allow leading RU to remove pap path sections that belong to the involved agencies Bug Major 08/03/2018 https://ts.railneteurope.info/otrs/index.pl?Action=AgentTicketZoom;TicketID=73070#120204
Web Services - restore missing DL params in IM requests

SNCF is not sending dossier level parameters in their requests. In PCS IP they were put back and status code 102 was generated. In PCS web services 302 is returned.

Story Major 09/11/2017 2017101287000087
Login screen additions: PCS web services version, new documentation links

Needs to be done:

  • supported version of IP (v5.1): add property to config.properties named "pcs.web.services.version"
  • pull up pcs version section
  • change link to PCS IP Documentation
  • rename  

Link for PCS IP documentation:

http://cms.rne.eu/pcs/pcs-documentation/pcs-ip-handbook
RNE CMS should be renamed to PCS Documentation

Story Major 09/11/2017
New notifications - process related

Notification about in Ad-Hoc and Late Path Request process types: 

  • RFC, IM, AB receives e-mail when path request was submitted by an RU
  • RU receives e-mail when harmonization was started by leading RU and when offer arrived (ad-hoc request, draft offer or final offer)

These notification depend on the process type, are hooked to certain dossier transition and agency type. Consider using ACL (or similar configuration) to define who gets such email notifications. Some of the existing notifications already are conditioned with phase transitions with direct checks before sending and in the workflow configuration which might not be the best place for this.

Story Major 09/11/2017
Exception to the N day rule for PAP dossiers for Short term path requests

Currently we have the N day rule defined in PCS that returns every day from the Published PaPs to the IMs. This is fine, but with this rule RFC are not able to process PAPs for short term path requests.

In order to be able to process that kind of PAP dossiers (with Exception to N-day rule) in Excel Importer, in the step where RFCs enter TTP, Train Type and Type of pre-constructed product we will add a check box where they can check if they want to import PAP dossiers for Short term path requests. That information will be kept on dossier level, will be shown in Dossier Basic Data and will be used to ignore those PAP dossiers in RFC capacity returning (automatic and manual) and PAP dossier Publishing. For those kind of dossier, instead of defined N-day rule, will be used 0-day rule.
Also the checkbox for paps for short term should be added in the pap manager.

Story Major 09/11/2017
Loco types view available to RFC's; moved C-OSS Dashboard navigation menu item

RFC's will benefit from access to loco types definition when resolving catalogue import issues.

Story Major 09/11/2017
Prevent changing responsible IM for a reference point

The problem was due to existence of two reference points for PKP-I and none for DB-NZ.
The border  Frankfurt (Oder) Oderbruecke was DB-NZ reference point in PR and than the responsible IM was changed but reference point was not reassigned.

Bug Major 09/11/2017 2017092687000036
Cannot add loco type

It should be possible to edit existing and add new loco types for all active timetable periods at all times. It should not be possible to delete a loco type that is used in dossiers.

This is a CR against the original requirements (Loco Types SRS v1.4.docx, Req. 1.c "The system shall allow addition of new loco types for the current timetable period at any time.").

Original task: https://extranet.netcetera.biz/jira/browse/RNE014-1294

For add operation: check if the timetable is created OR check for loco interval.

For edit/delete operation: check if the loco type is used in dossiers.

Bug Major 27/11/2017
N-Day rule was still taken into account for Short term Paps Bug Major 27/11/2017 2017112087000097
TTP 2019 end date is not correct

Last date of TTP 2019: 14th December 2019

Bug Major
Automatic RFC capacity return - failed when NO_CHANGES_FOUND

Automatic RFC capacity return - failed when NO_CHANGES_FOUND (prevent stopping of execution of RFC capacity return task in case of Exception on dossier level; check for changes before persisting CT dossier; move updating of CT/RFC calendars into separate service)

Improvement Major 06/12/2017
TAF/TSI System: Agency notifications namespace issue Story Major 06/12/2017 2017092987000012
Carry forward - loco type wrong label and message

In loco types step of carry forward the header says that loco type; national id, it should be loco type; explanation.

Further, even though correct loco type is selected for replacement it still asks for confirmation about proceeding without fixing outdated loco types.

 

Bug Major 06/12/2017
Quick search by path id fails for not number

Also should exit the PathId mode after Escape is hit, because currently only reload takes you back to the normal quick search.

And probably is better to accept non-case sensitive input of pathid let's say as a command.

Bug Major 06/12/2017
Czech translations Story Major 06/12/2017 2016120187000024
Issues when saving and propagating changes to subsidiary

There is now a cancel button in the dialog for propagation of parameter changes to subsidiaries. With this change if there is an error (no changes, or even something went wrong) the action can be canceled.
 

Bug Major 28/12/2017 https://ts.railneteurope.info/otrs/index.pl?Action=AgentTicketZoom;TicketID=72539#117188
Issues with train parameters templates

All templates created by any user from an agency can be seen and edited in Template administration but only the ones created by the logged in user can be selected when copying in the timetable view. 

Bug Major 28/12/2017 https://ts.railneteurope.info/otrs/index.pl?Action=AgentTicketZoom;TicketID=72538#117145
Fix for dossier report statistics

Reason

  • incorrect number of search results in Statistics/Archive report, because of dossier_ruimpair_archive.coss_id = dossier_ruimpair.coss_id

What was done:

  • use descr of the ReportType when sending mail for generated report
  • fix showing of expiration date on GUI
  • fix incorrect number of search results in Statistics/Archive report, because of dossier_ruimpair_archive.coss_id = dossier_ruimpair.coss_id
  • optimize Statistics/Archive report search query
  • refactor Statistic/Archive report search
  • fix select part for non-ruimpair dossiers in Register search
  • rename package archive-search to reports-search
  • rename frontend files dossier-archive-search to dossier-report-search
  • rename report related models
  • rename package dossierorganizerarchiverregister to dossier
  • change rest calls for report generation and archive/register search
Improvement Major 28/12/2017 https://ts.railneteurope.info/otrs/index.pl?Action=AgentTicketZoom;TicketID=72162#115353
Loco-type value dissapears after Path Alteration
  • dossier id: 172066, PA Offer
  • working copy of RU TT (loco type was missing)
  • state of the dossier was fixed with DB update (as loco type id was set loco type from working copy of IM TT)
Bug Major 28/12/2017 https://ts.railneteurope.info/otrs/index.pl?Action=AgentTicketZoom;TicketID=72467#116980
Dossiers need to be closed before TT starts

Use start date of TTP to check whether the start date of the TTP of the dossier has passed.

Bug Major 28/12/2017 https://ts.railneteurope.info/otrs/index.pl?Action=AgentTicketZoom;TicketID=72483#
Fix for inability to close dropdown when choosing Train Id agency

When editing train id if you select the agency field you cannot close it by clicking outside of it (and to select the same you have to find it again)

Bug Minor 28/12/2017
An exception occurs in search with labels selected at the same time Story Major 28/12/2017 https://ts.railneteurope.info/otrs/index.pl?Action=AgentTicketZoom;TicketID=72377#116518
Add adhoc pre-accepted process type in the PDF export table Story Major 28/02/2018 https://ts.railneteurope.info/otrs/index.pl?Action=AgentTicketZoom;TicketID=72825#118835
Train ID

Description

  • Train ID consists the following elements:
    • Object type: 2 characters (TR)
    • Company code: 4 digits (RICS or UIC code - user can choose from RU agencies that have UIC ID)
    • Core element: 12 characters
    • Variant: 2 digits (value: '00')
    • Timetable Year: 4 digits (ttp of the dossier)
    • Start-date (optional) <xs:minInclusive value="2012-01-01"/> <xs:maxInclusive value="2097-12-31"/>
  • Train ID should be mandatory element, in order to be compatible with master it's better to be defined as optional element in WS schema, and to return ERROR code if Train ID is not defined
  • This identifier should be stored on the dossier level in the Basic Data (under the international train number field) (should be shown on GUI)
  • Should be defined during the process of dossier creation in dossier wizard
  • Modification of the Train ID is possible only in Open phase (by Leading RU), after releasing the dossier to Harmonization the editing of the Train ID should be disabled
  • Core elementCompany codeVariant and Start date are the fields that should be entered by the user, the rest will be resolved by the system
  • Code list for Object Types:
    • Train: TR
    • Case Reference: CR
    • Path Request: PR
    • Path: PA

Implementation

  • add new columns in dossier table:
    • TSI_CORE_ELEMENT (rename already existing INT_TRAIN_NR_VARIANT to TSI_CORE_ELEMENT)
    • TSI_VARIANT (rename already existing TSI_VARIANT_COUNTER to TSI_VARIANT)
    • TSI_COMPANY_CODE
    • TSI_START_DATE
  • Object type - we know that for TRAIN_ID is 'TR'
  • Timetable period is the same as dossier timetable period
Story Critical 05/05/2017
Path request id / Path id

Description

  • Add element TsiPathId in PCS and TSI Layer will map with it
  • TsiPathId consists the following elements:
    • Object type: 2 characters (RU Path: PR, IM Path: PA)
    • Company code: 4 digits (UIC id of the owner of the path, RU UIC code in the RU Path, IM UIC code in the IM Path)
    • Core element: 12 characters
    • Variant: 2 digits (default value: '00')
    • Timetable Year: 4 digits (ttp of the dossier)
    • Start-date (optional) <xs:minInclusive value="2012-01-01"/> <xs:maxInclusive value="2097-12-31"/>
  • Should be available only in WS (not GUI) and should be defined as optional element that will have mentioned elements
  • Core elementVariantStart date are the one that should be entered by the user, the rest will be resolved by the system
  • Modification depends on the timetable and the agency. Path Request ID meaning RU timetable until the end of Harmonization, Path ID meaning IM timetable until the end of Ad-Hoc request Offer (Draft Offer). Then in Post-processing it should be possible again for the IM to change the ID.

Implementation

  • add new columns in trasse table:
    • TSI_CORE_ELEMENT
    • TSI_VARIANT (already exists in DB)
    • TSI_START_DATE
  • Object type - we know that for RU TT is PR, for IM Path is PA
  • Timetable period is the same as dossier timetable period
Story Critical 05/05/2017
Ad-hoc request, automatic promotion to Acceptance phase not working for non-PCS members Bug Major 04/04/2017 2017031787000126
(Web Services) Path Alteration process returns 102

How WS work with:

Path Alteration

  • start PA Replacement process
    • change dossier status to PA Conference <dossierstatus_id>AC</dossierstatus_id>
    • change process type to PA <processtype_id>E</processtype_id>
    • in pathAlterationTriggerRequest element enter pathAlterationType_idimPathId (paths that will be marked for editing), affected pairs cannot be marked through WS (they will be resolved automatically by PCS)
      		<pathAlterationTriggerRequest>
                        <pathAlterationTypes>
                           <!--1 or more repetitions:-->
                           <pathAlterationType_id>2</pathAlterationType_id>
                        </pathAlterationTypes>
                        <!--Optional:-->
                        <imsPathsForAlteration>
                           <!--1 or more repetitions:-->
                           <imPathId>402477</imPathId>
                        </imsPathsForAlteration>
                     </pathAlterationTriggerRequest>
      
  • starting PA Adjustment process through WS is currently not possible (maybe we should add separate operations where PA/PM process will be started) 
  • work with working copies: edit working copies, create new subsidiaries as 'Adjustment'
  • accept dossier as IM through WS
  • promote dossier to PA Offer
  • accept dossier as RU through WS
  • RU cannot accept/reject PA Offer (WS status code 618 is returned) 
    • i.e. dossier is in PA Offer and here for the RU available transitions as Reject PA Offer and Accept PA Offer, both transitions return dossier to Active TT (with current implementation, there is no way through WS to decide which transition to take -> proposal to have new operation were user can specify action that is performing)

Path Modification

  • start PM Replacement process
    • change dossier status to PM Conference <dossierstatus_id>MC</dossierstatus_id>
    • change process type to PM <processtype_id>M</processtype_id>
    • in pathModificationTriggerRequest element enter pathModificationType_idimPathId (paths that will be marked for editing), affected pairs cannot be marked through WS (they will be resolved automatically by PCS)
              <pathModificationTriggerRequest>
                  <pathModificationTypes>
                      <!--1 or more repetitions:-->
                      <pathModificationType_id>4</pathModificationType_id>
                      <pathModificationType_id>5</pathModificationType_id>
                  </pathModificationTypes>
                  <imsPathsForModification>
      				<imPathId>402590</imPathId>
                  </imsPathsForModification>
              </pathModificationTriggerRequest>
      
  • starting PM Adjustment process through WS is currently not possible (maybe we should add separate operations where PA/PM process will be started) 
  • work with working copies: edit working copies, create new subsidiaries as 'Adjustment'
  • accept dossier as RU through WS
  • promote dossier to PM Request
  • accept dossier as IM through WS
  • promote dossier to PM Offer
  • RU cannot accept/reject PM Offer (WS status code 620 is returned) 
    • i.e. dossier is in PM Offer and here for the RU available transitions as Reject PM Offer and Accept PM Offer, both transitions return dossier to Active TT (with current implementation, there is no way through WS to decide which transition to take -> proposal to have new operation were user can specify action that wants to perform)
Story Major 08/05/2017 2017031487000131
PDF export problem Bug Major 08/05/2017 2017050487000085
Dossier reports select/unselect all Story Major 08/05/2017 2017041387000088
Include route class in PDF report Bug Major 08/05/2017 2017042187000054
RU should be able to add attachments in Observation and Acceptance phase

In order to be able request e.g. terminal capacity, RUs are able to add attachments in Observations and Acceptance phase.

Improvement Major 24/07/2017
Fix for navigation issues in the dossier creation wizard

In the dossier wizard if you click on next steps nothing happens but errors are logged in the console.

Bug Minor 24/07/2017
PDF export, empty columns in train composition Bug Major 24/07/2017 2017051187000035
Missing PaPs from PAMT report - select all option was not working Story Major 24/07/2017
Crash when promoting dossiers observations to post processing Story Critical 03/08/2017 2017080387000116
Traction details -> Traction mode -> Banking locomotive visual confusion Improvement Major 2017061987000037
Fix for bulk acceptance indicator change fails for dossiers with observations

Observation types were not deserialized properly when received as part of the selected dossier presentation model.

Bug Minor 10/11/2017
Fix for IM parameter value can be changed despite of dependent params

Parent params values should not be changed if there is a dependency to them in some child params (nested conditions and mandatory exception).

Bug Major 10/11/2017 2017110687000088
PCS WS notification handler example service is published again as it is needed as a template when agencies integrate 10/11/2017 2017110287000086
Loco types missing in Pre-booking

Ad-hoc dossiers created prior to loco types being introduced and promoted to Path Request after, are with missing loco types. Now they will be resolved during promotion.

Bug Major
Fix for IM Parameters mandatory exception without value could be saved

It is possible to create IM parameter with mandatory exception with empty parameter value.

Bug Major 10/11/2017
Fix for IM param default value not set for path section level Bug Major 10/11/2017 2017110787000022